- BFinance checks your card program configuration and card status: BFinance checks the card status and predefined configurations before sending an authorization request to your server as a webhook.
- BFinance sends the authorization request: Authorization Webhook
- Your server makes a decision: Based on your internal rules, such as balance checks or spending controls, your server decides whether to approve or reject the transaction.
- You respond to BFinance: You send your decision to BFinance via HTTPS response within 1.2 seconds.
- BFinance checks your balance: Before sending your solution to the card processor, BFinance checks your card program balance to make sure it can cover the transaction.
- BFinance completes processing: BFinance sends your decision to the card processor to approve or reject the transaction.
- The transaction webhook is triggered: Transaction
Partner-managed Auhorization
Authorization Flow
How partner-managed authorization works end-to-end.
Once setup is complete, your card program is ready for cardholders to start making purchases. In this guide, we’ll walk you through how transactions are authorized, using a real-world example to illustrate the authorization process in real time.
When a cardholder uses their card:

