PayU Russia
Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.
- API Version
- Payment Methods
- Currencies
- Features
- Requests
- Setup Procedures
- Integration Procedures
- Testing
API Version
Minimum required API version: 1.0.0
Payment Methods
The following table lists all supported payment methods.
| Payment Method | Payment Method Type |
|---|---|
| MAESTRO | Cards |
| MASTERCARD | Cards |
| MIR | Cards |
| QIWI | Bank Transfer |
| VISA | Cards |
| VISA Electron | Cards |
Currencies
RUB
Features
The following table provides an overview of all supported and non-supported features.
| Feature | Supported |
|---|---|
 3DS 1.0 External | No |
| 3DS 1.0 Internal | Yes |
| 3DS 2.0 External | No |
| 3DS 2.0 Internal | No |
| Installments | No |
| Level 2 and 3 Data | No |
| Retrieve Supported Payment Methods | No |
| Statement Soft Descriptor | No |
| Stored Credentials Flag | Yes |
| Transaction Processing without CVV | Yes |
Requests
The following table lists all supported requests. Use the bodybuilder to create a sample request body for each request type.
| Request | Partial/Multiple | Mode |
|---|---|---|
| Authorize | Partial and multiple are not supported | Asynchronous |
| Capture | Partial is supported | Asynchronous |
| Refund | Both partial and multiple are supported | Asynchronous |
| Void | Not Applicable | Asynchronous |
| Request | Partial/Multiple | Mode | Notes |
|---|---|---|---|
| Authorize | Partial and multiple are not supported | Asynchronous | After the Authorize request, PayU Russia will capture the funds manually. You should thus not invoke a Capture request yourself. To receive a notification when the Capture is done, register webhooks and enable notifications for Create Capture events. |
Setup Procedures
The following table lists the setup procedures that are specific to this provider.
| Configuration | Required/Optional |
|---|---|
In the PaymentsOS Control Center, configure the following credentials:
| Required |
| In the PaymentsOS Control Center, register webhooks to be notified when a transaction changes its status. | Required |
| In your PayU Russia account, configure the currencies you want to use in transactions. Contact PayU Russia support for assistance. | Required |
| In your PayU Russia account, enable IPNs (Instant Payment Notifications). This will ensure that PaymentsOS is kept in sync with PayU systems. See Configuring IPN Settings below. Contact PayU Russia support for assistance. | Required |
| Disable the cvv check if you do not require customers to enter their cvv code when initiating a payment. This can only be done by PayU Russia support. Contact PayU Russia support for assistance. | Optional |
| Enable partial captures if desired. This can only be done by PayU Russia support. Contact PayU Russia support for assistance. | Optional |
| Enable partial captures if desired. This can only be done by PayU Russia support. Contact PayU Russia support for assistance. | Optional |
Integration Procedures
The following sections list the integration procedures that are specific to this provider.
Configuring IPN settings
You must enable IPNs (Instant Payment Notifications) to keep PaymentsOS in sync with PayU systems. To enable IPNs, login to your PayU Russia account, and open the Account Management > Account Settings > IPN Settings tab.
In your account, configure the following IPN URL:
- For working with the PaymentsOS test environment: https://api.paymentsos.com/callbacks/payurussia/test/notifications
- For working with the PaymentsOS live environment: https://api.paymentsos.com/callbacks/payurussia/live/notifications
After aconfiguring the IPN URLs, select the following (required) fields: SALEDATE, REFNOEXT, ORDERSTATUS, IPN_PID[], IPN_PNAME[], IPN_DATE, and IPN_TOTALGENERAL.
We recommend selecting all the fields.
As a last step, enable IPNs in your PayU Russia account (by default, IPNs are enabled for Authorized orders only). Click Account Settings > Notifications > Send notifications for and select the following:
Canceled and returned ordersComplete orders
Testing
The following table lists the card numbers you can use for testing.
| Card Number | Expiry Date | CVV | Notes |
|---|---|---|---|
| 4150399999000900 | 01/19 | 620 | None |
| 4058889968744754 | 01/15 | 866 | 400 RUB on account. Try large amounts |
| 4058889902715340 | 01/15 | 702 | Status: Restricted |
| 4058889987820056 | 01/15 | 794 | Limit: 10 RUB |
| 4058889945545159 | 01/15 | 694 | Status: Not active |
| 4058889967077602 | 01/15 | 136 | Status: Compromised |
| 5408145000011841 | 01/20 | 110 | None |