PayU Nigeria

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

Creating a Provider Configuration

When creating a new provider configuration in the PaymentsOS Control Center, select PayU Magellan as the provider.

Specifications for Card-based Transactions

The following table lists the integration specifications for PayU Nigeria.

Minimum PaymentsOS API Version1.1.0
  • Authorize
  • Capture (including multiple/partial)
  • Charge
  • Refund (including multiple/partial)
  • Void
CurrenciesNGN, USD
Payment Methods
  • AMEX
  • VISA
Transaction Processing without CVVSupported
3DS RedirectionSupported


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

In the PaymentsOS Control Center, configure the following credentials:
  • Username: Web service username provided by PayU Nigeria.
  • Password: Web service password provided by PayU Nigeria.
  • Safekey: PayU Merchant Identifier provided by PayU Nigeria.
To obtain test credentials, click here. To obtain live credentials, login to the merchant portal.
In your PayU Nigeria account, verify whether 3DS is configured to be optional or required and handle the 3DS flow accordingly. For more information, see Enabling 3DS below. Contact PayU Nigeria support for assistance.Required
In your PayU Nigeria account, disable the cvv check if you do not require customers to enter their cvv code when initiating a payment. Contact PayU Nigeria support for assistance.Optional

Sample Requests

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

Enabling 3DS


3DS must be implemented as part of a redirection flow. For an overview of how to implement a redirection flow, see Implementing a Redirection Flow.

If you require 3DS, contact PayU Nigeria support to configure the following IPN URLs in your PayU Nigeria environment:

After configuring the IPN URLs, configure Webhooks in your PaymentsOS environment to receive updates when a change in a transaction status occurs.

Note that in your PayU Nigeria account, you can configure 3DS to be either required (force 3DS) or optional. If you configured your account to enforce 3DS, then the user will always be required to complete a 3DS authentication step. If you configured 3DS to be optional and you want the user to complete a 3DS authentication step, then include a provider_specific_data object with an is3ds value of true in your Create Authorization or Create Charge API requests.

"provider_specific_data": {
    "magellan": {
      "additional_details": {
        "is3ds": "true"

Regardless of whether 3DS is set to required or optional, PayU Nigeria will only direct a user to complete a 3DS authentication flow if a user's card is enrolled for 3DSecure.

Bear in mind that a 3DS redirection flow requires that you pass a merchant_site_url in the Create Authorization or Create Charge request. If you do not pass a merchant_site_url, the user will not be able to complete the 3DS authentication flow. The response data of the Create Authorization or Create Charge request will indicate this in the additional_details.error field:

  "additional_details": {
    "error": "The transaction requires 3DS authentication, but cannot be completed as the merchant_site_url was not provided"


If the user could not complete the 3DS authentication flow, the transaction will remain in status Pending. After 40 minutes, the transaction will transition to a status of Failed.


You can use the test cards from the PayU Nigeria Test Credentials site.

results matching ""

    No results matching ""