Migration Guide: Redirects with SCA

Changes Required

If your integration already supports Riverty's Strong Customer Authentication (SCA), most of the work is already done: You only need to add a merchantURL parameter to every /authorize request instead of appending it to the responded Url to enable the new version of the redirect flow. Validating the status of a redirected transaction status has not changed and therefore require no updates.

This guide walks you through the required change.

Prepare the /authorize request

Modify your POST /api/v3/authorize request to include a merchantUrl parameter:

{
  "customer": {
    "firstName": "John",
    "lastName": "Doe"
  },
  ...
  "merchantUrl": "https://yourwebsite.com/redirect-handler"
}

Process the Authorization Response

If the outcome field in the API response is Pending and a redirectUrl is provided, then redirect the shopper to the given URL. Compared to the previous version, there is no need to append the Url as you have already provided it via the initial /authorize request.

No further error handling or response validation is required if outcome is Pending and a redirectUrl is responded:

{
    "outcome": "Pending",
    "redirectUrl": "https://secure-pt.riverty.com/v...." ,
    ...
 }

Deployment Update: We are making an update to the authentication flow to harmonize field naming and improve consistency across responses:

• The new redirectUrl field will replace the existing secureLoginUrl field. To ensure compatibility, the old field will continue to be included in responses, but is deprecated.
• The change will be deployed on April 10th, 2025.

For further details, refer to our main Redirect documentation..