Brite Instant Payments are built with a conversion-first approach, allowing you to gain full insights into your end user’s behaviour and giving you full control to tailor the end-user experience to your needs. Through direct connections to the bank APIs, Brite Deposit lets your end users deposit/pay instantly from their bank using only top-of-mind information.
The deposit API enables the merchant to initiate a payment session towards Brite. In the response to creating the deposit, the merchant will receive a session_token that will be used to render the Brite javascript client, as well as a session_id that can be used to get information on the ongoing session.
When creating a deposit session make sure to subscribe to the session callbacks as well as the transaction callbacks to get updates about the status and get information if it will be successful or fail.
One of the fields in the create_API call is “approval_required“. If this is set to true, sessions created will have to be approved by the merchant before going through. This enables the merchant to make an internal check of the customer before approving their deposit session.
Since there are markets where we don’t have a third-party KYC provider, merchants must provide Brite with customer information.
The following API calls are referenced here:
