PayU Ghana

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

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

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




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

3DS 1.0 ExternalNo
3DS 1.0 InternalYes
3DS 2.0 ExternalNo
3DS 2.0 InternalNo
End-to-End Encryption (E2EE)Yes
Level 2 and 3 DataNo
Network TokensNo
Payment FacilitatorNo
Retrieve Supported Payment MethodsNo
Retrieve Supported PlansNo
Statement Soft DescriptorNo
Stored Credentials FlagNo
Transaction Processing without CVVNo


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.
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.
Charge Not ApplicableAsynchronous
Refund Both partial and multiple are supportedSynchronous
Void Not ApplicableSynchronous

Setup Procedures

Creating a Provider Configuration

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

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

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.
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.

Implementing 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.

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"


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.

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.


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

results matching ""

    No results matching ""