REDIRECT

The REDIRECT method is a browser-based flow where the consumer is redirected to a secure page to authenticate their payment. After completing the process, they are redirected back to the merchant’s website with the payment result.

REDIRECT authentication requires you to provide a returnUrl which is where the consumer will be returned after completing the payment.

Request

//...
  "authenticationSettings": [
    {
      "type": "REDIRECT",
      "settings": {
        "returnUrl": "https://example.com/order_details?order_id=12345"
      }
    }
  ]
//...

Response

//...
  "authenticationMethods": [
    {
      "details": {
        "requestUrl": "https://redirection-target.com",
        "requestMethod": "GET"
      },
      "type": "REDIRECT"
    }
  ]
//...

requestUrl is the URL where the consumer should be redirected to authenticate the payment.

requestMethod is GET or POST.

• GET a simple redirection is expected.
• POST a client-side form submission with requestUrl as the form target is expected.

💡

Note

We do not recommend using IFrames. This causes the scheme's pages not to render correctly and not complete the payment.

Make sure you use the device-native web view (Safari for iOS and Chrome for Android) for the in-app rendering of the scheme's HTML pages. Using third-party rendering engines causes the scheme's pages not to render correctly.