Trustap uses a payment model where end-users pay a small fee to add Trustap's protection to their transactions. Trustap does not charge third-party clients to integrate Trustap into their services.

This section details how the Trustap fee should be retrieved and handled when using the TrustAPI.

Handling Trustap Pricing

With the TrustAPI, Trustap's fees are calculated when a transaction begins, before payment has been made. This allows users to know ahead of time how much it will cost to use Trustap for a particular transaction.

In general, handling the pricing of a Trustap transaction consists of 3 steps:

  1. Retrieve Trustap's fees using a plain get request (note that this will require an active access token). For example:
curl \
-H "Authorization: Bearer $access_token" \
  1. Show the fees to the user.
  2. Create a new transaction (or update an existing transaction) by adding the fields provided by the call to /api/v1/charge to a transaction creation/update request.

Model Endpoints

The online model and the face-to-face model use different endpoints for calculating fees:

Charge Calculator Version

The /charge endpoints return an additional charge_calculation_version field. This field is useful for the rare occasions where Trustap changes its pricing calculation, in which case the client can be notified that such a change has occurred, instead of the request simply failing due to a discrepancy in the charge value.