PayU Romania

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.

Currencies

RON, USD, EUR, GBP, HUF, BGN, CZK, DKK, PLN, SEK, HRK, and UAH.

Features

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

Feature	Supported
3DS Data from External MPI	No
3DS Redirection	Yes
Installments	Yes
Statement Soft Descriptor	No
Stored Credentials Flag	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.

Setup Procedures

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.

Configuring IPN settings

Enabling IPNs is mandatory, to keep the PaymentsOS platform in sync with PayU systems.

Login to your PayU Romania account, and choose Account Management > Account Settings > IPN Settings.

First, set the following IPN URL fFor the PaymentsOS live environment: https://api.paymentsos.com/callbacks/payuromania/live/notifications

Next, select the following (required) fields:SALEDATE, REFNOEXT, ORDERSTATUS, IPN_PID[], IPN_PNAME[], IPN_DATE, and IPN_TOTALGENERAL. We recommend selecting all the fields.

Now enable IPNs in your PayU Romania account by choosing Account Settings > Notifications > Type of notifications, and select IPN (Instant Payment Notification) (by default, only Authorized orders is enabled.)

As a last step, Activate all IPN types by choosing Account Settings > Notifications > Send notifications for, and select:

• Canceled and returned orders
• Complete orders

Redirecting your Customer for Redirection Flows (3DS)

When you send a post authorization request, a redirection flow may be required (3D Secure authentication). If so, we will return an authorization resource containing an authorization.redirection.url, and a status of 'pending'. Redirect your customer to this URL, so that they can authenticate themselves / complete the payment flow.

Once the redirection session is done, we'll redirect your customer's browser back to your site, using the merchant_site_url (that you provided in the post authorization request). We've included the following URL parameters in the merchant_site_url, to provide you with the context of the page that you'll need to load: payment_id, authorization_id, and status (of the authorization). Here's an example:

<merchant_site_url>
  ?payment_id=dd1fbe34-4636-4a61-8cb1-27ac8a175284
  &authorization_id=aec1c306-e0f7-452b-8fb5-5b34489e9d10
  &status=Pending

Testing

You can use the following test cards for testing:

You can test installments payment methods using the following card details for different testing scenarios: