Make a donation

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.

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.

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

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 2 redirect.

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

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

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

The shopper country.

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

The shopper's date of birth.

Format ISO-8601: YYYY-MM-DD

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

The address where the purchased goods should be delivered.

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

Donation account to which the transaction is credited.

The donation campaign ID received in the /donationCampaigns call.

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

Donation token received in the /payments call.

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 Riverty.

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

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 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.

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

Required for browser-based (channel Web) 3D Secure 2 transactions.Set this to the origin URL of the page where you are rendering the Drop-in/Component. Do not include subdirectories and a trailing slash.

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

When donationToken is provided, the payment method is derived from the token and this field becomes optional.

If you are PCI compliant, and make donations using raw card details, you must explicitly provide the payment method details.

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.

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

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

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.

The URL to return to in case of a redirection. The format depends on the channel.

• 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: https://your-company.example.com/checkout?shopperOrder=12xy
• 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://your.package.name

If the URL to return to includes non-ASCII characters, like spaces or special letters, URL encode the value.

We strongly recommend that you use a maximum of 1024 characters.

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

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

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

The shopper's email address. We recommend that you provide this data, as it is used in velocity fraud checks. > Required for Visa and JCB transactions that require 3D Secure 2 authentication if you did not include the telephoneNumber.

The shopper's IP address. 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).

Required for Visa and JCB transactions that require 3D Secure 2 authentication for all web and mobile integrations, if you did not include the shopperEmail. For native mobile integrations, the field is required to support cases where authentication is routed to the redirect flow. This field is also mandatory for some merchants depending on your business model. For more information, contact Support.

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 authorization 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 authorization (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.

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

The shopper's full name.

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.

The shopper's social security number.

The shopper's telephone number. The phone number must include a plus sign (+) and a country code (1-3 digits), followed by the number (4-15 digits). If the value you provide does not follow the guidelines, we do not submit it for authentication.

Required for Visa and JCB transactions that require 3D Secure 2 authentication, if you did not include the shopperEmail.

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.

Required to trigger the authentication-only flow. If set to true, you will only perform the 3D Secure 2 authentication, and will not proceed to the payment authorization.Default: false.