5. Submitting a recurring transaction
You can submit a recurring payment using a specific recurringDetails record or by using the last created recurringDetails record. The
request for the recurring payment is done using a paymentRequest.
5.1. Payment request
You can submit a recurring payment by calling the authorise action on the Payment service with a paymentRequest. However, a One-
Click payment session is set up like a regular payment and these additional fields are not required. Please refer to section 3.1 for
more information on setting up the payment.
5.1.1. One-Click payments
The paymentRequest is set up like a regular payment with a couple of differences:
• card
The container for card data. This should contain the following items:
o expiryMonth
The field should be null.
o expiryYear
The field should be null.
o holderName
The field should be null.
o number
The field should be null.
o cvc
The card validation code. This is the CVC2 code (for MasterCard), CVV2 (for Visa) or CID (for American Express).
• recurring
o contract
If “ONECLICK,RECURRING” was specified initially, then this field should be “ONECLICK”. Please refer to section 3 for
more information.
• shopperInteraction
Set to “Ecommerce”.
5.1.2. Recurring payments
The paymentRequest has the following fields:
• selectedRecurringDetailReference
The recurringDetailReference you want to use for this payment. The value “LATEST” can be used to select the most recently
stored recurring detail.
• 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
“RECURRING”. Please refer to section 3 for more information.
• merchantAccount
The merchant account for which you want to process the payment.
• amount
The amount to authorise. This consists of a currencyCode and a paymentAmount. Please refer to section 2.2 of the Adyen
Merchant Integration Manual for more information.
• shopperEmail
The shopper's email address. This does not have to match the email address supplied with the initial payment.
• shopperReference
An ID that uniquely identifies the shopper. This shopperReference must be the same as the shopperReference used in the
initial payment.
• shopperInteraction
Set to “ContAuth”.
