Adyen · Schema

DonationPaymentRequest

DonationPaymentRequest schema from Adyen API

PaymentsFinancial ServicesFintech

Properties

Name Type Description
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.
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 The amount information for the transaction (in [minor units](https://docs.adyen.com/development-resources/currency-codes)). For [BIN or card verification](https://docs.adyen.com/payment-methods/cards/
applicationInfo object Information about your application. For more details, see [Building Adyen solutions](https://docs.adyen.com/development-resources/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 browse
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 yo
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
checkoutAttemptId string Checkout attempt ID that corresponds to the Id generated by the client SDK for tracking user payment journey.
conversionId string 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](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) Example: NL or DE
dateOfBirth string The shopper's date of birth. Format [ISO-8601](https://www.w3.org/TR/NOTE-datetime): YYYY-MM-DD
deliverAt string The date and time the purchased goods should be delivered. Format [ISO 8601](https://www.w3.org/TR/NOTE-datetime): 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.
deviceFingerprint string A string containing the shopper's device fingerprint. For more information, refer to [Device fingerprinting](https://docs.adyen.com/risk-management/device-fingerprinting).
donationAccount string 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.
lineItems array 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 Zi
merchantAccount string The merchant account identifier, with which you want to process the transaction.
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". * Maxim
mpiData object Authentication data produced by an MPI (Mastercard SecureCode, Visa Secure, or Cartes Bancaires).
origin string 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 object The type and required details of a payment method to use.
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 amou
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 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 require
returnUrl string 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
sessionValidity string The date and time until when the session remains valid, in [ISO 8601](https://www.w3.org/TR/NOTE-datetime) 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 m
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 Se
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 b
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 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 identif
socialSecurityNumber string The shopper's social security number.
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](https://docs.adyen.com/online-payments) or [Classic integration](h
threeDSAuthenticationOnly boolean If set to true, you will only perform the [3D Secure 2 authentication](https://docs.adyen.com/online-payments/3d-secure/other-3ds-flows/authentication-only), and not the payment authorisation.
View JSON Schema on GitHub