post https://your.custom.endpoint.com/account_balance/clientcustomendpoint
Overview
The platform can use this callback to receive the updated balance of the consumer (receiving entity) after a successful credit or when a debit happens towards a refund or settlement. This callback helps the platform maintain a running balance after each transaction. If you are looking only for the latest balance, you can also use Decentro's merchant dashboard against a consumer to see the latest balance.
A balance callback due to a credit transaction can be received for the below scenarios.
- Generate payment link API
- Issue Collect Request
- Generate Dynamic QR
- Static QR Code (Under development)
- Virtual Account based collections (Under development)
A balance callback due to a debit transaction can be received for the below scenarios.
- Refund API
- Settlement-related debit to the platform's bank account
Flow
Below is the flow for receiving the callback.
- The platform asks Decentro to configure an endpoint against which the balance callbacks will be triggered by dropping a mail at [email protected]
- The platform creates a payment request, and a successful transaction is processed through any of the support models mentioned above
- Decentro triggers a balance callback to the configured endpoint after the Terminal Transaction Status Callback/Webhook is triggered with type = CREDIT.
- The platform initiates a refund request against a transaction using the Refund API. The callback is also triggered with type = DEBIT in such a scenario.
- Decentro initiates a settlement to the platform's bank account per the settlement schedule. The callback is also triggered with type = DEBIT in such a scenario.
The platform can use the decentroTxnId parameter from the original transaction initiation to map the balance at its end.