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.
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).
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","giropay"]
The amount information for the transaction (in minor units). For BIN or card verification requests, set amount to 0 (zero).
List of payment methods to be hidden from the shopper. To refer to payment methods, use their payment method type.
Example: "blockedPaymentMethods":["ideal","giropay"]
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 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.
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.
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.
400 - Bad Request
A problem reading or understanding the request.
401 - Unauthorized
Authentication required.
403 - Forbidden
Insufficient permissions to process the request.
422 - Unprocessable Entity
A request validation error.
500 - Internal Server Error
The server could not process the request.