Payment-method icon

African e-wallets and online banking for API only

Add African e-wallets and online banking to an existing API integration.

Adyen currently cannot accept new integrations with African e-wallets and online banking.

Accept African e-wallets and online banking payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.

Before you begin

Before starting your African e-wallets and online banking integration:

  1. Make sure that you have set up your back end implementation.
  2. Add African e-wallets and online banking in your Customer Area.

When building your integration, note that you can already collect optional parameters from the shopper. This enhances the shopper experience as they won't have to fill these in later when they're redirected to the Cellulant payment form.

African shoppers expect merchant's email and direct phone number for requesting refunds and cancellations on the payment form. Take this into account when building your payment form for African e-wallets and online banking.

Build your payment form for African e-wallets and online banking

Include Cellulant in the list of available payment methods.

If you are using /paymentMethods to show available payment methods to the shopper, specify the following parameters:

The response contains paymentMethod.type: cellulant.

We provide logos for Cellulant which you can use on your payment form. For more information, refer to Downloading logos.

Make a payment

From your server, make a /payments request, specifying:

Parameter name Required Description
paymentMethod.type -white_check_mark- cellulant
paymentMethod.issuer Specify an issuer to skip the MNO selection step and switch the shopper directly to the page of the issuer. For example, ORANGE_CI.
reference -white_check_mark- Your unique reference for this payment. Keep the value to less than 15 characters as some MNOs restrict using longer values. If reference is longer than 15 characters, it will be stripped but not rejected.
countryCode The country's two-letter country code.
returnUrl -white_check_mark- URL to where the shopper should be taken back to after a redirection. The URL can contain a maximum of 1024 characters and should include the protocol: http:// or https://. You can also include your own additional query parameters, for example, shopper ID or order reference number.
shopperEmail The shopper's email address.
shopperName The shopper's first name and last name.
telephoneNumber The shopper's telephone number.

The following example shows how to make a payment request for 10 KES.

In the /payments response, note the action object. This contains the information needed to redirect the shopper.

Handle the redirect

  1. To complete the payment, redirect the shopper to the action.url returned in the /payments response.

    When using the HTTP GET method:
    For security reasons, when displaying the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.

  2. After the shopper is redirected back to your website, check the payment result by making a POST /payments/details request, specifying:

    • details: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.
  3. In the response note the following:

    • resultCode: use this to present the result to your shopper.
    • pspReference: our unique identifier for the transaction.

Present the payment result

Use the resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for African e-wallets and online banking are:

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful and proceed with the order.
You will receive the funds in 7 days.
Cancelled The shopper canceled the payment while on the African e-wallets and online banking website. Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.
Error There was an error when the payment was being processed. Inform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.
Refused The payment was refused by the shopper's bank. Ask the shopper to try the payment again using a different payment method.

If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for African e-wallets and online banking are:

eventCode success field Description Action to take
AUTHORISATION false The transaction failed. Cancel the order and inform the shopper that the payment failed.
AUTHORISATION true The shopper successfully completed the payment. Inform the shopper that the payment has been successful and proceed with the order.

Test and go live

Make a test payment then follow Cellulant's payment simulation instructions. Use the test credentials provided by Cellulant.

Then check the status of the test payment in your test Customer Area > Transactions > Payments.

Before you can accept live payments, you need to submit a request for Cellulant in your live Customer Area.

See also