How do I add card payments to my app in Kenya?
By Bonaventure Ogeto, Founder and CEO, Mctaba Labs
Published
You add card payments by opening an account with a payment gateway that serves Kenyan businesses, then having your developer connect its checkout to your app. The gateway collects the card details, runs the bank's security check and pays you out to a bank account or M-Pesa. You never handle or store card numbers yourself.
M-Pesa will carry most of your payments in Kenya, and for a while it may carry all of them. Then one of three customers turns up. A company that pays with a corporate card. A Kenyan abroad buying for family at home. A subscriber who wants to be billed every month without approving a prompt each time, and who would sooner save a card than set up an M-Pesa standing order. Each of them is better served by a card, which a Till does not accept.
Adding cards is less work than founders fear and carries one risk they rarely hear about until it happens. This guide covers both.
Who is actually involved when a customer pays by card?
Five parties, and you only ever speak to one of them.
- The cardholder, your customer.
- The issuer, the bank that gave them the card.
- The card network, Visa or Mastercard, which carries the request between banks.
- The acquirer, the bank or licensed institution that accepts card payments on behalf of businesses.
- The gateway, the company whose software you connect to. It sits in front of the acquirer, so you sign one agreement and get one dashboard.
When your customer taps Pay, the gateway sends the card details through the network to the issuer, the issuer approves or declines, and the answer comes back in seconds. The money itself moves later, in a batch, and reaches you after the gateway has taken its fee.
You do not apply to Visa. You choose a gateway. In Kenya, payment service providers are authorised by the Central Bank of Kenya, which publishes a directory of them. Checking that directory, and the gateway's own compliance page, is a sensible first filter.
What do I need before a gateway will switch cards on?
Business documents, a payout account and a product the gateway can look at.
The exact list depends on your business type. Paystack's requirements for Kenya, for instance, run from an ID and a personal account for an unregistered starter business, to a registration certificate and KRA PIN for a sole proprietor, to a certificate of incorporation, CR-12, company KRA PIN and a matching company bank account for a limited company. Other gateways ask for similar papers, and several also want a live website or a description of what you sell.
Gather these before the build begins. Approval can take longer than the code, and you cannot hurry it.
Should customers pay on the gateway's page or inside my app?
Use the gateway's own checkout. There are two usual ways to do it, and both keep card details away from your servers.
| Compared on | Redirect to a hosted page | Pop-up or embedded form |
|---|---|---|
| What the customer sees | They leave your app for the gateway's payment page, then return | A payment window opens on top of your page |
| Who collects the card number | The gateway | The gateway, through its own form |
| Effort to build | Lowest | A little more |
| Feels like | A trusted bank-style page | Part of your product |
| Good for | First versions, low-trust audiences, payment links | Polished web apps and repeat buyers |
Paystack's documentation describes exactly these two options, a redirect to a checkout link and a pop-up on your page. Other gateways have their own versions, so ask each one which it offers.
There is a third option, which is to design your own card form and pass the numbers along yourself. Do not take it. It makes you responsible for the security of every card that passes through, which the PCI section below explains.
One instruction for your developer, straight from the gateway's own documentation: the app must confirm with the gateway that a payment succeeded before it delivers anything. A customer landing back on your "thank you" page proves nothing by itself.
If you want to see how one checkout handles several payment methods across countries, read one checkout for M-Pesa, mobile money and cards. For a build walkthrough, see a Kenyan e-commerce checkout that accepts M-Pesa and cards.
What is 3-D Secure, and why does my customer get a code from their bank?
It is the issuer checking that the person paying is the real cardholder. Visa calls its version Visa Secure and describes it as an added layer of identity verification before a payment is authorised, with data exchanged between the business, the card issuer and, when needed, the customer.
In practice the customer enters their card, and their bank either approves quietly in the background or asks for proof, usually a one-time code by SMS or an approval in the banking app. Your gateway runs this step for you. You do not build it.
It matters to you for two reasons. It adds a step where a few customers drop off, so the screen before it should say "your bank may ask you to confirm". And it protects you. Stripe's guide to the standard explains that when a payment is authenticated this way, liability for chargebacks caused by fraud shifts from the business to the customer's bank. Ask your gateway whether it applies to every card payment or only some.
What is a chargeback, and how do I protect the business?
A chargeback is a card payment being pulled back after you have been paid. This is the risk M-Pesa-first founders do not expect.
The cardholder calls their bank and disputes the charge. Visa defines a dispute as the reversal of the value of a transaction by the card issuer, passed back through the acquirer to the business. Paystack's documentation lists the usual reasons: the customer says they never got what they paid for, they do not recognise the charge, the card was used without permission, or there was an error such as being billed twice.
The gateway then asks you to accept or to answer with evidence, and the clock is short. Paystack's developer documentation says disputes should be handled within 16 hours, after which it accepts them on your behalf and refunds the customer from your balance. Ask your own gateway for its exact window in Kenya and who gets the email.
Four habits prevent most disputes:
- Trade under a name the customer will recognise on a statement.
- State your refund and cancellation terms before they pay.
- Keep a record of delivery for every order: a login, a download, a signed delivery note.
- Refund quickly when you are in the wrong. A refund is cheaper than a dispute.
What is PCI DSS, and why must I never store card numbers?
PCI DSS is the security standard the card industry applies to anyone who stores, processes or transmits card data. The more of that data touches your own systems, the more of the standard you must prove you meet, up to formal audits.
The way out is simple: let the gateway's page or form collect the card. Stripe's guide to the standard puts it clearly. When the payment fields are served from the provider's systems, the customer's card information never touches your servers, and your compliance burden drops to the lightest level. Write your own code to handle card numbers and you take on the most demanding one. Paystack states on its compliance page that it is certified at Level 1, the strictest tier for service providers.
So make it a rule from the first day. No card numbers in your database, in a spreadsheet, in an email, in WhatsApp or on paper. For repeat billing, the gateway gives you a token after the first authenticated payment, along with harmless details such as the card brand and the last four digits. You store the token. The card stays with the gateway.
How and when does the money reach me?
In a batch, a day or more after the sale, minus the fee.
As of 19 November 2026, Paystack's Kenya pricing page lists 2.9% for a local card and 3.8% for an international card, with payout to your bank account or M-PESA wallet in two working days. Flutterwave's Kenya page lists 3.2% for local cards and 4.8% for international transactions, before VAT, with local payments paid out the next day. Read both pages again on the day you choose, since they change.
On both pages an international card costs more than a local one. If you expect buyers abroad, price with that rate in mind.
What should I ask a gateway before I sign up?
Put the same ten questions to each provider and compare the answers side by side.
- Are you on the Central Bank of Kenya's directory of authorised payment service providers?
- Which documents do you need for my business type?
- Which cards do you accept, and are international cards on by default?
- What is the fee for a local card and for an international card, and is VAT extra?
- When do I get paid, and to a bank account, M-Pesa or both?
- Can I charge and be paid out in dollars?
- Is 3-D Secure applied to every card payment?
- How do disputes work, how long do I have to respond, and is there a fee per dispute?
- Can I save a card for repeat billing, and does it work for cards in Kenya?
- If I leave, can my customers' saved cards move with me?
The last question is easy to skip and costly later. Saved cards live with the gateway. If they cannot be moved, changing provider means asking every subscriber to enter their card again.
Key takeaways
- You do not deal with Visa, Mastercard or a card-acquiring bank directly. A gateway does that for you.
- Use the gateway's own checkout page or payment form. Never collect card numbers in your own form.
- 3-D Secure is the bank's code or app prompt. It adds a step and protects you against fraud claims.
- A card payment can be reversed weeks later through a dispute. Keep proof of delivery and answer notices fast.
- Compare gateways on the international card rate, payout time and dispute process, not only the headline fee.
- Offer cards beside M-Pesa, not in place of it.
Frequently asked questions
- Do I need a limited company to accept card payments?
- Not with every gateway. Paystack, for example, publishes requirements for unregistered starter businesses and sole proprietors as well as companies. What changes is the paperwork and the payout account. A registered company needs a bank account in the company's name.
- Can customers pay by card and M-Pesa on the same checkout?
- Yes, with a gateway that supports both. Paystack, for example, lists card, M-PESA and Apple Pay as options on its Kenya checkout, and the customer picks. For a Kenyan audience that is the right default, because a buyer who owns a card may still prefer to pay from their phone.
- How long does it take to go live with card payments?
- The build is usually the short part. The longer wait is the gateway approving your business documents, and that depends on how complete they are. Submit the documents before development begins, so approval and the build run side by side.
- Can I charge a customer's card every month without asking again?
- Yes, if the gateway supports it. After a first successful payment, which the customer authenticates with their bank, the gateway gives your system a token that stands in for the card. Your app can charge that token later. You still never see or keep the card number.
- Is it safe to take card details over WhatsApp or the phone?
- No. A card number written in a chat or on paper is exactly what the card security rules exist to prevent, and it leaves you responsible if it leaks. Send the customer a payment link from your gateway and let them type the details into its page.
Sources
- Pricing for Kenya, Paystack. Checked on 19 November 2026.
- Compliance requirements for Kenya, Paystack Support. Checked on 19 November 2026.
- Accept Payments, Paystack Developer Documentation. Checked on 19 November 2026.
- Recurring Charges, Paystack Developer Documentation. Checked on 19 November 2026.
- Manage Disputes, Paystack Developer Documentation. Checked on 19 November 2026.
- Compliance at Paystack, Paystack. Checked on 19 November 2026.
- Pricing, collections for Kenya, Flutterwave. Checked on 19 November 2026.
- Visa Secure with EMV 3-D Secure, Visa. Checked on 19 November 2026.
- Dispute Resolutions, Visa. Checked on 19 November 2026.
- What is PCI DSS compliance?, Stripe. Checked on 19 November 2026.
- 3D Secure 2, Stripe. Checked on 19 November 2026.
- Directory of Authorized Payment Service Providers, as at 10 August 2026, Central Bank of Kenya. Checked on 19 November 2026.
