Custom Fees

Custom fees allow partners to specify a fee above the normal fee for a particular transaction. The custom fee can be used where additional factors, such as higher risk or specialized transactions, can occur.

For example, custom fees can be used:

Foreign transactions, recurring transactions, or where additional risks associated with the transaction exist.
Transaction amount threshold is reached, such as transactions greater than $250.
The custom fee feature is available through the Stax API.

Custom fees can be used where the following conditions apply:

Custom fees must be activated on the Partner account.
The transaction can not be a surcharge.
A merchant account is not a Trust Account.
Custom fees cannot be greater than the transaction total.
Custom fees can not be used for Google or Apple Pay or when a card is present on the transaction.

A custom fee can be used when the partner provides value-added services or to mitigate increased risks associated with associated transactions.

if any of the above conditions are not met, the custom fee passed into the request will NOT be used, and the response will return a meta.customFeeMessage with the reason the custom fee was not used.

IMPORTANT: To certify a Custom Fees implementation, you must communicate to the merchant that additional fees are assessed based on how the merchant processes payments.

Return Values for meta.customFeeMessage

Message	Description
Custom fee not used, unsupported brand.	The partner does not have custom fees enabled
Custom fee not used, defaulting to a minimum fee.	The custom fee passed in is insufficient to cover the minimum fee.
Custom fees are not used; trust accounts do not support custom fees.	Accounts that have a trust pricing plan cannot use custom fees.
Custom fees are not used, and sources are not allowed.	Custom fees are not supported with things like GooglePay, ApplePay, BBPOS, etc.'
Custom fee not used, surcharged transaction.	Merchants who have surcharges enabled cannot use a custom fee.
The custom fee is not used; the custom fee is higher than the transaction total.	The custom fee passed in is higher than the transaction total.

Note: In cases where the custom fee message returns because the transaction did not qualify for a custom fee, the transaction may have still succeeded. A transaction not qualifying for a custom fee will not prevent a transaction from being sent.