POST /cardDetails
Use this endpoint to get information about the card or network token that enables you to decideon the routing of the transaction and the eligibility of the card for the type of transaction.
If you include your supported brands in the request, the response also tells you if you support each brand that was identified on the card.
If you have an API-only integration and collect card data, use this endpoint to find out if the shopper's card is co-branded. For co-branded cards, you must let the shopper choose the brand to pay with if you support both brands.
Servers
- https://checkout-test.adyen.com/v71
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Idempotency-Key |
String | No |
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID). |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
cardNumber |
String | Yes |
A minimum of the first eight digits of the card number. The full card number gives the best result. You must be fully PCI compliant to collect raw card data. |
merchantAccount |
String | Yes |
The merchant account identifier, with which you want to process the transaction. |
supportedBrands[] |
Array | No |
The card brands you support. This is the If not included, our API uses the ones configured for your merchant account and, if provided, the country code. |
countryCode |
String | No |
The shopper country. Format: ISO 3166-1 alpha-2 Example: NL or DE |
encryptedCardNumber |
String | No |
The encrypted card number. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.