PayU Russia

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

API Version

Minimum required API version: 1.0.0

Payment Methods

The following table lists all supported payment methods.

Payment MethodPayment Method Type
MAESTROCards
MASTERCARDCards
MIRCards
QIWIBank Transfer
VISACards
VISA ElectronCards

Currencies

RUB

Features

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

FeatureSupported
3DS 1.0 ExternalNo
3DS 1.0 InternalYes
3DS 2.0 ExternalNo
3DS 2.0 InternalNo
InstallmentsNo
Level 2 and 3 DataNo
Retrieve Supported Payment MethodsNo
Statement Soft DescriptorNo
Stored Credentials FlagNo
Transaction Processing without CVVYes

Requests

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

Supported requests for card transactions.
RequestPartial/MultipleMode
AuthorizePartial and multiple are not supportedAsynchronous
Capture Partial is supportedAsynchronous
Refund Both partial and multiple are supportedAsynchronous
Void Not ApplicableAsynchronous
Supported requests for bank transfer transactions.
RequestPartial/MultipleModeNotes
AuthorizePartial and multiple are not supportedAsynchronousAfter 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.

ConfigurationRequired/Optional
In the PaymentsOS Control Center, configure the following credentials:
  • merchant_code: The merchant id in PayU Russia.
  • secret_key: Secret key provided by PayU Russia.
To see your PayU Russia credentials, open your PayU administration page and choose Account Management > Account settings.
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

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:

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 orders
  • Complete 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

results matching ""

    No results matching ""