PayU Romania

PayU Romania has some special integration requirements. Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

Specifications for Card-based Transactions

The following table lists the integration specifications for PayU Romania.

SpecificationsDetails
Minimum PaymentsOS API Version1.0.0
Requests
  • Authorize
  • Capture (including partial)
  • Refund (including partial)
  • Void
Limitations:
Support for partial Capture depends on the specific acquirer.
CurrenciesRON, USD, EUR, GBP, HUF, BGN, CZK, DKK, PLN, SEK, HRK, and UAH.
Payment MethodsCredit cards with installments:
  • MAESTRO
  • MASTERCARD
  • VISA
  • VISA Electron
Credit cards without installments:
  • ALPHABANK_INSTALLMENTS
  • BCR_INSTALLMENTS
  • BRDF
  • BRD_INSTALLMENTS
  • CARD_AVANTAJ
  • GARANTI_RO
  • OPTIMO
  • RAIFFEISEN
  • STAR_BT
Before starting your implementation, you should verify with your PayU Romania Account Manager, which of the payment methods with installments are enabled in your account.
3DS RedirectionSupported

Configurations

The following table lists the configurations that are specific to PayU Romania.

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

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:
Required
In your PayU Romania account, configure the currencies you want to use in transactions. Contact PayU Romania support for assistance.Required
In your PayU Romania 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 Romania support for assistance.Required

Sample Requests

Use the bodybuilder to create a sample request body for each request type.

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

Note

The status of your authorization request may still be 'pending' when we redirect your customer back to your site (while the provider is processing the request).

Testing

You can use the following test cards for testing:

Test Card Number Expiration Month Expiration Year CVV / CVC2 Cardholder Name 3DS Enrolled Payment Status Error received
4111111111111111 12 2020 123 Any name YES Success payment -
4111111111111111 11 2020 123 Any name No Success payment -
5105105105105100 11 2020 123 Any name No Failed payment Not sufficient funds
5563693062030796 11 2020 123 Any name No Failed payment Stolen card, pick up
4921301010459253 11 2020 123 Any name No Failed payment Default error

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

Brand Test Card Numbers Expiration Month Expiration Year CVV / CVC2 Cardholder Name
Card Avantaj 5186170004106668
5186170028360523
5186170008405330
03 2021 123 Any Name
BRD Finance 5220620107681833
5220620150352787
5220620137283642
03 2021 123 Any Name
Star BT 4555552420664386
4555551748017871
4555553122374365
03 2021 123 Any Name
Raiffeisen 6011116461271023
6011113186588013
6011113776422151
03 2021 123 Any Name
Garanti Bonus Card 5555003167580804
5555004528364631
5555004866445521
03 2021 123 Any Name
BCR 4999990806306657
4999995741805002
4999992252873230
03 2021 123 Any Name
AlphaBank 4670935882226267
4670934671405661
4670935815277585
03 2021 123 Any Name

results matching ""

    No results matching ""