Simplifying Merchant Integration with Redirect-Based Data Collection

This page describes an optional redirect pattern that streamlines merchant integration by outsourcing the collection of sensitive payment-specific data—such as an IBAN for direct debit—to Riverty. At the same time, it allows merchants to retain control over payment method selection and user experience on their checkout pages.

Use Case: Merchant-Hosted Payment Selection, Riverty-Hosted Data Input

Many merchants prefer to keep the payment selection experience on their own checkout page to ensure a consistent look and feel and to optimize conversion, as shoppers can choose their preferred payment method directly. However, the collection of payment-specific data often varies by method and comes with regulatory obligations (e.g. presenting correct legal terms or SECCI documents for installment payments).

To address this, Riverty offers a hybrid redirect approach:

1. User selects a payment method (e.g. Direct Debit or Installments) on the merchant’s checkout page
2. Merchant redirects the user to Riverty for sensitive data input (e.g. IBAN)
3. User completes data entry on Riverty’s secure, compliant hosted page
4. User is redirected back to the merchant to finalize the checkout

This setup reduces technical complexity and compliance scope for the merchant while preserving the ability to fully manage the payment selection flow.

Example: Direct Debit with IBAN Collection via Redirect

1. Checkout page (merchant site)
   The user selects “Direct Debit” as their preferred payment method. The IBAN input field is not shown on the merchant's site.

2. Create payment session (merchant backend)
   The merchant initiates a BNPL session via Riverty’s API with payment_method: invoice and includes an empty directDebit object.

3. Redirect to Riverty for data entry
   The user is redirected to a Riverty-hosted page where they securely enter their IBAN in a compliant environment.

4. Return to merchant
   Upon successful submission, the session is updated, and the user is redirected back to the merchant’s site to complete the checkout.

Benefits

• ✅ Reduces compliance complexity
  Merchants are not required to handle or store sensitive data like IBANs or implement specific legal requirements for certain payment methods.

• ✅ Improves user experience
  Payment method selection stays under the merchant’s control, maintaining design consistency and usability.

• ✅ Minimizes integration effort
  No need to build and maintain secure data input flows—Riverty handles the heavy lifting.

Implementation Overview

To enable this pattern:

1. Refer to the Redirect Integration Guide
2. Riverty must activate the feature. For testing purposes, simply send an empty hostedCheckout object in the root of your /authorize request
3. Handle the redirect response and resume the session in your existing flow

Examples

Invoice

{
    "payment": {
        "type": "invoice"
    },
    "hostedCheckout": {},
    "merchantUrl": "https://www.example.com",
    ...
}

Direct Debit

{
    "payment": {
        "type": "invoice",
        "directDebit": {}
    },
    "hostedCheckout": {},
    "merchantUrl": "https://www.example.com",
    ...
}

Part Payment / Installments

{
    "payment": {
        "type": "partPayment"
    },
    "hostedCheckout": {},
    "merchantUrl": "https://www.example.com",
    ...
}

Within partPayment, Riverty will render the relevant installment options based on the customer profile and market.

For example:

• In Germany, fixed installments (represented as "type": "Installment" in the direct integration) will be displayed.
• In the Netherlands, the Pay-in-3 option (represented as "type": "PayinX") will be shown.