Start a transaction for donations

post /donations

Takes in the donation token generated by the /payments request and uses it to make the donation for the donation account specified in the request.

For more information, see Donations.

Endpoint destination URL
Click to copy

Header parameters

Idempotency-Key string

A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).

Request parameters

accountInfo object

Shopper account information for 3D Secure 2.

For 3D Secure 2 transactions, we recommend that you include this object to increase the chances of achieving a frictionless flow.

additionalAmount object

If you want a BIN or card verification request to use a non-zero value, assign this value to additionalAmount (while the amount must be still set to 0 to trigger BIN or card verification). Required to be in the same currency as the amount.

additionalData object

This field contains additional data, which may be required for a particular payment request.

The additionalData object consists of entries, each of which includes the key and value.

amount object Required

The amount information for the transaction (in minor units). For BIN or card verification requests, set amount to 0 (zero).

applicationInfo object

Information about your application. For more details, see Building Adyen solutions.

authenticationData object

Data for 3DS authentication.

billingAddress object

The address where to send the invoice.

The billingAddress object is required in the following scenarios. Include all of the fields within this object.

  • For 3D Secure 2 transactions in all browser-based and mobile implementations.
  • For cross-border payouts to and from Canada.
browserInfo object

The shopper's browser information.

For 3D Secure, the full object is required for web integrations. For mobile app integrations, include the userAgent and acceptHeader fields to indicate that your integration can support a redirect in case a payment is routed to 3D Secure 1.

captureDelayHours integer

The delay between the authorisation and scheduled auto-capture, specified in hours.

channel string

The platform where a payment transaction takes place. This field is optional for filtering out payment methods that are only available on specific platforms. If this value is not set, then we will try to infer it from the sdkVersion or token.

Possible values:

  • iOS
  • Android
  • Web
checkoutAttemptId string

Checkout attempt ID that corresponds to the Id generated by the client SDK for tracking user payment journey.

company object

Information regarding the company.

conversionId string Deprecated in version 68

Use checkoutAttemptId instead

Conversion ID that corresponds to the Id generated by the client SDK for tracking user payment journey.

countryCode string

The shopper country.

Format: ISO 3166-1 alpha-2 Example: NL or DE

dateOfBirth string

The shopper's date of birth.

Format ISO-8601: YYYY-MM-DD

dccQuote object

The forex quote as returned in the response of the forex service.

deliverAt string

The date and time the purchased goods should be delivered.

Format ISO 8601: YYYY-MM-DDThh:mm:ss.sssTZD

Example: 2017-07-17T13:42:40.428+01:00

deliveryAddress object

The address where the purchased goods should be delivered.

deliveryDate string Deprecated in version 70

Use deliverAt instead.

The date and time the purchased goods should be delivered.

Format ISO 8601: YYYY-MM-DDThh:mm:ss.sssTZD

Example: 2017-07-17T13:42:40.428+01:00

deviceFingerprint string
Max length: 5000

A string containing the shopper's device fingerprint. For more information, refer to Device fingerprinting.

donationAccount string Required

Donation account to which the transaction is credited.

donationOriginalPspReference string

PSP reference of the transaction from which the donation token is generated. Required when donationToken is provided.

donationToken string

Donation token received in the /payments call.

enableOneClick boolean

When true and shopperReference is provided, the shopper will be asked if the payment details should be stored for future one-click payments.

enablePayOut boolean

When true and shopperReference is provided, the payment details will be tokenized for payouts.

enableRecurring boolean

When true and shopperReference is provided, the payment details will be tokenized for recurring payments.

entityType string

The type of the entity the payment is processed for.

fraudOffset integer

An integer value that is added to the normal fraud score. The value can be either positive or negative.

fundOrigin object

The person or entity funding the money.

fundRecipient object

the person or entity receiving the money

industryUsage string

The reason for the amount update. Possible values:

  • delayedCharge
  • noShow
  • installment
installments object

Contains installment settings. For more information, refer to Installments.

lineItems array [object]

Price and product information about the purchased items, to be included on the invoice sent to the shopper.

This field is required for 3x 4x Oney, Affirm, Afterpay, Clearpay, Klarna, Ratepay, and Zip.

localizedShopperStatement object

The localizedShopperStatement field lets you use dynamic values for your shopper statement in a local character set. If not supplied, left empty, or for cross-border transactions, shopperStatement is used.

Adyen currently supports the ja-Kana character set for Visa and Mastercard payments in Japan using Japanese cards. This character set supports:

  • UTF-8 based Katakana, capital letters, numbers and special characters.
  • Half-width or full-width characters.
mandate object

The mandate details to initiate recurring transaction.

mcc string

The merchant category code (MCC) is a four-digit number, which relates to a particular market segment. This code reflects the predominant activity that is conducted by the merchant.

merchantAccount string Required

The merchant account identifier, with which you want to process the transaction.

merchantOrderReference string

This reference allows linking multiple transactions to each other for reporting purposes (i.e. order auth-rate). The reference should be unique per billing cycle. The same merchant order reference should never be reused after the first authorised attempt. If used, this field should be supplied for all incoming authorisations.

We strongly recommend you send the merchantOrderReference value to benefit from linking payment requests when authorisation retries take place. In addition, we recommend you provide retry.orderAttemptNumber, retry.chainAttemptNumber, and retry.skipRetry values in PaymentRequest.additionalData.

merchantRiskIndicator object

Additional risk fields for 3D Secure 2.

For 3D Secure 2 transactions, we recommend that you include this object to increase the chances of achieving a frictionless flow.

metadata object

Metadata consists of entries, each of which includes a key and a value. Limits:

  • Maximum 20 key-value pairs per request. When exceeding, the "177" error occurs: "Metadata size exceeds limit".
  • Maximum 20 characters per key.
  • Maximum 80 characters per value.
mpiData object

Authentication data produced by an MPI (Mastercard SecureCode, Visa Secure, or Cartes Bancaires).

order object

The order information required for partial payments.

orderReference string

When you are doing multiple partial (gift card) payments, this is the pspReference of the first payment. We use this to link the multiple payments to each other. As your own reference for linking multiple payments, use the merchantOrderReferenceinstead.

origin string
Max length: 80

Required for the 3D Secure 2 channel Web integration.

Set this parameter to the origin URL of the page that you are loading the 3D Secure Component from.

paymentMethod Required

The type and required details of a payment method to use.

platformChargebackLogic object

Defines how to book chargebacks when using Adyen for Platforms.

recurringExpiry string

Date after which no further authorisations shall be performed. Only for 3D Secure 2.

recurringFrequency string

Minimum number of days between authorisations. Only for 3D Secure 2.

recurringProcessingModel string

Defines a recurring payment type. Required when creating a token to store payment details or using stored payment details. Allowed values:

  • Subscription – A transaction for a fixed or variable amount, which follows a fixed schedule.
  • CardOnFile – With a card-on-file (CoF) transaction, card details are stored to enable one-click or omnichannel journeys, or simply to streamline the checkout process. Any subscription not following a fixed schedule is also considered a card-on-file transaction.
  • UnscheduledCardOnFile – An unscheduled card-on-file (UCoF) transaction is a transaction that occurs on a non-fixed schedule and/or have variable amounts. For example, automatic top-ups when a cardholder's balance drops below a certain amount.
redirectFromIssuerMethod string

Specifies the redirect method (GET or POST) when redirecting back from the issuer.

redirectToIssuerMethod string

Specifies the redirect method (GET or POST) when redirecting to the issuer.

reference string Required

The reference to uniquely identify a payment. This reference is used in all communication with you about the payment status. We recommend using a unique value per payment; however, it is not a requirement. If you need to provide multiple references for a transaction, separate them with hyphens ("-"). Maximum length: 80 characters.

returnUrl string Required
Max length: 8000

The URL to return to in case of a redirection. The format depends on the channel. This URL can have a maximum of 1024 characters.

  • For web, include the protocol http:// or https://. You can also include your own additional query parameters, for example, shopper ID or order reference number. Example:
  • For iOS, use the custom URL for your app. To know more about setting custom URL schemes, refer to the Apple Developer documentation. Example: my-app://
  • For Android, use a custom URL handled by an Activity on your app. You can configure it with an intent filter. Example: my-app://
riskData object

Contains risk data, such as client-side data, used to identify risk for a transaction.

sessionValidity string

The date and time until when the session remains valid, in ISO 8601 format.

For example: 2020-07-18T15:42:40.428+01:00

shopperEmail string

The shopper's email address. We recommend that you provide this data, as it is used in velocity fraud checks.

For 3D Secure 2 transactions, schemes require shopperEmail for all browser-based and mobile implementations.

shopperIP string

The shopper's IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks).

For 3D Secure 2 transactions, schemes require shopperIP for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, contact Support.

shopperInteraction string

Specifies the sales channel, through which the shopper gives their card details, and whether the shopper is a returning customer. For the web service API, Adyen assumes Ecommerce shopper interaction by default.

This field has the following possible values:

  • Ecommerce - Online transactions where the cardholder is present (online). For better authorisation rates, we recommend sending the card security code (CSC) along with the request.
  • ContAuth - Card on file and/or subscription transactions, where the cardholder is known to the merchant (returning customer). If the shopper is present (online), you can supply also the CSC to improve authorisation (one-click payment).
  • Moto - Mail-order and telephone-order transactions where the shopper is in contact with the merchant via email or telephone.
  • POS - Point-of-sale transactions where the shopper is physically present to make a payment using a secure payment terminal.
shopperLocale string

The combination of a language code and a country code to specify the language to be used in the payment.

shopperName object

The shopper's full name.

shopperReference string
Min length: 3 Max length: 256

Required for recurring payments. Your reference to uniquely identify this shopper, for example user ID or account ID. Minimum length: 3 characters.

Your reference must not include personally identifiable information (PII), for example name or email address.

shopperStatement string

The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.

socialSecurityNumber string

The shopper's social security number.

splits array [object]

An array of objects specifying how to split a payment when using Adyen for Platforms, Classic Platforms integration, or Issuing.

store string
Min length: 1 Max length: 16

The ecommerce or point-of-sale store that is processing the payment. Used in:

storePaymentMethod boolean

When true and shopperReference is provided, the payment details will be stored.

telephoneNumber string

The shopper's telephone number.

threeDS2RequestData object

Request fields for 3D Secure 2. To check if any of the following fields are required for your integration, refer to Online payments or Classic integration documentation.

threeDSAuthenticationOnly boolean Deprecated in version 69

Use authenticationData.authenticationOnly instead.

If set to true, you will only perform the 3D Secure 2 authentication, and not the payment authorisation.

trustedShopper boolean

Set to true if the payment should be routed to a trusted MID.

Response parameters

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

  • 200 - OK

    The request has succeeded.

    Show more Show less
  • 400 - Bad Request

    A problem reading or understanding the request.

    Show more Show less
  • 401 - Unauthorized

    Authentication required.

    Show more Show less
  • 403 - Forbidden

    Insufficient permissions to process the request.

    Show more Show less
  • 422 - Unprocessable Entity

    A request validation error.

    Show more Show less
  • 500 - Internal Server Error

    The server could not process the request.

    Show more Show less
  • Request
  • Click to copy
  • Response
  • Click to copy