---
title: "Dynamic surcharge"
description: "Provide the surcharge amount in your Terminal API request."
url: "https://docs.adyen.com/point-of-sale/surcharge/dynamic"
source_url: "https://docs.adyen.com/point-of-sale/surcharge/dynamic.md"
canonical: "https://docs.adyen.com/point-of-sale/surcharge/dynamic"
last_modified: "2026-06-01T15:33:14+02:00"
language: "en"
---

# Dynamic surcharge

Provide the surcharge amount in your Terminal API request.

[View source](/point-of-sale/surcharge/dynamic.md)

If you want to be in full control of surcharges, you can specify the surcharge amount in your in-person payment request. We refer to this as dynamic surcharge. To calculate the surcharge amount, you can use a third-party service or create your own calculation logic. If you accept ecommerce as well as point-of-sale payments, you can use the same calculation logic for both sales channels, taking into account all applicable compliance requirements.

Depending on your [use case](/point-of-sale/surcharge#surcharge-methods), you can combine dynamic surcharge with [configuration-based surcharge](/point-of-sale/surcharge/configuration).

## Requirements

In addition to the general [surcharge requirements](/point-of-sale/surcharge#requirements), take into account the following information.

| Requirement                                                   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| ------------------------------------------------------------- |   |
| **Integration type**                                          | Dynamic surcharge is supported with a [Terminal API integration](/point-of-sale/design-your-integration/) with payment terminals on terminal software version **1.118** or later.                                                                                                                                                                                                                                                                                                                                                                                                     |
| **[API credentials](/development-resources/api-credentials)** | To configure showing the [surcharge confirmation screen](/point-of-sale/surcharge#surcharge-confirmation-screen), you must have an API credential with an API key and the following [roles](/development-resources/api-credentials#api-permissions):- Management API—Terminal settings read
- Management API—Terminal settings read and writeIf you have a Terminal API integration with [cloud-based communications](/point-of-sale/design-your-integration/choose-your-architecture#cloud-communications), you can use the existing API key that you use for Terminal API requests. |
| **[Webhooks](/development-resources/webhooks)**               | It is recommended to subscribe to **Standard** webhooks and [enable](/point-of-sale/surcharge#surcharge-in-authorisation-webhooks) receiving the surcharge amount in AUTHORISATION webhook messages.                                                                                                                                                                                                                                                                                                                                                                                  |
| **Limitations**                                               | Requests to live Management API endpoints related to terminal settings are subject to [rate limits](/point-of-sale/automating-terminal-management#rate-limits-in-the-live-environment).                                                                                                                                                                                                                                                                                                                                                                                               |
| **Setup steps**                                               | Before you start:- [Enable receiving the issuer country/region](/point-of-sale/card-acquisition/identifiers) in API responses and webhook messages.
- Ask our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) to enable single tap.                                                                                                                                                                                                                                                                                                                |

## How it works

To use dynamic surcharge:

1. Design the customer experience. We recommend the following:

   * To inform customers about the changed amount after the surcharge is calculated, [configure showing](#show-confirmation) the [surcharge confirmation screen](/point-of-sale/surcharge#surcharge-confirmation-screen). If you hide this screen, regulations require you to provide another form of surcharge disclosure.

   * Use the single tap flow. This means that for contactless payments, customers do not need to tap again when they confirm they accept the surcharge. Contact our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) to enable single tap.

2. To get the details that are needed to calculate the surcharge amount, you [make a card acquisition request](#card-acquisition-request). These details include, for example, the transaction amount and currency, card brand, funding source, and issuing country of the card.

   Note the following:

   * In Australia the surcharge compliance requirements are simple enough that you can consider skipping card acquisition.

   * Also note that Mobile solutions currently do not support card acquisition.

3. On the payment terminal, a payment screen appears and the customer taps, inserts, or swipes their card.

4. When you receive the card acquisition response, you pass the details for the surcharge calculation to your own surcharge calculation logic or to the third-party surcharge calculation service.

5. When you get the calculated surcharge amount from your own system or the third party, you [make a payment request with the surcharge amount](#payment-with-surcharge) as the `surchargeFee` in the `SaleToAcquirerData`. The payment request must also refer to the card acquisition.

6. The surcharge confirmation screen appears. This enables the customer to accept the surcharge, or cancel the transaction.

   In a Mobile solution or if you configured to skip this Adyen-provided confirmation screen, you must provide another form of disclosure.

7. If the customer accepts the surcharge, the payment is processed and the payment response shows the surcharge amount in the `TotalFeesAmount` field.

## Show the confirmation screen

Adyen provides a surcharge confirmation screen that appears on the payment terminal to let the customer review and accept the surcharge, or cancel the transaction. You can configure this screen to be skipped. But if you do, you must provide another form of disclosure.

To configure showing or hiding the surcharge confirmation screen:

1. Optionally, check the current setting for the surcharge confirmation screen by making a GET request to the `/terminalSettings` endpoint for the [company account](https://docs.adyen.com/api-explorer/Management/latest/get/companies/\(companyId\)/terminalSettings), [merchant account](https://docs.adyen.com/api-explorer/Management/latest/get/merchants/\(merchantId\)/terminalSettings), [store](https://docs.adyen.com/api-explorer/Management/latest/get/stores/\(storeId\)/terminalSettings) or [terminal](https://docs.adyen.com/api-explorer/Management/latest/get/terminals/\(terminalId\)/terminalSettings). Check the `surcharge.askConfirmation` parameter.

2. Make a PATCH request to the `/terminalSettings` endpoint for the [company account](https://docs.adyen.com/api-explorer/Management/latest/get/companies/\(companyId\)/terminalSettings), [merchant account](https://docs.adyen.com/api-explorer/Management/latest/get/merchants/\(merchantId\)/terminalSettings), [store](https://docs.adyen.com/api-explorer/Management/latest/get/stores/\(storeId\)/terminalSettings) or [terminal](https://docs.adyen.com/api-explorer/Management/latest/get/terminals/\(terminalId\)/terminalSettings).\
   In the request body, specify a [surcharge](https://docs.adyen.com/api-explorer/Management/latest/patch/companies/\(companyId\)/terminalSettings#request-surcharge) object with the following parameter:

   | Parameter                                                                                                                                                 | Data type | Description                                                                                                                          |
   | --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------ |
   | [askConfirmation](https://docs.adyen.com/api-explorer/Management/latest/patch/companies/\(companyId\)/terminalSettings#request-surcharge-askConfirmation) | Boolean   | Indicates whether to show (**true**) or hide (**false**) the [surcharge confirmation screen](#how-it-works) on the payment terminal. |

   **Show the surcharge confirmation screen**

   ```bash
   curl https://management-test.adyen.com/v3/stores/{storeId}/terminalSettings \
   -H 'x-API-key: YOUR_X-API-KEY' \
   -X PATCH \
   -d '{
       "surcharge": {
           "askConfirmation": true
       }
   }'
   ```

3. Note that the response returns the setting for the surcharge confirmation screen as well as all other terminal settings at the level where you made the request.

## 1. Make a card acquisition request

To calculate the surcharge amount, you need to know certain details. For example, if the customer is using a credit or debit card, and where the card was issued.

We recommend getting these details through a card acquisition request. The response provides the details of the card that the customer presents to the payment terminal.

1. Make a [Terminal API](/point-of-sale/design-your-integration/terminal-api) card acquisition request, specifying:

   * The standard [`SaleToPOIRequest.MessageHeader` ](/point-of-sale/design-your-integration/terminal-api#request-message-header)object, with `MessageClass` set to **Service** and `MessageCategory` set to **CardAcquisition**.

     | Parameter         | Required                                                                                    | Description                                                                                                                                                 |
     | ----------------- | ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
     | `ProtocolVersion` | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | **3.0**                                                                                                                                                     |
     | `MessageClass`    | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | **Service**                                                                                                                                                 |
     | `MessageCategory` | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | **CardAcquisition**                                                                                                                                         |
     | `MessageType`     | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | **Request**                                                                                                                                                 |
     | `ServiceID`       | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | Your unique ID for this request, consisting of 1-10 alphanumeric characters. Must be unique within the last 48 hours for the terminal (`POIID`) being used. |
     | `SaleID`          | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | Your unique ID for the POS system component to send this request from.                                                                                      |
     | `POIID`           | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The unique ID of the terminal to send this request to. Format: *\[device model]-\[serial number]*.                                                          |

   - The [CardAcquisitionRequest](https://docs.adyen.com/api-explorer/terminal-api/latest/post/cardacquisition) object with:

     | Parameter                    | Required                                                                                    | Description                                                                                                                                                                                                                                                        |
     | ---------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
     | `SaleData.SaleTransactionID` | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | An object with:- `TransactionID`: Your reference to identify a payment. We recommend using a unique value per payment.
     - `TimeStamp`: The date and time of the request in [UTC format](https://en.wikipedia.org/wiki/ISO_8601#Coordinated_Universal_Time_\(UTC\)). |
     | `CardAcquisitionTransaction` | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | An object with:- `TotalAmount`: The amount due for the goods or services that the customer wants to purchase.                                                                                                                                                      |

   The examples show a card acquisition when the customer wants to purchase USD 620.00 worth of goods or services.

   **Simple card acquisition request**

   ```json
   {
       "SaleToPOIRequest":
           "MessageHeader": {
               "ProtocolVersion": "3.0",
               "MessageClass": "Service",
               "MessageCategory": "CardAcquisition",
               "MessageType": "Request",
               "ServiceID": "797",
               "SaleID": "POSSystemID12345",
               "POIID": "V400m-324688179"
           },
           "CardAcquisitionRequest": {
               "SaleData": {
                   "SaleTransactionID": {
                       "TransactionID": "369",
                       "TimeStamp": "2026-01-05T15:57:06.973Z"
                   }
               },
               "CardAcquisitionTransaction": {
                   "TotalAmount": 620.00
               }
           }
       }
   }
   ```

   When the card acquisition succeeds, the response contains a `message` of **CARD\_ACQ\_COMPLETED** in the `AdditionalResponse`.

   **Card acquisition response**

   ```json
   {
       "SaleToPOIResponse": {
           "CardAcquisitionResponse": {
               "POIData": {
                   "POIReconciliationID": "1000",
                   "POITransactionID": {
                       "TimeStamp": "2026-01-05T15:57:20.465Z",
                       "TransactionID": "BV0q001767628639000"
                   }
               },
               "PaymentInstrumentData": {
                   "CardData": {
                       "CardCountryCode": "840",
                       "MaskedPan": "600007 **** 7003",
                       "PaymentBrand": "mc",
                       "SensitiveCardData": {
                           "ExpiryDate": "0330"
                       }
                   },
                   "PaymentInstrumentType": "Card"
               },
               "Response": {
                   "AdditionalResponse": "PaymentAccountReference=t9BVKrTbgJT11Igro8dtfsmUVrLnL&alias=P601291289070502&aliasType=Default&backendGiftcardIndicator=false&cardBin=600007&cardHolderName=S%2Hopper&cardIssuerCountryId=840&cardIssuingBank=Adyen%20TEST&cardScheme=mc&cardSummary=7003&cardType=mc&dcc.dccRefusalReason=Currencies%20are%20the%20same&expiryMonth=03&expiryYear=2030&fundingSource=CREDIT&giftcardIndicator=false&isCardCommercial=false&iso8601TxDate=2026-01-05T15%3a57%3a20.465Z&issuerCountry=US&merchantReference=577&message=CARD_ACQ_COMPLETED&paymentMethod=mc&paymentMethodVariant=mccredit&posAmountCashbackValue=0&posAmountGratuityValue=0&posAuthAmountCurrency=USD&posAuthAmountValue=62000&posEntryMode=ICC&posOriginalAmountValue=62000&posadditionalamounts.originalAmountCurrency=USD&posadditionalamounts.originalAmountValue=62000&shopperCountry=US&store=YOUR_STORE&tid=47069832&transactionType=GOODS_SERVICES&txdate=05-01-2026&txtime=16%3a57%3a20",
                   "Result": "Success"
               },
               "SaleData": {
                   "SaleTransactionID": {
                       "TimeStamp": "2026-01-05T15:57:06.973Z",
                       "TransactionID": "577"
                   }
               }
           },
           "MessageHeader": {
               "MessageCategory": "CardAcquisition",
               "MessageClass": "Service",
               "MessageType": "Response",
               "POIID": "V400m-324688179",
               "ProtocolVersion": "3.0",
               "SaleID": "POSSystemID12345",
               "ServiceID": "979"
           }
       }
   }
   ```

2. From the [CardAcquisitionResponse](https://docs.adyen.com/api-explorer/terminal-api/latest/post/cardacquisition#responses-200-Response), get the details that are needed for the surcharge calculation. Also get the `POITransactionID` details, which you will need to specify later in your payment request.

   | Parameter                        | Usage                                                                                                                                                                           |
   | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | `POIData.POITransactionID`       | Keep the `TimeStamp` and `TransactionID`, because you need these card acquisition details in your payment request.                                                              |
   | `PaymentInstrumentData.CardData` | Includes details you may need for the surcharge calculation:- `CardCountryCode`: The three-digit code of the issuer country/region.
   - `PaymentBrand`: The type of payment card. |
   | `Response.AdditionalResponse`    | Includes details you may need for the surcharge calculation.                                                                                                                    |

   As an example, the `AdditionalResponse` from the `CardAcquisitionResponse` above includes the following details that can be useful for the surcharge calculation:

   | Parameter + value               | Description                                                                                                                                           |
   | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
   | `cardIssuerCountryId=840`       | The three-digit code of the issuer country/region.                                                                                                    |
   | `cardScheme=mc`                 | The card scheme.                                                                                                                                      |
   | `cardType=mc`                   | The card type.                                                                                                                                        |
   | `fundingSource=CREDIT`          | The funding source used for the transaction, such as a credit, debit, prepaid, or charge card. In other words: where the customer's money comes from. |
   | `isCardCommercial=false`        | Indicates if this is a commercial card or a consumer card. When **true**, it is a commercial card. When **false**, it is a consumer card.             |
   | `issuerCountry=US`              | The two-letter code of the issuer country/region.                                                                                                     |
   | `paymentMethod=mc`              | The payment method on the brand or scheme level.                                                                                                      |
   | `paymentMethodVariant=mccredit` | The payment method on the product level.                                                                                                              |
   | `posAuthAmountCurrency=USD`     | The three-letter code of the transaction currency.                                                                                                    |
   | `posAuthAmountValue=62000`      | The transaction amount in minor units.                                                                                                                |
   | `posOriginalAmountValue=62000`  | The transaction amount before surcharge, gratuity, adjustments, and such (if any).                                                                    |
   | `shopperCountry=US`             | The two-letter code of the customer's country/region.                                                                                                 |

   If the `AdditionalResponse` doesn't include the expected details, check if you enabled receiving those details. Refer to [Receive identifiers](/point-of-sale/card-acquisition/identifiers#receiving-identifiers-in-responses).

3. Pass the relevant details to your own surcharge calculation system or to your third-party surcharge calculation service.

## 2. Add a surcharge to the payment request

When you have received the calculated surcharge amount from your own system or the third-party surcharge calculation service, make a Terminal API payment request with the surcharge amount specified using the `surchargeFee` field inside `SaleToAcquirerData`.

In the following example, a surcharge of USD 6.00 is added to an original amount of USD 620.00.

1. Format a string in one of the following ways, using `surchargeFee` as the parameter and the calculated surcharge amount as the value.

   Do not use minor units for the surcharge amount.

   * **Option 1**: as a JSON object converted to a Base64-encoded string.

     **Surcharge in JSON format**

     ```json
     {
        "additionalData": {
           "surchargeFee": "6.00"
        }
     }
     ```

     Note that the surcharge amount must be specified as a string value, not as a numeric value.

     **Converted to Base64**

     ```raw
     ewogICAiYWRkaXRpb25hbERhdGEiOiB7CiAgICAgICJzdXJjaGFyZ2VGZWUiOiAiNi4wMCIKICAgfQp9
     ```

   * **Option 2**: as a string consisting of a key-value pair.

     **Surcharge as a key-value pair**

     ```raw
     surchargeFee=6.00
     ```

   You will send the resulting string in the `SaleToAcquirerData`.

2. Make a [Terminal API](/point-of-sale/design-your-integration/terminal-api) payment request, specifying:

   * The standard [`SaleToPOIRequest.MessageHeader` ](/point-of-sale/design-your-integration/terminal-api#request-message-header)object, with `MessageClass` set to **Service** and `MessageCategory` set to **Payment**.

     | Parameter         | Required                                                                                    | Description                                                                                                                                                 |
     | ----------------- | ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
     | `ProtocolVersion` | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | **3.0**                                                                                                                                                     |
     | `MessageClass`    | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | **Service**                                                                                                                                                 |
     | `MessageCategory` | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | **Payment**                                                                                                                                                 |
     | `MessageType`     | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | **Request**                                                                                                                                                 |
     | `ServiceID`       | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | Your unique ID for this request, consisting of 1-10 alphanumeric characters. Must be unique within the last 48 hours for the terminal (`POIID`) being used. |
     | `SaleID`          | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | Your unique ID for the POS system component to send this request from.                                                                                      |
     | `POIID`           | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The unique ID of the terminal to send this request to. Format: *\[device model]-\[serial number]*.                                                          |

   - The [PaymentRequest](https://docs.adyen.com/api-explorer/terminal-api/latest/post/payment) object with:

     | Parameter                              | Required                                                                                    | Description                                                                                                                                                                                                                                                               |
     | -------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
     | `SaleData.SaleTransactionID`           | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | An object with:- `TransactionID`: Your reference to identify a payment. We recommend using a unique value per payment.
     - `TimeStamp`: The date and time of the request in [UTC format](https://en.wikipedia.org/wiki/ISO_8601#Coordinated_Universal_Time_\(UTC\)).        |
     | `SaleData.SaleToAcquirerData`          |                                                                                             | The formatted string specifying the surcharge.                                                                                                                                                                                                                            |
     | `PaymentTransaction.AmountsReq`        | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | An object with:- `Currency`: The transaction [currency](/development-resources/currency-codes).
     - `RequestedAmount`: The transaction amount due for the goods or services, without surcharge, gratuity, or any other adjustment.                                          |
     | `PaymentData.CardAcquisitionReference` | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | An object referring to the card acquisition:- `TimeStamp`: The time stamp returned in the `POIData.POITransactionID` of the card acquisition response.
     - `TransactionID`: The transaction ID returned in the `POIData.POITransactionID` of the card acquisition response. |

   **Payment request with surcharge**

   ```json
   {
      "SaleToPOIRequest": {
         "MessageHeader": {
            "ProtocolVersion": "3.0",
            "MessageClass": "Service",
            "MessageCategory": "Payment",
            "MessageType": "Request",
            "SaleID": "POSSystemID12345",
            "ServiceID": "0207111104",
            "POIID": "V400m-324688179"
         },
         "PaymentRequest": {
            "SaleData": {
               "SaleTransactionID": {
                  "TransactionID": "27908",
                  "TimeStamp": "2026-01-05T15:59:49.294Z"
               },
               "SaleToAcquirerData": "surchargeFee=6.00"
            },
            "PaymentTransaction": {
               "AmountsReq": {
                  "Currency": "USD",
                  "RequestedAmount": 620.00
               }
            },
            "PaymentData": {
               "CardAcquisitionReference": {
                  "TimeStamp": "026-01-05T15:57:20.465Z",
                  "TransactionID": "BV0q001767628639000"
               }
            }
         }
      }
   }
   ```

3. In the [PaymentResponse](https://docs.adyen.com/api-explorer/terminal-api/latest/post/payment#responses-200) note the following:

   * `PaymentResult.AmountsResp`:

     * `TotalFeesAmount`: The surcharge amount.
     * `AuthorizedAmount`: The total authorized amount, consisting of the original amount plus the surcharge amount.

   * `Response.AdditionalResponse`:

     * `posAuthAmountValue`: The total authorized amount in minor units.
     * `surchargeAmount`: The surcharge amount in minor units.

   **Payment response**

   ```json
   {
       "SaleToPOIResponse": {
           "MessageHeader": {...},
           "PaymentResponse": {
               "POIData": {
                   "POIReconciliationID": "1000",
                   "POITransactionID": {
                       "TimeStamp": "2026-01-06T11:27:24.575Z",
                       "TransactionID": "BV0q001767698805001.SWF7F9NR99LJCK75"
                   }
               },
               "PaymentReceipt": [...],
               "PaymentResult": {
                   "AmountsResp": {
                       "AuthorizedAmount": 626,
                       "Currency": "USD",
                       "TotalFeesAmount": 6
                   },
                   ...
                   "PaymentInstrumentData": {
                       "CardData": {
                           "CardCountryCode": "840",
                           "EntryMode": [
                               "ICC"
                           ],
                           "MaskedPan": "600007 **** 7003",
                           "PaymentBrand": "mc",
                           "SensitiveCardData": {
                               "CardSeqNumb": "23",
                               "ExpiryDate": "0330"
                           }
                       },
                       "PaymentInstrumentType": "Card"
                   }
               },
               "Response": {
                   "AdditionalResponse": "...cardIssuerCountryId=840&cardScheme=mc&ccardType=mc&fundingSource=CREDIT&isCardCommercial=false&issuerCountry=US&paymentMethod=mc&paymentMethodVariant=mccredit...&posAuthAmountCurrency=USD&posAuthAmountValue=62600&posOriginalAmountValue=62000&posadditionalamounts.originalAmountCurrency=USD&posadditionalamounts.originalAmountValue=62000...shopperCountry=US...&surchargeAmount=600...",
                   "Result": "Success"
               },
               "SaleData": {...}
               }
           }
       }
   }
   ```

## See also

* [Surcharge compliance guide](/development-resources/surcharge-compliance)
* [Configuration-based surcharge](/point-of-sale/surcharge/configuration)
* [Card acquisition](/point-of-sale/card-acquisition)
* [Use API calls to configure terminals](/point-of-sale/automating-terminal-management/configure-terminals-api)
