Skip to main content
After initiating consent, redirect the user to the webRedirectionUrl returned in the response. The user completes the AA consent journey there — and, if AA cannot deliver, the same journey transparently guides them through the PDF statement upload fallback.
The webRedirectionUrl carries a time-bound access_token. Use it exactly as returned — do not modify or re-encode it.

​
Redirect the user

Send the user (browser or in-app web view) to the webRedirectionUrl. Once the journey finishes, the user is returned to the redirectUrl you supplied, with the result appended as query parameters.

​
Callback query parameters

ParamDescription
txnidTransaction identifier
statustrue = success, false = failure

​
Example callback

https://yourapp.com/callback?txnid=abc123&status=true
The callback status is a quick UI signal only. Always confirm the terminal outcome — including whether data arrived via AA or the PDF fallback — via Track Status.

​
Next steps

Continue to Track Status — webhook, status polling, or in-iframe UI events.