PayU Ghana

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications in this section to integrate with PayU Ghana.

API Version

Minimum required API version: 1.1.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 MethodPayment Method Type
MASTERCARDCards
VISACards

Payment Page

The following table lists all supported payment methods available on the PayU payment page. For each supported payment method, the API Value column list the value you need to pass in the payment_method.additional_details.supported_payment_methods array of the Create Charge request.

Payment MethodAPI ValueOnly for Requests
Airtel MoneyAIRTEL_MONEYCharge
MASTERCARDCREDITCARDCharge
MTN MomoMTN_MOMOCharge
TigoPesaTIGOPESACharge
VISACREDITCARDCharge
Vodafone CashVODAFONE_CASHCharge

Currencies

GHS

Features

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

FeatureSupported
3DS 1.0 ExternalNo
3DS 1.0 InternalYes
3DS 2.0 ExternalNo
3DS 2.0 InternalNo
InstallmentsNo
Level 2 and 3 DataNo
Network TokensNo
Payment FacilitatorNo
Pre-authorizationNo
Retrieve Supported Payment MethodsNo
Retrieve Supported PlansNo
Statement Soft DescriptorNo
Stored Credentials FlagNo
Transaction Processing without CVVNo

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.

Supported requests for card transactions.
RequestPartial/MultipleModeNotes
Charge Not ApplicableAsynchronous or SynchronousThe request can be synchronous or asynchronous, depending on whether you implemented a 3DS flow.
Refund Both partial and multiple are supportedSynchronous
Void Not ApplicableSynchronous
Supported requests for payment page transactions.
RequestPartial/MultipleMode
AuthorizePartial and multiple are not supportedAsynchronous
Capture Partial is supportedSynchronous
Charge Not ApplicableAsynchronous
Refund Both partial and multiple are supportedSynchronous
Void Not ApplicableSynchronous

Setup Procedures

The following table lists the setup procedures that are specific to this provider.

ConfigurationRequired/Optional
In the PaymentsOS Control Center, configure the following credentials:
  • Username: Web service username provided by PayU Ghana.
  • Password: Web service password provided by PayU Ghana.
  • Safekey: PayU Merchant Identifier provided by PayU Ghana.
To obtain test credentials, click here. To obtain live credentials, login to the merchant portal.
Required
In your PayU Ghana account, enable the payment methods you want to display in the payment page. For more information, see Implementing a Payment Page Flow below. Contact PayU Ghana support for assistance.Optional
If you want to use our End-to-End Encryption Service, configure the public key generated with PayU Ghana in the PublicJWK field in your PaymentsOS account. Optional

Integration Procedures

The following sections list the integration procedures that are specific to this provider.

Enabling 3DS

PayU Ghana 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 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 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"
  }
  ...
}

Processing Payments without a CVV Check

If you disabled the cvv check in your account, you will need to pass a recurring field with a value of true in the provider_specific_data object.

"provider_specific_data": {
    "magellan": {
      "additional_details": {
       ...
    },
     "recurring": true
  }

Implementing a Payment Page Flow

If desired, you can implement a payment flow in which users are redirected to a payment page where they can then select their payment method of choice. This flow is identical to a redirection flow, in which the response of the Create Charge request returns a Redirection object that includes the URL of the payment page to which you can redirect the user. Just make sure that your Create Charge request includes a payment_method.additional_details.supported_payment_methods field with a comma separated list of the payment methods you want to show in the payment page:

{
  "payment_method": {
    "source_type": "payment_page",
    "type": "untokenized",
    "additional_details": {
      "supported_payment_methods": "CREDITCARD,[SEE TABLE SUPPORTED PAYMENT METHODS]"
    }
  }
}

A few caveats:

  • In your PayU account, you must enable the payment methods you want to show in the payment page.

  • Authorize and Capture requests are not supported in a payment page flow.

  • When using the BodyBuilder to generate sample requests, make sure to choose the Payment Page payment type.

Testing

For testing, use the cards listed below. For any of the cards, use 02/2022 as expiry date and 123 as CVV.

VISA - Simulator Matrix for basic 3DS Scenarios

Card Type

PAN

Card Enrolled

OTP Success

ECI

Description

Risk Setting: Fully Authenticated = OFF

VISA 3DS test scenarios for 2 different 3DS authentication mode settings

Transaction Result

VISA

4000015372250142

YES

YES

05

Cardholder Authentication Success + Bank response success

Approved

VISA

4000019562093601

YES

NO


Cardholder Authentication Failure

Transaction Failed

VISA

4000019542438801

NO

N/A

06

Issuer/Cardholder not participating

Transaction Successful

VISA

4000029520272445

YES

YES

05

Cardholder Authentication Success + Bank response failure

Transaction Failed

MasterCard - Simulator Matrix for basic 3DS Scenarios

Card Type

PAN

Card Enrolled

OTP Success

ECI

Description

Risk Setting: Fully Authenticated = OFF

MasterCard 3DS test scenarios for 2 different 3DS authentication mode settings

Transaction Result

MasterCard

5100018609086541

YES

YES

02

Cardholder Authentication Success

Transaction Successful

MasterCard

5100013960913581

YES

NO


Cardholder Authentication Failure

Transaction Failed

MasterCard

5100011063555010

NO

N/A

01

Issuer/Cardholder not participating

Transaction Successful

MasterCard

5100022615342534

YES

YES

02

Cardholder Authentication Success + Bank response failure

Transaction Failed

3D Secure

For testing 3D secure transactions, use the following accounts.

3DS redirect:

  • Username: 800060
  • Password: qDRLeKI9
  • Safekey: {FBEF85FC-F395-4DE2-B17F-F53098D8F978}

3DS no-redirect:

  • Username: 800059
  • Password: 0aSlJ068
  • Safekey: {38D2290B-712B-4D86-B514-E450A1788F91}
Last modified December 7, 2021