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.

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.

sequenceDiagram
    participant C as Customer
    participant M as Merchant
    participant B as Buckaroo
    participant R as Riverty
    C->>M: Places order (BNPL checkout)
    M->>B: Pay / Authorize request
    B-->>M: Status 791 (Pending) + RequiredAction.RedirectURL
    M->>C: Redirect to RedirectURL
    C->>R: Completes identity verification
    R-->>B: Verification result
    B-->>M: Push message with final status
    Note over M,B: 190 = Success · 690 = Rejected
    M->>C: Show confirmation / decline based on push

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"
  }
}

What happens after the redirect

After you redirect the customer to the RequiredAction.RedirectURL, the customer completes identity verification on Riverty's side. Your integration does not receive the final outcome synchronously — verification happens outside your checkout, so you must rely on the asynchronous status update.

When verification is finished, Buckaroo sends a push message to your configured push URL with the final transaction status:

• 190 — Success: the transaction is confirmed and you can complete the order.
• 690 — Rejected: verification failed or was declined; do not fulfill the order.
• 890 / 891 — Cancelled: the customer abandoned the flow without completing verification.

Make sure a push URL is configured for these transactions, and that your push handler treats the 791 → final status transition as the authoritative result rather than the initial Pay/Authorize response. If you do not use push messages, you can instead poll the transaction status using Transaction Status (GET), though push is strongly recommended to avoid delays in order confirmation.

Note: Customers may not always return to your returnURL after verification (for example, if they close the browser). Because of this, the push message — not the customer's return — should drive your order state.

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.