Terms of Service

You are responsible for your account, your credentials and every operation sent from your project.

The business and transaction data you give us must be accurate, complete and kept current.

You may use the gateway only for lawful activity that matches what we reviewed during onboarding.

Fees are set per project in your merchant agreement. Reserves and holds, if any, are also defined there and not on this page.

We may limit or suspend access when there is a valid reason. We may update these terms and will show the revision date on this page.

These terms apply to any business that opens a merchant account with Payment Gateway Africa, connects a project, or sends operations through the gateway. The terms also apply to people who act on behalf of that business.

Payment Gateway Africa provides a payment gateway. It processes pay-ins from your customers and, where available for the method and project, payouts to recipients. It also sends merchant settlements. These are three separate flows. Each flow follows its own rules in your merchant agreement and in the technical documentation.

Your merchant agreement sets out the commercial terms for your project. If the agreement conflicts with these terms on fees, reserves, holds, settlement or liability, the agreement applies.

These terms do not cover how we handle personal data. Our privacy policy covers that, and our cookie notice covers the cookies this website uses.

There are two ways to connect to the gateway. One is a direct host-to-host (H2H) API. The other is a Hosted Payment Page that your customers open in a browser. Both are connection methods for one product. Neither is a white-label offering. Our integration guide explains both.

The gateway supports the local methods listed for each market. Kenya: M-Pesa (KES). Egypt: mobile wallet payments by phone number (EGP). Ethiopia: CBE Birr, M-Pesa and local transfers (ETB). Senegal: Wave and Orange Money (XOF). Mali: Wave, Orange Money and Moov Money (XOF). Guinea: Orange Money (GNF). Tunisia: D17 and Flouci (TND). Your project can use only the methods enabled for it. The country directory shows current coverage.

Payment Gateway Africa dispatches each merchant settlement on the day it falls due (T+0). This term describes when we release funds, not when they appear in your account. Posting times depend on your receiving bank and can vary.

The gateway reports operation statuses to you, the merchant, by postbacks and webhooks. We do not send notifications to your customers on your behalf. The webhooks documentation explains how these notifications work.

Existing merchants can ask us to add supported payment methods. Adding a method carries no extra connection fee, and the connection price does not depend on how many methods you enable.

You must name people who are authorised to use your account. You are responsible for what they do in the account.

Keep your API keys, project identifiers and dashboard logins confidential. Store them only on systems you control. Share them only with staff or contractors who need them.

Any operation sent with your valid credentials is treated as authorised by you. If you think a credential has been exposed or misused, tell us without delay. Then rotate or revoke it as the documentation describes.

You must keep your own systems maintained. This includes the server that receives postbacks and confirms operation statuses. The security overview lists the practices we expect from merchants.

We review your business before your project goes live. During that review, you must give us true and complete information about your business: its owners, its activity, its websites and its target markets. The AML and KYB process explains what we review and why.

Tell us promptly about any material change. Examples include new ownership, a new business model, new websites or new markets. We may ask for more documents at any time to keep our records accurate.

Each operation must carry correct data. That means the right amount, currency, country, method and reference. You are responsible for any problem caused by incorrect or incomplete data that you submit.

Use the gateway only for lawful goods and services. That activity must match what you declared and what we approved during onboarding. If you want to add a new type of activity, ask us for approval first.

You must not use the gateway to do any of the following:

• Hide where funds come from or where they go.
• Process operations for third parties who have not been onboarded.
• Split operations to get around limits or checks.
• Send test traffic through a live project.
• Interfere with the gateway, probe it, or overload it.
• Copy or resell access to it without our written permission.

You must follow the laws that apply to your business and to each market you serve. You must also follow the rules of each payment method you use.

Tell your customers clearly what they are buying, what it costs, and how they can get support. Our refund policy explains how refunds and reversals relate to the gateway.

Fees are set for each project and written into your merchant agreement. Pay-ins, payouts and settlement may each be priced separately. This page does not list any rates. The pricing page explains what affects a quote.

Reserves, holds, deductions and settlement conditions are defined only in your merchant agreement. If the agreement includes them, it also sets out how they apply and when they are released.

We may deduct agreed fees and amounts owed under the agreement before we send a settlement. Settlement reports show these deductions.

We may limit, pause or suspend a project, a method or a whole account for any of the following reasons:

• You break these terms or your merchant agreement.
• The information you gave us turns out to be inaccurate.
• We see activity that does not match the use we approved.
• A method provider, a legal requirement or a regulator requires it.
• We need to protect customers, other merchants or the gateway.

When we are allowed to, we will tell you the reason and what you need to do to restore access. Some restrictions can take effect at once. Others may follow a request for information.

Either party may end the relationship as set out in the merchant agreement. Obligations that existed before termination continue after it. These include fees owed, record-keeping, cooperation on disputes, and confidentiality.

We work to keep the gateway available. However, maintenance, incidents and decisions by method providers can affect service. When we post a notice about an incident or maintenance, it appears on the status page.

We may add, change or withdraw methods, markets or features. When a change affects a method your project already uses, we will try to give you reasonable notice.

You are responsible for your products, your customer relationships, and the content and accuracy of your operations.

The limits of each party's liability, and any compensation between the parties, are defined in your merchant agreement. These terms do not extend those limits.

We may revise these terms when the service, our processes or our legal obligations change. Each revision is published on this page with a new revision date.

Material changes will be communicated through your account contacts before they take effect, where reasonably possible. If you keep using the gateway after a change takes effect, you accept the revised terms.

To ask about these terms or your merchant agreement, write to us through the contact page. Choose the request type that fits your question. Include your company name and project identifier if you already have an account.