Operation Manual
23
Recurring payments manual
</ns1:recurring>
<ns1:merchantAccount>SupportAdyenTest</ns1:merchantAccount>
<ns1:shopperReference>grasshopper77</ns1:shopperReference>
</ns1:request>
</ns1:listRecurringDetails>
</soap:Body>
</soap:Envelope>
The response comes back that there is one stored card for the shopper – the Visa from the first payment. Here we can see the
recurringDetailReference for the first time:
<?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:listRecurringDetailsResponse xmlns:ns1="http://recurring.services.adyen.com">
<ns1:result>
<creationDate xmlns="http://recurring.services.adyen.com">2014-01-01T01:50:12.178+01:00</creationDate>
<details xmlns="http://recurring.services.adyen.com">
<RecurringDetail>
<bank xsi:nil="true"/>
<card>
<cvc xmlns="http://payment.services.adyen.com" xsi:nil="true"/>
<expiryMonth xmlns="http://payment.services.adyen.com">12</expiryMonth>
<expiryYear xmlns="http://payment.services.adyen.com">2016</expiryYear>
<holderName xmlns="http://payment.services.adyen.com">Grass Hopper</holderName>
<number xmlns="http://payment.services.adyen.com">1111</number>
</card>
<creationDate>2014-01-01T01:50:16.353+01:00</creationDate>
<elv xsi:nil="true"/>
<name xsi:nil="true"/>
<recurringDetailReference>8313147988756818</recurringDetailReference>
<variant>visa</variant>
</RecurringDetail>
</details>
<lastKnownShopperEmail
xmlns="http://recurring.services.adyen.com">gras.hopper77@somewhere.org</lastKnownShopperEmail>
<shopperReference xmlns="http://recurring.services.adyen.com">grashopper77</shopperReference>
</ns1:result>
</ns1:listRecurringDetailsResponse>
</soap:Body>
</soap:Envelope>
Step 3: Subsequent payment
Based upon the results of step 2, the Merchant offers the shopper the choice of using the previously stored card ending with “1111”
or a new card. The shopper chooses to use the existing card ending with “1111”, so the Merchant can now submit a Payment without
the shopper needing to enter their card details again.
The merchant submits a Payment request with the following additional fields:
• selectedRecurringDetailReference: In this case it is “8313147988756818”
• 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"?>