Getting Started
Direct Merchant Integration
- Braintree Merchants
- Stripe Merchants
- Generic integration
- PayPal Integration
Gateway partners
- Gateway partners integration
Stripe Callback
Supported Callbacks
Bounce can send callbacks to notify merchants of specific events:
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": "ch_aB3dE5fG7HjK2lM9nOpQ",
"buyerId": "Xy1Z2wV3uT4rS5qP6oN7",
"paymentMethodId": "pm_aB3dE5fG7HjK2lM9",
"retryId": "Lm8N9oP0qR1sT2uV3wX4"
}
The transaction ID received from the merchant. Corresponds to the merchant_transaction_id in the decline API.
The buyer ID received from the merchant. Corresponds to the buyer.buyer_id in the decline API.
The payment method ID received from the merchant.
A unique identifier for the retry request. This must be used in the retry response API after performing the retry.
This callback notifies you when Bounce creates a new transaction, providing both the new transaction ID and the original declined transaction ID.
{
"originalTransaction": "ch_aB3dE5fG7HjK2lM9nOpQ",
"successfulRetryTransaction": "ch_Xy1Z2wV3uT4rS5qP6oN7"
}
The transaction ID received from the merchant. Corresponds to the merchant_transaction_id in the decline API.
The payment system’s transaction ID for the successful retry transaction.
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": "ch_aB3dE5fG7HjK2lM9nOpQ",
"paymentMethodId": "pm_E5fGM9nO3dE5fGG7HjK2"
}
The transaction ID received from the merchant. Corresponds to the merchant_transaction_id in the decline API.
The payment method ID received from the merchant.