Adyen is phasing out Classic API integration
This page is for the Classic API (
/authorise) integration, which we are no longer developing.
We strongly recommend switching to the newer Tokenization integration.
After you store payment details along with an
/authorisation call, you need the
recurringDetailReference to refer to the stored details in other requests.
To retrieve the payment details and their reference number, use the
/listRecurringDetails call. In this call, pass your merchant account and a reference of a shopper, whose payment details were previously stored.
For information on all available fields, see .
The following example demonstrates how to get payment details stored with your TestMerchant account for a shopper 14194858.
If there are payment details stored for the specified
shopperReference, the response contains one or more
RecurringDetail objects. In this object some fields may be missing or nil, depending on the payment method being used.
The response is different in the following scenarios:
- If the
shopperReferencedoes not exist, the endpoint returns an empty object.
- If the
shopperReferenceexists but the request contains a specific
contracttype and a recurring detail for that contract does not exist, the
detailsarray is not included in the response.
For information on all fields available in a response, see RecurringDetailsResult.
The following example shows the response if a shopper 14194858 stored the details of their VISA Debit card with a number starting with 492179. In this case, the
recurringDetailReference is equal to 8313147988756818.