Operation Manual

Recurring payments manual

Appendix B: Complete workflow example

To help understand the principles outlined in this manual, we will walk through a scenario, from the initial payment through to

subsequent recurring payments.

The Merchant has two offerings – products and subscriptions. For products, the shopper selects a product, pays, and then has the

item delivered to them. The Merchant has decided that, for certain products, they will allow the shopper to choose from an existing

stored card, if it exists, or the option to add a new one.

For subscriptions, the shopper selects a service, pays upfront for the first month, with the option to select from existing stored cards

if they exist, and agrees to be automatically charged every month until they cancel. The Merchant has decided that, for subscriptions

only, they will always use the last stored card details for the shopper in subsequent months.

Step 1: First initial recurring payment

On the 1

of January 2014 a shopper signs up with the Merchant and is making their first purchase of a product.

The Merchant creates a Payment request including the required additional fields as follows:

• shopperReference: grasshopper77

• shopperEmail: gras.shopper77@somewhere.org

• recurringContract: RECURRING

The payment request might look as follows:

<input type="hidden" name="orderData"

value="H4sIAAAAAAAAALMpsOPlCkssyswvLVZIz89PKVZIzEtRKE4tKstMTi3W4+Wy0S+wAwDOGUCXJgAAAA==" />

Once on the HPP, the shopper successfully uses a Visa card ending 1111, and the Merchant receives an AUTHORISATION notification

of successful payment. The merchant now knows the recurring detail has been stored, with a new recurring contract created. The

Merchant does not receive any information about the recurring details, as these are not needed at this point.

Step 2: listRecurringDetails for a shopper

A week later, on 8

January 2014, the same shopper returns to the website and purchases a subscription.

The Merchant decides to check to see if the shopper has any stored recurring details:

<?xml version="1.0"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soap:Body>

<ns1:listRecurringDetails xmlns:ns1="http://recurring.services.adyen.com">

<ns1:request>

<ns1:recurring>

<contract xmlns="http://payment.services.adyen.com">RECURRING</value>