{"title":"Configuration-based surcharge","category":"default","creationDate":1776961628,"content":"

Using Management API settings, you can configure surcharge rules for your Adyen company or merchant account, store, or individual terminals. Your rules need to take into account all applicable compliance requirements and aspects such as payment method (card brand), funding source, issuing country, and currency.<\/p>\n

Based on the rules you configured, surcharges are then automatically calculated and applied to your in-person payments. In your payment requests, you can use split instructions to define how to book the surcharge amount. <\/p>\n

Depending on your use case<\/a>, you can combine configuration-based surcharge with dynamic surcharge<\/a>.<\/p>\n

Requirements<\/h2>\n

In addition to the general requirements<\/a> for in-person payments with an Adyen for Platforms integration and the general surcharge requirements<\/a>, take into account the following information.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Requirement<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
Integration type<\/strong><\/td>\nConfiguration-based surcharge is supported with:
API credentials<\/a><\/strong><\/td>\nYou must have an API credential with an API key and the following roles<\/a>:
Webhooks<\/a><\/strong><\/td>\nIt is recommended to subscribe to Standard<\/strong> webhooks and enable<\/a> receiving the surcharge amount in AUTHORISATION webhook messages.<\/td>\n<\/tr>\n
Hardware<\/strong><\/td>\nConfiguration-based surcharge is not supported with SFO1<\/strong> terminals or with NYC1 card readers<\/a> (in a Mobile solution).<\/td>\n<\/tr>\n
Limitations<\/strong><\/td>\nNote the following:
Setup steps<\/strong><\/td>\nFor surcharges on Tap to Pay transactions, ask our Support Team<\/a> to enable single tap.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

How it works<\/h2>\n

After the surcharge amounts and\/or percentages are configured<\/a>:<\/p>\n

    \n
  1. \n

    You make a payment request like you normally do. There are no special parameters required to trigger the surcharge.<\/p>\n<\/li>\n

  2. \n

    The payment terminal or mobile device shows a screen with the purchase amount and instructs your user's customer to present their card.<\/p>\n<\/li>\n

  3. \n

    Based on the card that the customer presents, the terminal or Mobile SDK calculates the surcharge using the surcharge amounts and\/or percentages you configured.<\/p>\n<\/li>\n

  4. \n

    Depending on your configuration and solution, the surcharge confirmation screen<\/a> appears. This enables your user's customer to accept the surcharge, or cancel the transaction.<\/p>\n

    \n

    In a Mobile solution or if you choose to skip the confirmation screen, you must provide another form of disclosure.<\/p>\n<\/div>\n<\/li>\n

  5. \n

    If your user's customer accepts the surcharge, the payment is processed and the payment response shows the surcharge amount in the TotalFeesAmount<\/code> field.<\/p>\n<\/li>\n<\/ol>\n

    Configure surcharges<\/h2>\n

    The payment acceptance fee charged to your user depends on the payment method brand (scheme), funding source (credit or debit), currency, and the country\/region that issued the payment method (domestic or international). Therefore, the surcharge that your user passes on to the customer must be specific for the combination of brand, funding source, currency, and country\/region.<\/p>\n

    The surcharge can be a fixed amount for each transaction, a percentage of the sum of the purchase amount and the tip, or both a fixed amount and a percentage. You can configure the surcharge logic for payments based on the agreements you have with your users.<\/p>\n

    In addition, you can:<\/p>\n