About — NectPay

Why we exist

Sending money into Africa costs more, takes longer, and fails more often than sending it almost anywhere else in the world — not because the demand isn't there, but because the infrastructure was never built for it as a primary market. Most payment companies treat African corridors as an edge case bolted onto systems designed for the US, UK, and EU. We started from the opposite assumption: design for Lagos, Nairobi, and Accra first, and the result will work everywhere else too.

That single decision — build for the hardest corridor first, not the easiest — shapes almost everything else on this page.

Where we are right now

We believe in being precise about status rather than rounding up. Here's exactly where NectPay stands today:

Incorporation

Complete

FCA Authorisation

Not yet applied

Core engine

Built

Live pilot clients

Pre-launch

We'll update this strip as each milestone changes — not as a marketing gesture, but because a payments company asking for trust should make its actual status easy to check, not easy to assume.

The company, formally

Corporate details

Legal nameNectPay Ltd

Company number16134387

JurisdictionEngland & Wales

Registered addressRegistered in England & Wales — address on file at Companies House (No. 16134387)

FCA statusTechnology layer only — settlement via authorised partner (Global Remit Financial Services Ltd, FCA Ref. 930827). NectPay PI authorisation application not yet submitted.

ICO registrationICO registration number: ZC195350

Full detail on our regulatory approach and roadmap is on the Security & Compliance page. Legal terms governing use of the service are in our Terms of Service.

What we've actually built

Rather than describe NectPay in the abstract, here's what exists today as working architecture — not slideware:

⚙️Compliance-first routing

Every payout is evaluated against destination-jurisdiction KYC/AML rules before any rail is contacted — not after. A failed check means no rail is ever touched, not a payment held mid-transfer.

📈Multi-source FX engine

Every conversion is quoted across multiple liquidity sources and routed through the best effective rate, disclosed before you confirm — not a single opaque rate with margin hidden inside it.

🔁Automatic rail fallback

If the top-ranked rail fails, the engine automatically retries the next-best option — the mechanism behind our guaranteed delivery commitment, not a manual retry process.

🔒Sender tokenisation

Partner rails never see a client's real business identity — only a one-way reference token. Rails deliver funds without ever learning who's sending them.

You can run all four of these against live logic — not a mockup — in our developer demo.

How we think about the next 18 months

Done

Incorporation & core engine architecture

NectPay Ltd registered in England & Wales. Compliance, FX, and routing engine built and demonstrable.

In progress

FCA Payment Institution authorisation

Application not yet submitted. Intended as our primary regulatory base ahead of individual African market licensing. NectPay currently operates as a technology layer only — regulated partner institutions handle all money movement.

First enterprise pilots live on our Phase 1 corridors, with Nigeria-specific data residency infrastructure in place ahead of the CBN's January 2027 deadline.

Later

Corridor expansion & PAPSS connectivity

Expanding to 20+ African markets and connecting into the Pan-African Payment and Settlement System as it scales — bringing same-day, transparent payouts to every major African corridor.

Infrastructure for the corridor everyone else treats as an afterthought.