- Raw card data<\/a><\/li>
- Encrypted card data<\/a><\/li><\/ul><\/td>\n<\/tr>\n
\n API credential roles<\/a><\/strong><\/td>\n You need an API credential with an API key and the Checkout webservice role<\/strong>.<\/td>\n <\/td>\n<\/tr>\n \n Webhooks<\/a><\/strong><\/td>\n Subscribe to Standard webhooks.<\/td>\n <\/td>\n<\/tr>\n \n Limitations<\/strong><\/td>\n Make sure that you take into account the following: - The surcharge feature is in pilot, and restrictions may apply. Reach out to your Adyen contact to be part of the pilot.<\/li>
- Surcharges cannot be applied to authorization adjustments<\/a> or overcaptures<\/a>. The surcharge amount cannot be higher than the surcharge amount that was shown to the customer at the moment of purchase.<\/li><\/ul><\/td>\n<\/tr>\n
\n Setup steps<\/strong><\/td>\n Before you begin: - Make sure you comply with the general and regional compliance requirements mentioned in our Surcharge compliance guide<\/a>.<\/li>
- We recommend consulting your own legal advisor on compliance with regulatory requirements, and reviewing the scheme rules for the latest information.<\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Compliance<\/h2>\n
How it works<\/h2>\n
When your shopper proceeds to pay:<\/p>\n
- \n
- Collect the shopper's card details on your checkout page.<\/li>\n
- From your server, make a \/cardDetails<\/a> request using the shopper's card details, to get the information that helps to make a decision about the surcharge.<\/li>\n
- Implement logic to decide if a surcharge is allowed, and to calculate the surcharge amount, using the data from the \/cardDetails<\/a> response.<\/li>\n
- Display the surcharge amount on your checkout page.<\/li>\n
- When the shopper proceeds to pay, from your server, make a \/payments<\/a> request that includes the surcharge amount.<\/li>\n<\/ol>\n
Get card details<\/h2>\n
Use the customer's raw or encrypted card number to make an API request that retrieves the details of the card that helps to determine whether you can apply surcharge to a payment.<\/p>\n
- \n
- \n
In your payment form, collect the card number of the customer with either of the following:<\/p>\n
- \n
- Custom payment form to collect raw card data<\/a><\/li>\n
- Custom Card Component integration to collect encrypted card data<\/a><\/li>\n<\/ul>\n<\/li>\n
- \n
From your server, make a \/cardDetails<\/a> request, including:<\/p>\n
\n \n - Custom Card Component integration to collect encrypted card data<\/a><\/li>\n<\/ul>\n<\/li>\n
- Custom payment form to collect raw card data<\/a><\/li>\n
- Implement logic to decide if a surcharge is allowed, and to calculate the surcharge amount, using the data from the \/cardDetails<\/a> response.<\/li>\n
- We recommend consulting your own legal advisor on compliance with regulatory requirements, and reviewing the scheme rules for the latest information.<\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
- Make sure you comply with the general and regional compliance requirements mentioned in our Surcharge compliance guide<\/a>.<\/li>
- Encrypted card data<\/a><\/li><\/ul><\/td>\n<\/tr>\n
![\"Conditionally](\"\/user\/pages\/reuse\/image-library\/01.icons\/conditionally-required\/conditionally-required.svg?decoding=auto&fetchpriority=auto\")
<\/span><\/td>\n![\"Required\"](\"\/user\/pages\/reuse\/image-library\/01.icons\/required\/required.svg?decoding=auto&fetchpriority=auto\")
<\/span><\/td>\n