Handle users coming back to your interface

When users are redirected to your predefined redirect URI, we add a query parameter to this redirect URI to help you handle

• status=success when the user is redirecting to you after having successfully aggregated their account. In this case, we also append the parameter customer_id={customerId}
• status=error when is redirecting to after not having successfully aggregated their account
• status=session_expired when the is redirected to you after the expiration of the session
• status=user_cancelled when the user is redirected to you after exiting the aggregation journey

So, depending on the parameter received, you can display a customized page. For example :

• https://myredirecturl.com?status=success: you display the page expected in the event of success to the user. If you have not processed the OB data yet, you can show a loading page
• https://myredirecturl.com?status=error: you display the page intended for the user in the event of an error. You can send the user back to the OB journey or offer an alternative way
• https://myredirecturl.com?status=user_canceled: you display the page intended for the user in the event of an exit. You can send the user back to the OB journey or offer an alternative way
• https://myredirecturl.com?status=session_expired: you display the page intended for the user in the event of an session expiration. You can send the user back to the OB journey or offer an alternative way