M-Pesa and mobile money
Fincra names M-Pesa and mobile money on the Kenya page. IntaSend names M-Pesa as a method next to cards. The customer approves on the handset. Keep that approval separate from the card fields.
A 2D payment gateway asks for the card number, the expiry date, and the CVV. In Kenya that card step sits beside M-Pesa, bank transfer, and other mobile money. The phone prompt for M-Pesa is not a card form, and a card payment can still ask for a one-time password when the card network requires it.
IntaSend’s explanation of a 2D payment gateway says the first check is the card number, the expiry, and the name, and the second check is the CVV on the back of the card. A 3D payment gateway adds an OTP sent to the phone number the bank holds. IntaSend says its own gateway is ready for 3-D Secure when the card network demands it. That is the opposite of a promise that every payment skips the password.
Fincra’s Kenya page lists debit and credit cards, bank transfers, M-Pesa, and mobile money as ways a customer can pay. M-Pesa is confirmed on the phone, through a prompt or a paybill the customer already knows. The customer is not typing a CVV into that prompt. A merchant that offers both still runs two flows.
Fincra names M-Pesa and mobile money on the Kenya page. IntaSend names M-Pesa as a method next to cards. The customer approves on the handset. Keep that approval separate from the card fields.
SeerBit Kenya says a merchant can accept cards and mobile money from one integration. The card path still collects card details. Mobile money does not.
Fincra lists bank transfers among pay-in methods. A transfer is a credit to an account. It is not a 16-digit card number plus a CVV.
Fincra describes payment links for a business with no website, and APIs for checkout, virtual accounts, and payouts. Paytota describes plugins, a no-code payment request, and APIs. The tool you pick does not change the difference between a card and M-Pesa.
IntaSend’s 2D article spends most of its length on why an OTP reduces fraud and chargebacks, then points Kenyan merchants to a 3-D Secure ready gateway that can also take M-Pesa. Read that as a warning, not as a ban on card fields. If you show a card form, say in the checkout what the shopper will type, and let the issuer add the password when the network asks. Fincra tells Kenya merchants it offers a dashboard, account managers, and one API across online and offline payments. SeerBit Kenya says the same integration can serve a small business or a large organisation, and that a white-label setup can sit on its infrastructure. Paytota lists e-commerce, marketplaces, banks, and business-to-business collections, plus a no-code request and a developer API.
A shop with no website can start from a payment link, which Fincra and the IntaSend customer notes both describe. A shop on WooCommerce or Shopify can start from a plugin, which Paytota and IntaSend both point to. A fintech that needs payouts can look at Fincra’s pay-out methods: local and international bank transfer, and mobile money. None of those tools changes the split between a card and M-Pesa. The link, the plugin, and the API are pipes. The confirmation is still either card details or a phone approval.
IntaSend also says banking services on its platform are provided by licensed banking partners. This page does not copy a licence number, because 2D Payment Gateway is not publishing one here. If a Kenyan buyer asks who holds the funds, the answer belongs in the contract with the partner that settles, not in a slogan. The same restraint applies to fees. Fincra’s Kenya headline mentions low fees and no hidden charges without putting a rate card in the opening. Do not invent a percentage. Ask for the schedule that matches your volume and your mix of cards and M-Pesa.
An M-Pesa confirmation is a prompt or a paybill on the customer’s phone. A 2D card authorization is the number, the expiry, and the CVV typed into a checkout. Offering both on one Kenyan store does not merge them. If the card network asks for 3-D Secure, the card path gains an OTP. The M-Pesa path still ends on the phone, whether or not the card path asked for a password.
IntaSend spells out the card checks in order. The number, the expiry, and the name are on the front of the card. The CVV is the second check, and card networks also call that code CID, CVC, or CSC. The OTP, when a 3D flow is used, is a third check sent to the mobile number the customer registered at the bank. IntaSend says that code is random and usually expires in about five minutes. A shopper who cannot see the phone cannot finish that third check. That is why a stolen card photo is weaker against a 3D flow than against a form that stops at the CVV. It is also why you should not advertise that a Kenyan checkout never asks for the password. The network can still demand it.
IntaSend argues that the extra password cuts fraud, cuts chargebacks, and reassures shoppers who look for a 3-D Secure mark. Those are arguments for keeping the password available, not statistics we are repeating as our own results. Chargebacks still need a person who can send evidence. Fincra’s Kenya page points merchants to a dashboard and to dedicated managers. Use that kind of access so a failed M-Pesa prompt and a declined card are visible as separate rows. A single “failed payment” label will send your team to the wrong rail.
Going live is a short sequence. First decide which confirmations you will show: M-Pesa, cards, bank transfer, or all three. Second, pick the pipe: a payment link if there is no website, a plugin if the store is WooCommerce or Shopify, or an API if the product is your own. Third, run one test on each confirmation, not one test that you then assume covers the others. Fourth, agree who settles the funds and on what schedule, in writing. Fincra lists KES among the currencies it says it can process, and it also lists payouts to bank accounts and mobile money. Settlement into a Kenyan business account is a commercial term. It is not created by labelling the card form 2D.
SeerBit Kenya describes reach across more than a dozen African countries from one integration, and local payment methods as the way to convert buyers who will not use a foreign card. That is useful when you sell outside Kenya. It does not remove M-Pesa for buyers who are in Kenya. Paytota describes the same idea from the other direction: one connection toward many markets, with cards, transfers, wallets, and cash named as categories. Keep the Kenyan phone confirmation in the list even if the catalogue of foreign methods gets longer.
Before the first real shilling moves, write down the three confirmations in the order the shopper will see them. If M-Pesa is first, the phone prompt should be the first thing after the amount. If the card is first, the number, expiry, and CVV come first, and the OTP appears only when the network asks. A bank transfer, when you offer it, needs its own reference so the credit can be matched. Fincra’s pay-in copy treats those methods as a list the customer chooses, not as one blended authorization. Copy that separation into the screen, then test each line with a small amount. A test that only checks the card will not tell you whether the M-Pesa prompt reached the handset. Record that test.
No. M-Pesa stays a phone confirmation. The card form collects the card number, expiry, and CVV.
No. IntaSend describes the OTP as the extra step on a 3D payment gateway, and says 3-D Secure runs when the card network demands it. Do not promise that the password never appears.
Fincra and IntaSend customer notes both describe a payment link. The link can still offer M-Pesa and cards as separate choices.
Send a name, a Telegram username, and an email. The form does not approve an account on its own.