Stripe Merchants
Stripe Callback
Supported Callbacks
Bounce can send callbacks to notify merchants of specific events:Retry callback
Retry callback
When Bounce approves a transaction, it creates a retry schedule. At each scheduled time, Bounce notifies the merchant that a retry attempt is required using the following schema:
transactionId
transactionId
The transaction ID received from the merchant. Corresponds to the merchant_transaction_id in the decline API.
buyerId
buyerId
The buyer ID received from the merchant. Corresponds to the buyer.buyer_id in the decline API.
paymentMethodId
paymentMethodId
The payment method ID received from the merchant.
retryId
retryId
A unique identifier for the retry request. This must be used in the retry response API after performing the retry.
Successful Retry Attempt callback
Successful Retry Attempt callback
This callback notifies you when Bounce creates a new transaction, providing both the new transaction ID and the original declined transaction ID.
originalTransaction
originalTransaction
The transaction ID received from the merchant. Corresponds to the merchant_transaction_id in the decline API.
successfulRetryTransaction
successfulRetryTransaction
The payment system’s transaction ID for the successful retry transaction.
Abandoned Transaction callback
Abandoned Transaction callback
After approving a transaction, Bounce attempts retries for a specific period. If this period expires without a successful retry, Bounce sends this callback to notify that no further retries will occur. For guaranteed transactions, this indicates that reimbursement is due.
transactionId
transactionId
The transaction ID received from the merchant. Corresponds to the merchant_transaction_id in the decline API.
paymentMethodId
paymentMethodId
The payment method ID received from the merchant.