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

Currencies

GHS

Features

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

Feature	Supported
3DS 2.0 External	No
3DS 2.0 PaymentsOS-handled	No
3DS 2.0 Provider-handled	Yes
3DS 2.0 Self-handled	No
Installments	No
Level 2 and 3 Data	No
Multi-seller Payments	No
Network Tokens	No
Payment Facilitator	No
PayU Risk	No
Pre-authorization	No
Retrieve Supported Payment Methods	No
Retrieve Supported Plans	No
Statement Soft Descriptor	No
Stored Credentials Flag	No
Transaction Processing without CVV	No

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.

• Cards
• Payment Page

Setup Procedures

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

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

MasterCard - Simulator Matrix for basic 3DS Scenarios

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}