Direct Connection Users

You can ask users to connect to open banking on your own product via the D•One co-branded Direct Connection journey. The user journey begins on your product. The user is then asked to connect on the D•One co-branded connection journey, and is then retuned to your product.

⚠️

Be aware

If you're integrating via a marketplace, you won't need to manage this journey—it's handled entirely by the marketplace. Please visit marketplace integration page.

The user flow

The journey begins when you ask a user to connect their bank account on your product. They will be directed to the D•One co-branded Direct Connection journey which features your branding colours and logo. In this flow, they will provide consent, and connect their bank account. They will then be redirected back to your product.

Integrating the Direct Connection journey

In order to launch a Direct Connection journey, you must create a user and then create a session. The session creates a connectionURL which the user is directed to in order for them to connect their bank account.

Users

A User object represents a user and should be reused whenever performing actions against the D•One API for the same
individual.

Sessions

Sessions are short lived objects representing a user journey on the D•One Open Banking journey. When a session is created two URLs are returned. A user should be redirected to one of these two URLs depending on what journey they are undertaking.
The two URLs returned are as follows:

• connectionUrl
  • This is recommended if this is the user's first time using our service as it will take them through connecting a bank account for the first time.
• managementUrl
  • This is recommended if this is not the user's first time using our service as it will take them directly to a list of their current Open Banking connections. The user can then add more bank accounts, re-authenticate their bank accounts, or unlink current connected bank accounts.

The URLs will have a partnerToken attached to the query string which is used to authenticate the user when they enter the D•One journey.

Sessions have a token associated with them which are only valid for 1 hour. After the time elapses the token will expire and the URL will no longer work; a new one will need to be generated.

When a user is done with the D•One journey, they will be returned to the partnerRedirectUrl, provided when the session was created. A sessionTerminationToken will be appended to this URL which can be used to re-identify the user using this token along with the complete session endpoint. The userId will be returned.

An overview of the call sequences can be seen below.