Operation Manual

Recurring payments manual

<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:authorise xmlns:ns1="http://payment.services.adyen.com">

<ns1:paymentRequest>

</amount>

<ns1:merchantAccount>SupportAdyenTest</ns1:merchantAccount>

<ns1:reference>SubscriptionOrder031-241</ns1:reference>

<ns1:shopperEmail>gras.shopper77@somewhere.org</ns1:shopperEmail>

<ns1:shopperReference>grasshopper77</ns1:shopperReference>

<ns1:selectedRecurringDetailReference>8313147988756818</ns1:selectedRecurringDetailReference>

<ns1:recurring>

<ns1:contract>RECURRING</ns1:contract>

</ns1:recurring>

<ns1:shopperInteraction>ContAuth</ns1:shopperInteraction>

</ns1:paymentRequest>

</ns1:authorise>

</soap:Body>

</soap:Envelope>

The response might look as follows:

<?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:authoriseResponse xmlns:ns1="http://payment.services.adyen.com">

<ns1:paymentResult>

<resultCode xmlns="http://payment.services.adyen.com">Authorised</resultCode>

</ns1:paymentResult>

</ns1:authoriseResponse>

</soap:Body>

</soap:Envelope>

Notifications are also sent, as was the case in Step 1.

Step 4: Storing a second recurring detail

On 17 January 2014, the shopper purchases another product from the Merchant.

As with Step 2, the Merchant retrieves a list of the stored recurring details and gets the same result as presented there. The

Merchant offers the shopper the choice of using the previously stored card ending with “1111” or a new card. This time the shopper

chooses to use a new card, so the Merchant must now submit a Payment where they will create another recurring detail on an

existing recurring contract.

The payment request might look as follows: