PayU Single Platform (PL, CZ, HU, SK)

PayU Single Platform 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 Single Platform.

SpecificationsDetails
Minimum PaymentsOS API Version1.0.0
RegionsPoland, Czech Republic, Hungary, Slovakia
Requests
  • Authorize
  • Capture
  • Refund (including partial)
  • Void
Limitations:
Partial Capture is not supported. Sending less than the full amount will generate an error.
CurrenciesBGN, CHF, CZK, DKK, EUR, GBP, HRK, HUF, NOK, PLN, RON, RUB, SEK, UAH, USD
Payment Methods
  • MAESTRO
  • MASTERCARD
  • VISA
Transaction Processing without CVVSupported
3DS RedirectionSupported

Specifications for Bank Transfer Transactions

The following table lists the integration specifications for PayU Single Platform.

SpecificationsDetails
Minimum PaymentsOS API Version1.0.0
RegionsPoland, Czech Republic, Hungary, Slovakia
RequestsAuthorize
CurrenciesCZK, EUR, PLN
Payment Methods
  • PBL (Pay by Link)
  • payment_wall

Configurations

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

ConfigurationRequired/Optional
In the PaymentsOS Control Center, configure the following credentials:
  • pos_id: The merchant's pos_id in the PayU Single Platform account.
  • second_key: The second_key obtained from PayU.
  • client_secret: used to validate notifications provided by PayU.
For your test credentials, login to your PayU Sandbox account.
For your live credentials, login to your PayU Account. In the PayU Biz Panel, in the Online payments tab, click > My Shops > click POS of the relevant shop > click the name under POS > CONFIGURATION KEYS.		Required
In the PaymentsOS Control Center, register webhooks to be notified when a transaction changes its status. The payment flows for PayU Single Platform are asynchronous, which return responses with the pendingstatus.Required
In your PayU Single Platform account, disable the Automatic collection option in your PayU Single Platform account for the relevant PayU Single Platform payment methods. This will enable the correct processing of authorization requests, and keep PaymentsOS in sync with the PayU system.Required
In your PayU Single Platform account, configure the currencies you want to use in transactions (only applicable to the credit card and payment_wall payment methods).Required
In your PayU Single Platform account, disable Tokenization for credit card payment methods. Contact PayU Single Platform support for assistance.Optional
In your PayU Single Platform account, disable the CVV check if desired. Contact PayU Single Platform support for assistance.Optional

Sample Requests

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

Redirecting your customer for Asynchronous Payment Flows

You'll need to redirect your customer for the following payment methods:

  • Credit card payments that include 3D Secure
  • PBL bank transfers
  • payment_wall payments

When you send a post authorization request, 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 and complete the payment flow:

  • For credit card payment methods, the redirection is to a 3D Secure site.
  • For the PBL payment method, the redirection is to your customer's bank authentication site.
  • For the payment_wall payment method, the redirection is to a PayU Single Platform hosted page, where your customer can select a payment method.

Once the authentication / payment method selection process at the provider 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

This section list the test card numbers you can use for testing your integration and outlines the test procedures for bank transfer payment methods.

Testing with Credit Card Payment Methods

You can use test cards for testing.

Card number Expiration date CVV Expected response 3-D Secure Card type
4444333322221111 01-2019 123 Positive authorization no Visa
5434021016824014 01-2019 123 Positive authorization no MasterCard
5099802211165618 01-2019 123 Positive authorization no Maestro
4012001037141112 01-2019 123 Positive authorization yes Visa
5000105018126595 01-2019 123 Negative authorization no Maestro

To see the most up to date list of cards, and the test POS for the sandbox, click here: http://developers.payu.com/en/overview.html#sandbox.

Testing with the PBL or payment_wall Payment Methods

To test an authorization request, use the following values for the payment_method.additional_details.bank_name field:

  • For the live environment use: "t", "payment_wall".
  • For the test environment use: "m", "o", "p", "c", or "payment_wall".

results matching ""

    No results matching ""