Payment gateway · BYO-MID
Your MID.
Our gateway.
A payment gateway connects your checkout to your acquiring bank. LekkaPay's gateway is built for merchants who hold their own merchant ID: you keep your acquiring relationship and your rates, and we provide the cloud-native technology layer in between.
LAST UPDATED ·
Acquirer connectivity
Which banks can I connect to?
If your bank runs Mastercard Payment Gateway Services or Cybersource, we can route to it. Direct integrations cover South Africa's major acquirers.
- Absa Direct integration
- Nedbank Direct integration
- MPGS Any MPGS-connected acquirer
- Cybersource Any Cybersource-connected bank
Instant EFT rides alongside your card acquiring: pay-by-bank via Ozow covers all major South African banks, with Nigeria served through NIBSS. See Instant EFT.
On the gateway
Everything in the payment path.
- Smart routing Transactions routed to your acquirer with retry logic and full lifecycle visibility.
- Frictionless 3DS2 3-D Secure 2 with frictionless flows preferred, so security does not cost you conversions.
- Token vault Serverless, PCI-isolated card storage for one-click and recurring payments.
- Risk engine Real-time scoring, velocity checks and per-merchant allow and block lists.
- Reporting & reconciliation Settlement statements, decline analytics and a back office your finance team will like.
- Enterprise support A named engineer who knows your integration, not a ticket queue. Live status, always public.
How it works
How it works
-
Your customer pays at your checkout
Hosted checkout, API or plugin - card data goes straight into the LekkaPay vault, never your servers.
-
LekkaPay authenticates and screens
3-D Secure 2 with the frictionless flow where risk allows, plus real-time fraud scoring before authorisation.
-
We route to YOUR acquirer
The authorisation goes to your acquiring bank under your MID - your rates, your settlement, your relationship.
-
You reconcile in one back office
Settlements, fees and declines in one view, whatever the acquirer.
What a gateway does - and what LekkaPay's does differently
Every gateway moves an authorisation from a checkout to an acquirer. The differences that matter are on either side of that hop. Before it: LekkaPay runs 3-D Secure 2 with the frictionless exemption path, so low-risk customers never see a challenge screen, and a real-time risk engine screens the transaction while the authorisation is in flight. After it: settlements from your acquirer are reconciled against transaction records automatically, so your finance team stops matching spreadsheets.
Acquirer connectivity
Acquirer compatibility is the first question every merchant with a MID asks, so here is the answer plainly: direct integrations with Absa and Nedbank, plus compatibility with any MPGS-connected acquirer and any Cybersource-connected bank. If your bank runs Mastercard Payment Gateway Services or Cybersource - and most South African acquirers run one of them - LekkaPay can route to it. Instant EFT rides alongside via Ozow, covering all major South African banks, with Nigeria covered through NIBSS.
Built for the merchants acquirers take seriously
The gateway model assumes real volumes, and the platform is engineered accordingly: serverless, event-driven infrastructure on AWS that scales with your peak trading days, PCI DSS Level 1 compliance at the service-provider level, and a public status page - status.lekkapay.com - because uptime claims should be checkable, not taken on faith.
- acquiring routes - Absa, Nedbank, any MPGS-compatible acquirer, any Cybersource-connected bank
- 4
- LekkaPay acquirer connectivity, 2026
The back office
What does the gateway look like in use?
A live transaction monitor - every approval and decline as it settles.
Switching
Graduating from an aggregator?
Bring your tokens with you.
The question every migrating merchant asks first: do my customers' saved cards survive the switch? Honest answer: usually yes. Card tokens can be migrated between PCI DSS compliant providers with the schemes' cooperation, and we plan that migration with you before anything moves.
We run the old and new integrations in parallel through cutover, so recurring customers never notice, and because merchant accounts and the gateway share one API, merchants who start on LekkaPay merchant accounts and later secure their own MID switch models without re-integrating at all.
FAQ
Gateway questions, answered.
What is a BYO-MID payment gateway?
A gateway for merchants who bring their own merchant ID. You hold the acquiring relationship and negotiate your own rates with your bank; LekkaPay provides the checkout, routing, tokenisation, risk and reporting layer between your store and that bank.
Which acquiring banks does LekkaPay connect to?
Direct integrations with Absa and Nedbank, plus compatibility with any acquirer connected through Mastercard Payment Gateway Services (MPGS) or Cybersource. If your bank runs either platform, we can route to it.
Can I move from an aggregator to my own MID without re-integrating?
Yes. Merchant accounts and the gateway run on the same API and back office, so a merchant who starts on LekkaPay merchant accounts and later secures their own MID switches models with configuration, not a rebuild.
Do my customers' saved cards survive a migration to LekkaPay?
Usually, yes. Token migration between PCI DSS compliant providers is an established process run with the schemes' cooperation. We scope it early, plan the cutover with you and run both integrations in parallel until your tokens are home.
What does the gateway cost?
Gateway pricing is tailored to your volumes and acquiring setup. Tell us about your MID and current flows and we will map the integration and the commercials together.
One platform, two models.
Start on LekkaPay merchant accounts or bring your own MID - same API, same back office, no re-integration.