Pre-authorization - Web-redirect

When the consumer either scan a Dynamic Code displayed as QrCode or type the mobile number to complete the pre-authorization. Both options are handled by the Web Redirect that is a solution that redirects the user to a Satispay web-page to complete the payment.


Web-button vs Web-redirect

The Pre-authorization - Web-button is the preferred solution. So rely on the Web-redirect only if you cannot support the other solution.

APIs required for this flow


Create authorization

When creating an authorization token for the Web-redirect, the callback_url (body_param) and redirect_url (in metadata) are required.

Sequence diagram

Authorization page

After the authorization token is created, redirect the user to the authorization page.{token_id}{token_id}