Use tokenized payment information for recurring and subscription payments.
Making a payment
To make a payment using a token, make a
/payments request. Include the following values:
shopperInteractionset to ContAuth.
A successful payment has a HTTP status of 200 and a
resultCode of Authorised.
Recurring transaction types
Some payment methods require payment requests to be flagged based on whether the shopper was present to enter the payment information themselves at point of payment, which is called a shopper-present transaction. If the shopper didn't enter their information at point of payment and saved details or card on file were used, this is called a shopper-not-present transaction.
Specify the shopper interaction,
shopperInteraction, as Ecommerce for shopper-present transactions or ContAuth for shopper-not-present transaction.
Whenever you make a card payment without collecting CVC, you need to specify the
shopperInteraction as ContAuth.
Collecting CVV with token
You may want to allow your shoppers to use their previously saved payment details, yet still collect the CVV in order to improve your auth rate and fraud protection. Use our Secured Fields to enable this.
On your payments page, only collect the CVV of the shopper. Then make a
/payments request, and include the following values:
paymentMethod.encryptedSecurityCode: The shopper's CVV, encrypted using Secured Fields.
If you're collecting raw card data, pass
paymentMethod.cvcinstead, specifying the shopper's CVV.
shopperInteraction: Set to Ecommerce.
Capture a payment
Capture approved authorisation when it's necessary to complete the payment.
Retrieve, update, and disable tokens you stored with Adyen.