Riverty Checkout Migration

Riverty is introducing a new checkout flow as a result of tightened BNPL legislation. The flow adds a pending status with a redirect URL, which requires merchants to redirect the customer to Riverty to complete identity verification before the transaction is confirmed.

Deadline: all merchants must be on a supported integration by 1 September 2026. If the update is not in place before this date, Riverty cannot guarantee successful transactions.

Do you need to take action?

Find your integration type in the table below.

Integration type	Action required
HPP / Smart Checkout	No action needed
Lightspeed	No action needed (automatic update)
WordPress / WooCommerce	No action needed (automatic update)
Shopware	Yes — update the plugin to version 3.2.0
Magento 2	Depends on your version — see below
Custom / API integration	Depends on your implementation — see below

Shopware

Update the Buckaroo plugin to version 3.2.0. You can find the latest release and update instructions on the Shopware 6 Releases page.

Magento 2

⚠️ Version guidance is being finalized. This section will be updated once confirmed with our engineering team. In the meantime, please contact [email protected] to check whether your specific Magento 2 version requires an update.

Custom / API integrations

You only need to act if your integration does not yet handle the new pending status with a redirect URL.

How to check

When a Riverty Pay or Authorize request requires additional customer verification, Buckaroo now returns a response with status code 791 (Pending processing) and a RedirectURL in the RequiredAction object. Your integration must redirect the customer to that URL to complete the flow.

Example pending response:

{
  "Status": {
    "Code": {
      "Code": 791,
      "Description": "Pending processing"
    }
  },
  "RequiredAction": {
    "RedirectURL": "https://checkout.buckaroo.nl/html/redirect.ashx?r=...",
    "Name": "Redirect"
  }
}

If your integration already detects status 791 and redirects the customer to the RequiredAction.RedirectURL, no action is needed.

If your integration does not yet handle this — for example, if it only processes status 190 (Success) and 690 (Rejected) — you need to add handling for the pending + redirect flow before 1 September 2026.

For the full request and response reference, see the Riverty Requests page.

Need help implementing this?

Contact [email protected] and our Technical Support team will assist you.