Rapyd

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications in this section to integrate with Rapyd.

API Version

Minimum required API version: 1.1.0

Currencies

IDR

Features

The following table provides an overview of all supported and non-supported features.

Feature	Supported
3DS 2.0 External	No
3DS 2.0 PaymentsOS-handled	No
3DS 2.0 Provider-handled	No
3DS 2.0 Self-handled	No
Multi-seller Payments	No
Network Tokens	No
Payment Facilitator	No
PayU Risk	No
Retrieve Supported Payment Methods	No
Retrieve Supported Plans	No
Statement Soft Descriptor	No
Transaction Processing without CVV	No

Requests

The following table lists all supported requests for card-based transactions. Use the bodybuilder to create a sample request body for each request type.

Payment Page

Supported requests for payment page transactions.

Request	Partial/Multiple	Mode
Charge	Not Applicable	Asynchronous

Setup Procedures

Creating a Provider Configuration

When creating a new provider configuration in the PaymentsOS Control Center, select Rapyd as the provider.

The following table lists the setup procedures that are specific to this provider.

Configuration	Required/Optional
In the PaymentsOS Control Center, configure the following Rapyd credentials: access_key secret_key payment_country (in ISO 2 format, e.g., US, GB, DE) When creating a new provider configuration in the PaymentsOS Control Center, select Rapyd as the provider.	Required
In your Rapyd account, configure which webhook notifications will be sent to PaymentsOS. See Configuring PaymentsOS to receive IPN messages from Rapyd below.	Required

Integration Procedures

The following sections list the integration procedures that are specific to this provider.

Configuring PaymentsOS to receive IPN messages from Rapyd

For Test Environment, configure the following:
- Callback URL: set to: https://api.paymentsos.com/callbacks/rapyd/test
- Events: Under the Collect section, select Select all to enable all webhook events
For Production Environment, configure the following:
- Callback URL: set to: https://api.paymentsos.com/callbacks/rapyd/live
- Events: Under the Collect section, select Select all to enable all webhook events
Click Save to apply the webhook configuration.

Implementing a Payment Page Flow

If desired, you can implement a payment flow in which users are redirected to a payment page where they can then select their payment method of choice. This flow is identical to a redirection flow, in which the response of the Create Charge request returns a Redirection object that includes the URL of the payment page to which you can redirect the user.

{
  "merchant_site_url": "http://www.abc.com/return-url",
  "payment_method": {
    "type": "untokenized",
    "source_type": "payment_page",
    "additional_details": {
      "supported_payment_methods": "visa,mastercard"
    }
  },
  "provider_specific_data": {
    "rapyd": {
      "additional_details": {
        "requested_currency": "USD",
        "description": "Payment description",
        "fixed_side": "buy",
        "language": "en",
        "expiration": 1785245629,
        "payment_expiration": 500,
        "billing_address_collect": false,
        "payment_fees_display": true,
        "required_customer_fields": "name,email,phone_number,address"
      }
    }
  }
}

A few caveats:

Authorize and Capture requests are not supported in a payment page flow.
When using the BodyBuilder to generate sample requests, make sure to choose the Payment Page payment type.

Last modified July 29, 2025