Skip to main content
After initiating consent, redirect the user to the webRedirectionUrl returned in the response. The user completes the consent journey there, and is then sent back to the redirectUrl you supplied.

​
Redirect the user

Open the webRedirectionUrl in the user’s browser (or a web view). The URL carries a time-bound access_token — use it as-is and do not modify it.

​
Return to your app

Once the journey finishes, the user is redirected back to your redirectUrl with the following query parameters appended:
ParamDescription
txnidTransaction identifier for the journey.
statustrue if the journey succeeded, false if it failed.

​
Example

https://yourapp.com/callback?txnid=abc123&status=true
The redirect status is a quick signal for your UI. Always confirm the terminal outcome via Track Status before fetching data.

​
Next step

Track the journey to completion via Track Status — webhook, status polling, or in-iframe UI events.