Rapyd
API Version
Minimum required API version: 1.1.0
Payment Methods
The tables below lists payment methods that are supported through a server-to-server integration and through the PayU payment page. When integrating a payment method, the Authorization, Capture and Charge request types are supported unless stated otherwise in the Only for Requests column.
Server-to-Server Integrations
The following table lists all supported payment methods through a server-to-server integration.
| Payment Method | Payment Method Type |
|---|---|
| Rapyd | Payment Page |
Payment Page
The following table lists all supported payment methods available on the PayU payment page. For each supported payment method, the API Value column list the value you need to pass in the payment_method.additional_details.supported_payment_methods array of the Create Charge request.
| Payment Method | API Value | Only for Requests |
|---|---|---|
| Rapyd | RAPYD | Charge |
Currencies
USD
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 | Yes |
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.
| Request | Partial/Multiple | Mode |
|---|---|---|
| Charge | Not Applicable | Asynchronous |
| Refund | Both partial and multiple are supported | Synchronous |
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.
Integration Procedures
The following sections list the integration procedures that are specific to this provider.
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. Just make sure that your Create Charge request includes a payment_method.additional_details.supported_payment_methods field with a comma separated list of the payment methods you want to show in the payment page:
{
"payment_method": {
"source_type": "payment_page",
"type": "untokenized",
"additional_details": {
"supported_payment_methods": "CREDITCARD,[SEE TABLE SUPPORTED PAYMENT METHODS]"
}
}
}
A few caveats:
-
In your PayU account, you must enable the payment methods you want to show in the payment page.
-
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.