A unique identifier of this stored payment method.
The adyen saved payment methods response, contains data about saved cards
| Property | Type | Description |
|---|---|---|
|
|
A unique identifier of this stored payment method. |
|
|
The brand of the card. |
|
|
The last four digits of the PAN. |
|
|
The display name of the stored payment method. |
|
|
The type of payment method. |
|
|
Any additional information in the response. |
The request to create a Payment Session.
| Property | Type | Description |
|---|---|---|
|
|
The amount of the payment. |
|
|
The reference to uniquely identify a payment. For example, the payment owner ID (Cart ID etc). |
|
|
The URL to return to when a redirect payment is completed. |
|
|
Defines a recurring payment type. Required when creating a token to store payment details. Allowed values: <ul> <li>Subscription – A transaction for a fixed or variable amount, which follows a fixed schedule.</li> <li>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.</li> <li>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.</li> </ul> |
|
|
Indicates if the details of the payment method will be stored for the shopper. Possible values: <ul> <li>disabled – No details will be stored (default).</li> <li>askForConsent – If the shopperReference is provided, the UI lets the shopper choose if they want their payment details to be stored.</li> <li>enabled – If the shopperReference is provided, the details will be stored without asking the shopper for consent.</li> </ul> |
|
|
Metadata consists of entries, each of which includes a key and a value. Limits: <ul> <li>Maximum 20 key-value pairs per request.</li> <li>Maximum 20 characters per key.</li> <li>Maximum 80 characters per value.</li> </ul> |
|
|
Any additional information for the request. |
The session response contains encrypted payment session data
| Property | Type | Description |
|---|---|---|
|
|
A unique identifier of the session. |
|
|
The payment session data you need to pass to your front end. |
|
|
Any additional information in the response. |
| Property | Type | Description |
|---|---|---|
|
|
The amount information for the transaction. |
|
|
The shopper’s country code. |
|
|
The combination of a language code and a country code to specify the language to be used in the payment. |
|
|
Required for recurring payments. Your reference to uniquely identify this shopper, for example user ID or account ID. Minimum length: 3 characters. |
|
|
The order information required for partial payments. |
|
|
Any additional information for the request. |
| Property | Type | Description |
|---|---|---|
|
|
The unique payment method code. |
|
|
The displayable name of this payment method. |
|
|
All input details to be provided to complete the payment with this payment method. |
|
|
Configuration props as set by the merchant in the CA and received in the PM object in the /paymentMethods response |
|
|
Brand for the selected gift card. For example: plastix, hmclub. |
|
|
List of possible brands. For example: visa, mc. |
|
|
The funding source of the payment method. |
|
|
The group where this payment method belongs to. |
The group where this payment method belongs to.
| Property | Type | Description |
|---|---|---|
|
|
The name of the group. |
|
|
Echo data to be used if the payment method is displayed as part of this group. |
|
|
The unique code of the group. |