Skip to main content

​
Bounce integrates with Gateway Partners

The integration between Bounce and a Partner Gateway consists of two parts:
  • The Partner Gateway integrates with Bounce’s API (see API specification below)
  • The Partner Gateway creates endpoints to support Bounce’s callbacks for retries and abandoned transactions

​
Bounce Callback Schemas

When Bounce approves a transaction, it creates a retry schedule. At each scheduled time, Bounce notifies partners that a retry attempt is required using the following schema:
{
    "transactionId": "aB3dE5fG7HjK2lM9nOpQ",
    "buyerId": "Xy1Z2wV3uT4rS5qP6oN7",
    "retryId": "Lm8N9oP0qR1sT2uV3wX4"
}
The transaction ID received from the partner gateway. Corresponds to the merchant_transaction_id in the decline API.
The buyer ID received from the partner gateway. Corresponds to the buyer.buyer_id in the decline API.
A unique identifier for the retry request. This must be used in the retry response API after performing the retry.
After Bounce approves a transaction, it attempts retries for a specific period. If this period elapses without a successful retry, Bounce sends this callback to notify the Gateway Partner that no further retries will occur. For guaranteed transactions, this indicates that reimbursement is due.
{
    "transactionId": "Qw3Er4Ty5Ui6Op7As8Df"
}
The transaction ID received from the partner gateway. Corresponds to the merchant_transaction_id in the decline API.
⌘I