4. Retrieving the recurring contract details
When you want to submit a recurring payment, you may choose to query the Adyen system to return any stored payment details.
This is done by submitting a request to the listRecurringDetails action.
4.1. listRecurringDetails request
The request has the following fields:
• merchantAccount
Your merchant account.
• shopperReference
Your unique ID for the shopper. This shopperReference must be the same as the shopperReference used in the initial
payment.
• recurring
o contract
This should be the same value that was submitted using recurringContract in the payment where the recurring
contract was created. However, if “ONECLICK,RECURRING” was specified initially, then this field should be either
“ONECLICK” or “RECURRING” depending on whether or not you want the shopper to enter their card's security
code. Please refer to section 3 for more information.
Please refer to Step 2 of Appendix B for a SOAP example of a listRecurringDetails request and response.
Please refer to Appendix C for a REST example of a listRecurringDetails request and response.
4.2. listRecurringDetails response
The response will be a result with a list of zero or more details containing:
• recurringDetailReference
The unique reference the details are stored under.
• variant
The payment method, such as “mc”, “visa”, “ideal”, “paypal”.
• creationDate
The date when the recurring details were created.
The recurring contracts are stored in the same object types that were used to submit the initial payment. Depending upon the
payment method, one or more fields may be blank or incomplete, for example CVC for card. Only one of the details below will be
returned per detail block, the others will be nil. For wallets (Paypal, Moneybookers/Skrill, Neteller) there is not a detail block.
• card
A container for credit card data. This contains the following items:
o expiryMonth
The expiration date's month written as a 2-digit string, padded with 0 if required, for example 03 or 12.
o expiryYear
The expiration date's year written in full, for example 2008.
o holderName
The card holder's name as embossed on the card.
o number
The card number. Only the last 4 digits of the card number are returned.
o cvc
The card validation code. This is the CVC2 code (for MasterCard), CVV2 (for Visa) or CID (for American Express).
The value will always be empty because it is not stored.
• Elv – deprecated 1
st
August 2014
A container for elv data with the following fields:
o bankLocation
The city in which the bank (branch) is located.
o bankName
The name of the bank.
