1
Handling Redirect
Connect will respond with the You will redirect the session to
session_redirect
route.redirect_url
via HTTP-GET, appending connect_token
.Example redirect (http)
You can append any other query parameter to redirect, for example, your internal session or a security key. They will be returned to you via callback later.
2
Handling Callback
Once you redirect the customer’s session to POST your response to Connect to
redirect_url
, you will soon receive a callback to the URI you specified when you created the connect_token
via the API. It will have the same query params and payload that you appended to the original redirect.Example callback
session_start
route:Your POST to Connect
Login
and Consent
.
However, depending on how the provider implements the login process, the configuration of their account (such as having multiple properties supplied under one contract) and other factors, they may be presented with additional pages:

The actual look and feel may vary between providers as they develop and host the pages. The word [Brand] will always be replaced with your business name.
