Operation Manual
25
Recurring payments manual
<input type="hidden" name="orderData"
value="H4sIAAAAAAAAALMpsOPlCkssyswvLVZIz89PKVZIzEtRKE4tKstMTi3W4+Wy0S+wAwDOGUCXJgAAAA==" />
<input type="hidden" name="sessionValidity" value="2014-01-18T11:00:00Z" />
<input type="hidden" name="merchantSig" value="33syWRtfDxDwq3235zOlEyZ0j3pg=" />
<input type="hidden" name="shopperEmail" value="gras.shopper77@somewhere.org" />
<input type="hidden" name="shopperReference" value="grasshopper77" />
<input type="hidden" name="recurringContract" value="RECURRING" />
Once on the HPP, the shopper successfully uses a Mastercard ending 4444, and the Merchant receives an AUTHORISATION
notification of successful payment. The merchant now knows the recurring detail has been stored against the existing recurring
contract. The Merchant does not receive any information about the recurring details, as these are not needed at this point.
There is now one recurring contract with two recurring details – the Visa card from the first purchase, and the Mastercard from this
purchase.
Step 5: Second subsequent payment
On 08 February 2014, a month has passed and the Merchant now needs to charge the shopper the next installment of their
subscription. Since the Merchant has chosen to use the latest stored details of the shopper they do not need to go through Step 2.
Instead they can immediately submit the Payment request with the following additional fields:
• selectedRecurringDetailReference: “LATEST”
• recurring / contract: “RECURRING” since it was set this way in Step 1
• shopperInteraction: “ContAuth” since the contract is RECURRING
The payment request, this time sent via SOAP, 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:authorise xmlns:ns1="http://payment.services.adyen.com">
<ns1:paymentRequest>
<amount xmlns="http://payment.services.adyen.com">
<currency xmlns="http://common.services.adyen.com">EUR</currency>
<value xmlns="http://common.services.adyen.com">1000</value>
</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>LATEST</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 is similar to that of Step 3, except that the Mastercard from Step 4 is used for the Payment, and not the Visa card from
Steps 1 & 3, since it was the most recently used recurring detail for this shopper.
This can be verified by looking up the recurring details for the shopper and noting the creationDate in each RecurringDetail:
<?xml version="1.0"?>










