Credit surcharge is an additional fee that merchants can add to a transaction when cardholder pays with a credit card. The surcharge helps cover the expenses incurred by the business for processing credit card payments.
triPOS provides two options for surcharging.
As part of this solution, the merchant sets the surcharge amount, which is then sent by the POS Application by setting the
creditSurchargeAmount in the endpoint call to triPOS. Credit surcharge is only allowed for credit transactions
i.e. Sale and Auth. If the transaction satisfies the CREDIT condition, the surcharge fee will be added to the total amount.
The creditSurchargeAmount in the triPOS response will only be present with credit cards and will be absent with debit cards.
Settlement will be processed directly to the merchant account based on the totalAmount.
The capability to ask the cardholder to accept the surcharge is configurable and is set to false by default.
triPOS logs surcharge amount in the Express Surcharge field for Authorization.
Hosted Credit Surcharge (Fee Assist) is a compliant credit surcharge product that allows enrolled merchants to add a fee to
a consumer’s bill when they pay with a credit card.
When the lane configuration parameter isHostedSurchargeEnabled is set to true, and the merchant is enrolled in the Hosted
Credit Surcharge program, the surcharge amount is calculated automatically for the transaction. Both the lane configuration
value set as true and enrollment in the program are required to enable this product. The calculation applies the enrolled
percentage to eligible transactions per compliance regulations. Note: Surcharges are prohibited on Debit transactions and
in some geographies.
In the Sale and Authorization endpoint calls, if the transaction qualifies for a surcharge, triPOS will automatically set
the surcharge amount in creditSurchargeAmount field before send the request for authorization.
Note: : Hosted Credit Surcharge will take precedence over the creditSurchargeAmount passed in on the request if
isHostedSurchargeEnabled is set to true and the merchant includes the credit surcharge amount in the transaction request body.
The option for isHostedSurchargeEnabled is set to false by default.
With either option, a prompt on the terminal to accept or reject the surcharge amount will be presented when the
isConfirmCreditSurchargeScreenDisplayed lane configuration option is set to true. If cardholder rejects when prompted,
the entire transaction will be cancelled.
For either option, with transactions that qualify for surcharge, the totalAmount of the requesed authorization will include the creditSurchargeAmount. For example:
creditSurchargeAmount : 1.00
transactionAmount : 99.00
totalAmount : 100.00
The totalAmount = transactionAmount + creditSurchargeAmount.
The integrator needs to inspect the triPOS response to know whether a transaction qualified and had a credit surcharge
applied. If so, the Merchant and Cardholder receipts are each required to display both the surcharge
amount (creditSurchargeAmount) and the totalAmount as separate line items. For transactions that did not have a surcharge
applied, the surcharge line item on the receipts may either be omitted or have a zero (0.00) amount, and the totalAmount will
be equivalent to the transactionAmount.
Store and Forward mode does not support Hosted Surcharge, because in Store and Forward, transaction runs offline without sending it to a processor. For more information on Store and Forward click here.