Ropay

Ropay is a payment method that supports QR code-based (desktop) and deeplink-based (mobile) payment flows, with integration options ranging from PayU's payment wall to fully transparent/embedded merchant-controlled checkout.

Configuration and Usage

Podstawowe informacje

Ropay jest dostępny wyłącznie dla merchantów działających w Rumunii.

---

To enable Ropay on the PayU side, contact the PayU sales team.

Once Ropay is configured and activated, it will be visible on the payment page (checkout).

User Payment Flows

Ropay supports two user flows depending on the device:

• Desktop flow: The user is presented with a QR code, which is scanned using a mobile banking application.
• Mobile flow: The user is redirected (via deeplink) to a mobile banking application to complete the payment.

QR Code Availability

The QR code is available only in the desktop flow.

Merchant Integration

The merchant can use Ropay in three ways:

• The payer selects the payment method on the PayU payment selection page.
• The payer selects the payment method on the merchant's checkout.
• The merchant uses a transparent/embedded flow with full control over the checkout experience.

PayU Payment Selection Page

This is a standard integration, the same as other payment methods.

The merchant creates an order indicating PAYMENT_WALL in the payMethod section, or omits the payMethod section entirely:

"payMethod": {
  "type": "PAYMENT_WALL"
}

Merchant's Checkout

The payer selects the Ropay icon on the merchant's checkout, and the merchant declares ropay in the order request, similarly to other PayU payment methods:

"payMethod": {
  "type": "PBL",
  "value": "ropay"
}

In response, the merchant obtains a redirectUri and the payer is then redirected through the standard PayU payment flow with Ropay preselected.

Transparent/Embedded Flow

The merchant has full control over the payment experience and the payer does not leave the merchant's checkout. The merchant is responsible for handling the payment flow based on details returned in the response when creating an order.

In transparent flow, the merchant determines how the user is redirected:

• Display a QR code (desktop scenario), or
• Trigger a redirect to a mobile banking application (mobile scenario).

PayU provides the necessary data in the response, while the final implementation and user experience are controlled by the merchant.

Desktop Flow

Request for desktop mode — a QR code will be returned in the response:

"payMethods": {
  "payMethod": {
    "type": "TRANSPARENT",
    "value": "ropay"
  }
}

Response contains a base64-encoded QR code image:

{
  "status": {
    "statusCode": "WARNING_CONTINUE_QRCODE",
    "severity": "WARNING"
  },
  "orderId": "WZHF5FFDRJ140731GUEST000P01",
  "qrCode": "iVBORw0KGgoAAAANSUhEUgAAAJEAAACRAQAAAADro2eOAAACW0lEQVR42r2Wsa30IBCE1yIgsxtAog0yWrIbsH0N2C05ow0kGjhnBMj7Blt3L"
}

Mobile Flow

Request for mobile mode — a redirect URL (deeplink) for the bank's mobile app will be returned in the response. To indicate a Swift Code in this integration type, the merchant must prepare their own bank selection page.

"payMethods": {
  "payMethod": {
    "type": "TRANSPARENT",
    "value": "ropay",
    "ropay": {
      "swiftCode": "ABCD1234"
    }
  }
}

Response contains a redirectUri with a deeplink to launch the mobile banking application:

Sample Response with redirectUri

{
  "status": {
    "statusCode": "SUCCESS"
  },
  "redirectUri": "{deeplink_for_waking_up_mobile_bank_app}",
  "orderId": "WZHF5FFDRJ140731GUEST000P01"
}