Authorise using details stored with a third party

Adyen is no longer developing the Classic API integration

This page is for the Classic API (/authorise) integration, which we no longer accept new integrations with.

We strongly recommend switching to the newer Network tokenization integration.

When you store payment details with a third party, you can use these details to authorise payments.

Initial Card on file/Subscription payments

The following fields must be passed in a Card-on-File/Subscription payment request:

amount
shopperInteraction: set to Ecommerce for the initial payment or set to ContAuth for subsequent payments.
recurringProcessingModel: set to Subscription for payments that recur on a fixed schedule, and Card On File for payments that do not occur on a fixed schedule.

{
   "card":{
      "number":"4111111111111111",
      "expiryMonth":"8",
      "expiryYear":"2018",
      "cvc":"737",
      "holderName":"John Smith"
   },
   "amount":{
      "value":2000,
      "currency":"EUR"
   },
   "reference":"Your Reference Here",
   "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
   "shopperEmail":"s.hopper@test.com",
   "shopperInteraction":"Ecommerce",
   "shopperIP":"61.294.12.12",
   "recurringProcessingModel":"Subscription"
}

Subsequent payments

{
   "card":{
      "number":"4111111111111111",
      "expiryMonth":"8",
      "expiryYear":"2018",
      "cvc":"737",
      "holderName":"John Smith"
   },
   "amount":{
      "value":2000,
      "currency":"EUR"
   },
   "reference":"Your Reference Here",
   "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
   "shopperEmail":"s.hopper@test.com",
   "shopperInteraction":"ContAuth",
   "shopperIP":"61.294.12.12",
   "recurringProcessingModel":"Subscription"
}