Get a list of available payment methods
Retrieves the list of available payment methods for the transaction, based on the transaction information like amount, country, and currency.
Headers
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).
Request body
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.
List of payment methods to be presented to the shopper. To refer to payment methods, use their payment method type.
Example: "allowedPaymentMethods":["ideal","applepay"]
List of payment methods to be hidden from the shopper. To refer to payment methods, use their payment method type.
Example: "blockedPaymentMethods":["ideal","applepay"]
The platform where a payment transaction takes place. This field can be used for filtering out payment methods that are only available on specific platforms. Possible values:
- iOS
- Android
- Web
The shopper's country code.
The merchant account identifier, with which you want to process the transaction.
A unique ID that can be used to associate /paymentMethods and /payments requests with the same shopper transaction, offering insights into conversion rates.
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.
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.
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. The value is case-sensitive and must be at least three characters.
Your reference must not include personally identifiable information (PII) such as name or email address.
Boolean value indicating whether the card payment method should be split into separate debit and credit options.
Required for Adyen for Platforms integrations if you are a platform model. This is your reference (on balance platform) or the storeReference (in the classic integration) for the ecommerce or point-of-sale store that is processing the payment.
Specifies how payment methods should be filtered based on the 'store' parameter:
- 'exclusive': Only payment methods belonging to the specified 'store' are returned.
- 'inclusive': Payment methods from the 'store' and those not associated with any other store are returned.
The shopper's telephone number.
Response
OK - the request has succeeded.