Supported callback
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
Retry callback
Retry callback
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
transactionId
The transaction ID received from the partner gateway. Corresponds to the merchant_transaction_id in the decline API.
buyerId
buyerId
The buyer ID received from the partner gateway. Corresponds to the buyer.buyer_id in the decline API.
retryId
retryId
A unique identifier for the retry request. This must be used in the retry response API after performing the retry.
Abandoned transaction callback
Abandoned transaction callback
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
transactionId
The transaction ID received from the partner gateway. Corresponds to the merchant_transaction_id in the decline API.