In this section we will cover the sessions that Brite handles. Sessions are created to load the Brite Client and there are five different use-cases:
When the session is created there is a session_token returned in the API that is used when loading the client.
All of these methods also support callbacks for automatic updates of the current session or transaction status.
Session Details #
The Brite API also provides functionality to get the session status and information.
The get session by id API call allows you to get the full information about a session. This will give you the state of the session as well as providing you with a corresponding transaction_id if applicable.
The get session state API call enables you to get the state of an ongoing session in the Brite backend. The session states show how the end user is interacting with the Brite client. This will give you the state of the session as well as providing you with a corresponding transaction_id if applicable.
The session states are the following:
|Session has been created.
|End user has chosen a bank, entered credentials and clicked submit.
|End user has finished authenticating.
|End user is shown the bank account selection view.
|End user has chosen the desired bank account for deposit.
|Deposit transaction is created.
|Only for Swedbank. The end user needs to add Brite to their recipient base.
|Only for Swedbank. The end user has added Brite to their recipient base.
|The end user needs to sign the transaction.
|The end user has signed the transaction.
|Session was aborted for a known reason, see 5.7 Aborted state errors.
|Session failed for unknown reason or was manually failed by Brite.
|The session flow has been completed.
Session Statuses and Details #
There are also API methods to get a list of sessions, export sessions and search for sessions.
For a complete guide on methods available have a look at the API reference.