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

The following features require an API version higher than the minimum:

• 3DS 2.0 Internal requires API version 1.3.0

• 3DS 2.0 External requires API version 1.3.0

Payment Methods

The tables below lists payment methods that are supported through a server-to-server integration and through the PayU payment page.

Server-to-Server Integrations

The following table lists all supported payment methods through a server-to-server integration.

Payment Page

The following table lists all supported payment methods available on the PayU payment page.

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	Notes
3DS 1.0 External	Yes
3DS 1.0 Internal	Yes
3DS 2.0 External	Yes
3DS 2.0 Internal	Yes	Supported flow type: Self-handled Flow. For more information, see 3DS 2 Self-handled Flow.
End-to-End Encryption (E2EE)	No
Installments	Yes
Level 2 and 3 Data	No
Network Tokens	No
Payment Facilitator	No
Pre-authorization	No
Retrieve Supported Payment Methods	No
Retrieve Supported Plans	No
Statement Soft Descriptor	No
Stored Credentials Flag	Yes
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.

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.

Considerations when Creating an Authorization

The authorization amount may be higher than the payment.amount, due to commissions related to installments. The final authorization.amount can be seen in the response to the authorization request.

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 (Bank Transfer Payment Methods and 3DS)

When you send a post authorization request, a redirection flow may be required (for instance for 3D Secure authentication, or if the customer chooses to pay using a bank transfer payment method). 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

Special Responses for WIRE Payment Method

The WIRE payment methods don't follow the standard redirect flow. The response from a post authorization for WIRE contains a list of your merchant bank accounts, which you should display to your customer. They will need to select a bank account, to transfer to.

Here's a sample response from a post authorization request for the WIRE payment method:

{
  "id": "da6aa5ce-7c2c-474a-bbd5-5837fd5505dc",
  "amount": 31500,
  "created": "1515076243342",
  "reconciliation_id": "74ac9b5e-6204-4265-a8d0-a0532d15d1ce",
  "provider_specific_data": {
    "additional_details": {
      "payment_method": "WIRE"
    }
  },
  "payment_method": {
    "billing_address": {
      "country": "TUR",
      "first_name": "John",
      "last_name": "Doe",
      "phone": "756312633",
      "email": "John.Doe@email.com"
    },
    "type": "untokenized",
    "source_type": "WIRE"
  },
  "result": {
    "status": "Pending"
  },
  "provider_data": {
    "provider_name": "PayURomania",
    "response_code": "PENDING_AUTHORIZATION",
    "description": "Order saved and pending authorization.",
    "raw_response": "{\"AUTH_CODE\":\"\",\"RETURN_MESSAGE\":\"Order saved and pending authorization.\",\"ALIAS\":\"dfdfee128cb5870d4601c894e96f13a0\",\"STATUS\":\"SUCCESS\",\"RRN\":\"\",\"DATE\":\"2018-01-04 17:30:43\",\"ORDER_REF\":\"74ac9b5e-6204-4265-a8d0-a0532d15d1ce\",\"RETURN_CODE\":\"PENDING_AUTHORIZATION\",\"HASH\":\"0ccffa773df5236026b6984d4627931a\",\"REFNO\":\"48880145\"}",
    "authorization_code": "",
    "external_id": "48880145",
    "documents": [{
        "descriptor": "bank_list",
        "content_type": "json",
        "content": "{\"BANK_IDENTIFIER\":\"IS BANK\",\"BANK_ACCOUNT\":\"TR770006400000110111847674\",\"ROUTING_NUMBER\":[\"\"],\"IBAN_ACCOUNT\":\"TR770006400000110111847674\",\"BANK_SWIFT\":\"ISBKTRIS\",\"COUNTRY\":\"Turkey\",\"WIRE_RECIPIENT_NAME\":\"PayU Ödeme Kuruluşu AŞ\",\"WIRE_RECIPIENT_VAT_ID\":\"0550442060\"}"
      }, {
        "descriptor": "bank_list",
        "content_type": "json",
        "content": "{\"BANK_IDENTIFIER\":\"FINANSBANK\",\"BANK_ACCOUNT\":\"TR680011100000000056754760\",\"ROUTING_NUMBER\":[\"\"],\"IBAN_ACCOUNT\":\"TR680011100000000056754760\",\"BANK_SWIFT\":\"FNNBTRIS  \",\"COUNTRY\":\"Turkey\",\"WIRE_RECIPIENT_NAME\":\"PayU Ödeme Kuruluşu AŞ\",\"WIRE_RECIPIENT_VAT_ID\":\"0550442060\"}"
      }, {
        "descriptor": "bank_list",
        "content_type": "json",
        "content": "{\"BANK_IDENTIFIER\":\"YAPI KREDI BANKASI\",\"BANK_ACCOUNT\":\"TR680006701000000046382916\",\"ROUTING_NUMBER\":[\"\"],\"IBAN_ACCOUNT\":\"TR680006701000000046382916\",\"BANK_SWIFT\":\"YAPITRISFEX\",\"COUNTRY\":\"Turkey\",\"WIRE_RECIPIENT_NAME\":\"PayU Ödeme Kuruluşu AŞ\",\"WIRE_RECIPIENT_VAT_ID\":\"0550442060\"}"
      }, {
        "descriptor": "bank_list",
        "content_type": "json",
        "content": "{\"BANK_IDENTIFIER\":\"TURK EKONOMI BANKASI\",\"BANK_ACCOUNT\":\"TR070003200000000030539275\",\"ROUTING_NUMBER\":[\"\"],\"IBAN_ACCOUNT\":\"TR070003200000000030539275\",\"BANK_SWIFT\":\"TEBUTRIS\",\"COUNTRY\":\"Turkey\",\"WIRE_RECIPIENT_NAME\":\"PayU Ödeme Kuruluşu AŞ\",\"WIRE_RECIPIENT_VAT_ID\":\"0550442060\"}"
      }, {
        "descriptor": "bank_list",
        "content_type": "json",
        "content": "{\"BANK_IDENTIFIER\":\"TURKIYE GARANTI BANKASI, A.S.\",\"BANK_ACCOUNT\":\"TR530006200006800006295309\",\"ROUTING_NUMBER\":[\"\"],\"IBAN_ACCOUNT\":[\"\"],\"BANK_SWIFT\":\"TGBATRISXXX\",\"COUNTRY\":\"Turkey\",\"WIRE_RECIPIENT_NAME\":\"PayU Ödeme Kuruluşu AŞ\",\"WIRE_RECIPIENT_VAT_ID\":\"0550442060\"}"
      }, {
        "descriptor": "bank_list",
        "content_type": "json",
        "content": "{\"BANK_IDENTIFIER\":\"AKBANK\",\"BANK_ACCOUNT\":\"TR270004600171888000103527\",\"ROUTING_NUMBER\":[\"\"],\"IBAN_ACCOUNT\":[\"\"],\"BANK_SWIFT\":\"AKBKTRIS\",\"COUNTRY\":\"Turkey\",\"WIRE_RECIPIENT_NAME\":\"PayU Ödeme Kuruluşu AŞ\",\"WIRE_RECIPIENT_VAT_ID\":\"0550442060\"}"
      }
    ]
  }
}

Testing

For testing in the sandbox environment, contact your PayU Romania account representative to request a dedicated testing account. Alternatively, use the following credentials to test in a shared environment:

• cPanel URL: https://sandbox.payu.ro/cpanel/

• User: support@zooz.com

• Password: Zooz@2018

• Merchant ID: DEMOROSB

• Secret Key: 1231234567890123

You can use the following test cards for testing:

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