Eslam Negm
Chief Executive Officer
EST. CAIRO · 2022
The FintechArsenal.
The foundational layer for modern fintech. Modular systems — gateway, switch, orchestration, wallet, fraud, settlement and beyond — on one SaaS platform. One ledger. One API. One suite to learn.
flagship.
flagship.
NOW SHIPPING
Payment OrchestratorPayment GatewayPayment SwitchFraud EngineDigital WalletSettlement & Reconciliation
ONE PLATFORMRegional-first
MENA rails and operator workflows by design
Modular
Adopt gateway, switch, wallet, or the full stack
Governed
Maker-checker on rules, batches, and overrides
Integrated
MPGS · regional PSPs · schemes you already use
Ecosystem · Pre-integrated
Product surfaces
Consoles and flows your operators and customers recognise — same platform, one suite to learn.
Wallet
What it is
01 — POSITIONING
Big payment stacks fray across vendors and glue, not in a single outage.
Flagship is one modular SaaS platform — gateway, switch, orchestration, wallets, fraud, settlement, and what follows.
Maker-checker where it matters, and one control plane your operators actually run.
Maker-checker controlsModular deploymentOperator-ready APIs
What we don't do
Replace your core banking, your general ledger, or your KYC vendor. Flagship sits beside them — it does not pretend to be them.
What we do better
Maker-checker governance on every rule, batch and override. Modular by design — adopt what you need.
Who we're for
Banks modernising card and POS rails. Processors orchestrating partners. Enterprises and PSPs running merchant portfolios.
The platformModular products,
Modular products,
one platform.
Compose gateway, switch, fraud, wallet, and settlement — shared identity and audit from day one.
01
Payment Orchestrator
One portal, every provider.
02
Payment Gateway
MPGS-integrated card acceptance.
03
Payment Switch
ISO 8583 switching for POS estates.
04
Fraud Engine
Rules-first. Explainable by design.
05
Digital Wallet
Multipocket by design.
06
Settlement & Reconciliation
The controlled end-of-day.
01 · ORCHESTRATOR
Payment Orchestrator
One portal,
every provider.
merchant_portal · invoice #INV-91823
Routed by policy
AMOUNT REQUESTED
EGP 2,480.00
Enabled channels
FawryPay
Cash + e-wallet
Paymob
Online cards
PayTabs
MENA cards
Kashier
MENA cards
Card via bank
MPGS · scheme
Route invoices and pay-links across FawryPay, Paymob, PayTabs, Kashier, and MPGS-backed card rails from one merchant portal — policy decides the channel, not a one-off integration.
01One relationshipOne integration with your platform instead of many separate vendor integrations.
02Structured onboardingCommercial, legal, and know-your-merchant steps captured once and shared across channels.
03Pay-links + checkoutShareable links and hosted checkout. Customers pay through the channel you allow.
04Unified payment statusNormalize provider callbacks into one lifecycle operators can reconcile.
02 · GATEWAY
Payment Gateway
MPGS-integrated
card acceptance.
gateway · checkout flow · merchant_8KQH
1Register orderamount · currency · items
2Checkout sessionMPGS · 3DS2
3Present checkouthosted · embedded
4Webhooksfinalize · capture
Run card-not-present acceptance on Mastercard Payment Gateway Services (MPGS) with multi-acquirer mapping, hosted or embedded checkout, 3DS2, and webhooks your ops stack can reconcile.
01MPGS integrationRegister order → create checkout session → present checkout → receive webhooks → finalize.
02Multi-acquirer routingRoute to the right acquirer per merchant, scheme or BIN. Configurable failover.
03Hosted or embeddedDrop in our checkout, embed in your flow, or build white-label from the API.
04Merchant onboardingOnboarding workflows that scale from a single merchant to enterprise portfolios.
03 · SWITCH
Payment Switch
ISO 8583 switching
for POS estates.
switch · TMS · velocity rules · v37
active
01if amount_velocity_5m > 8x avg→ throttle terminal
02if decline_storm in 60s→ block terminal · alert
03if PAN in hotlist→ decline · log
04if MID + BIN low-risk→ approve · on-us route
05if MID + BIN cross-scheme→ approve · off-us route
06if * (default)→ approve · cost-min
● APPROVED14:08:21
SALE · EGP
489.50
CARD•••• 4242 · VISA
TERMTID 8KQH · MID 91823
AUTH62ms
3DSok
1
2
3
4
5
6
7
8
9
*
0
#
Authorize and route POS card messages (SALE, VOID, REFUND) over ISO 8583 with on-us / off-us policy, terminal management, and velocity controls your operations floor can stage safely.
01ISO 8583 message processingIngest, validate, switch and respond with auditable event logs.
02Terminal Management (TMS)Remote configuration, health, hotlists and velocity rules — staged policy rollout.
03Velocity controlsLimits, counters, decline-storm detection, auto-throttle or block terminal.
04Operator reportingEOD, settlement totals, on-us / off-us splits, decline & timeout analysis.
04 · FRAUD
Fraud Engine
Rules-first.
Explainable by design.
fraud · event_4QH8 · cnp
score 0.72 → step-up
Decision breakdown
Base risk · CNP
BIN tier · medium
Velocity 5m > 4x
Device · new
Allowlist hit
OUTCOME · STEP-UP
Send to 3DS2 challenge before authorization.
Evaluate payment events in real time with versioned rules, enriched context, and deterministic outcomes — then apply the same policy vocabulary across gateway (CNP) and switch (POS).
01Auditable decisionsEvery decision traces to rules and signals — for regulators, disputes and reviews.
02Same engine, both railsWorks across gateway (CNP) and switch (POS) so policies stay consistent.
03Versioned rulesMaker-checker rollout. Stage in shadow mode. Promote with reason codes.
04Rich contextVelocity, allow/block lists, BIN & MCC tiers, country controls, device & geo signals.
05 · WALLET
Digital Wallet
Multipocket
by design.
Customer wallet
Pockets
Launch multipocket wallets — cash, points, savings, tickets, or operator-defined types — with typed units, conversion rules, and P2P flows behind your brand.
01Type + units per pocketMoney, points, tickets, savings units. Same model, different semantics.
02User-defined pocketsMultiple pockets of the same type allowed. Goals, labels, icons per pocket.
03Internal transfersPocket → pocket. Instant when same type. Conversion rules when crossing types.
04External wallet ↔ walletQR or customer reference for peer transfers with fees and arrival-time disclosure.
06 · SETTLEMENT
Settlement & Reconciliation
The controlled
end-of-day.
settlement · 2026-05-10 · maker-checker
4 batches
CYCLEBATCHGROSSFEENETSTATUS
T+0 · openB-91823 · EGP1,420,8000.55%1,412,985open
T+0 · lockedB-91822 · EGP893,2100.42%889,459locked
T-1 · paidB-91821 · EGP1,642,0000.68%1,630,838paid out
T-1 · paidB-91820 · USD212,4000.05%212,294paid out
Turn live transactions, fees, and beneficiary splits into single-currency batches finance can approve — then reconcile against acquirer, SWIFT, and GL files without spreadsheet bridges.
01Single-currency batchesSame settlement day. Same currency. Eligible payment states only.
02Processing vs value dateBoth stored so finance can align with SWIFT or local clearing.
03Bank file importCSV or bank-specific formats to populate expected lines or validate totals.
04Maker-checker overridesAdjustments require approvals and reason codes in the audit trail.
Who runs on Flagship
Built for the institutions moving money.
Banks & FIs
Modernise card, switch and POS rails beside core banking — gateway, switch, fraud, and settlement without forklifting the GL.
Processors & PSPs
Multi-tenant gateway and orchestrator with MPGS and regional PSP connectors — onboard merchants, route by policy, close settlement.
Enterprises
One platform for treasury, finance and operations across your merchant entities, currencies and geographies.
Fintech startups
Ship a wallet, a neobank, or a marketplace without building gateway, switch, settlement and fraud yourself.
ReachOne platform,
One platform,
every market you operate in.
Engineered in Cairo, operated across MENA and beyond. Wherever your banks, acquirers and partners are, Flagship plugs into the same rails — ready to be localised for any regulatory regime you run in.
CAIRO · HQ
Engineering · operations
GCC
Partner integrations · acquirers
MENA & LEVANT
Card schemes · local rails
SELECTED EU & APAC
Corridor expansion · pilots
The teamPayments people who've shipped the systems
Payments people who've shipped the systems
you're trying to replace.
Engineers, payments operators, and risk specialists with careers spent inside MPGS, ISO 8583, settlement files and merchant onboarding. We are not a team that explains what fees are — we ship the engines that calculate them.
Mohamed Nasser
Chief Technology Officer
Marwa Wagdy
Head of Business Development and Partnerships
Replace fragmented vendors
with one platform.
Send us a message — we'll show you the product, map it to your stack, and tell you honestly where it fits — and where it doesn't.