Merchant onboarding is a quarter-long project
Each new merchant means duplicated KYC, channel setup, and status models across gateway, PSP portals, and finance.
02 · Processors & PSPsMulti-tenant rails.
Multi-tenant rails.
Merchant velocity.
Run a multi-tenant gateway and orchestrator with MPGS and regional PSP connectors already in the product — onboard merchants in days, route by policy, and close settlement without rebuilding the stack.
Built forProcessors, PSPs, and acquiring platforms that need multi-tenant merchant onboarding, routing, and settlement across card and regional rails
Operating model
Multi-tenant gateway + orchestrator
Rails in product
MPGS · regional PSPs · policy routing
Operator controls
Maker-checker on rules, batches, overrides
What this segment is solving
Framed for Processors, PSPs, and acquiring platforms that need multi-tenant merchant onboarding, routing, and settlement across card and regional rails — not generic payments pain.
Routing lives in application code
Failover and acceptor preference require releases; ops cannot change policy when a regional PSP degrades.
Settlement and fraud are bolted on late
Gateway goes live first; fee batches, reconciliation, and defendable fraud overrides arrive as afterthoughts.
Flagship modules for this segment
Each module maps to a concrete job — adopt only what the programme needs.
Orchestrator
Merchant portal, KYC handoff, invoices/pay-links, and policy routing across contracted regional PSPs and card rails.
Gateway
Multi-tenant card acceptance (including MPGS-class flows) with acquirer agility for your merchant book.
Switch
When you also run POS or ISO switching for merchants — terminal estate under the same operator posture.
Fraud
Per-tenant and portfolio rules with case queues; assisted suggestions require human approval before production.
Wallet
Optional closed-loop or marketplace balances when merchants need stored value beside card/PSP acceptance.
Settle
Merchant settlement calendars, fee batches, and exports across acquirers and orchestrated channels.
How it works
- Tenant + portfolio model
Isolate merchant books; define operator roles and dual-control boundaries.
- Onboard merchants once
Capture KYC, contracts, and channel entitlements shared across gateway and orchestrator.
- Enable rails
MPGS/card profiles and regional PSP adapters the merchant is contracted for.
- Route by policy
Amount, currency, merchant, and channel health choose the acceptor — with failover lists.
- Govern risk + settlement
Fraud dual control and settlement batches close the operator day.
Core capabilities
Each capability names a concrete mechanism — not a marketing adjective.
Multi-tenant merchant book
Tenant isolation for merchant portfolios with shared platform controls — operators see one onboarding journey, not N vendor portals.
Structured merchant onboarding
Commercial, legal, and know-your-merchant steps captured once and reused when enabling additional channels.
Policy routing across rails
Orchestrator evaluates merchant, amount, currency, and channel health; failover is versioned configuration, not a hotfix.
MPGS + regional PSP surface
Card acceptance via gateway profiles alongside regional acceptors (e.g. FawryPay, Paymob, PayTabs, Kashier) as first-class channels.
Assisted routing suggestions
Optional AI flags underperforming channel combinations for human approval — never auto-promotes production policy without maker-checker.
Settlement and fee ops
Settle drives merchant calendars and fee batches so finance reconciles orchestrated and gateway volume in one posture.
Fraud with operator trails
Rules and cases per tenant/portfolio with audit on overrides — defendable to partners and internal risk.
Modular stack adoption
Start with orchestrator + gateway; add switch, fraud, wallet, or settle when the programme needs them.
Where this sits vs alternatives
You avoid owning N PSP SDKs, status normalizers, merchant portal UX, and settlement export plumbing — Flagship maintains the connector and operator surface.
Single-acceptor portals lock merchants to one rail. Flagship treats regional PSPs and card rails as swappable channels under one policy model.
Designed around MENA regional acceptors plus MPGS card rails — not a card-only mesh with regional PSPs bolted on.
Integration experience
Integrate once to Flagship APIs and consoles; channel credentials stay in adapter configuration. Sandbox merchants and simulators are issued during onboarding.
MPGSFawryPayPaymobPayTabsKashierSettlement exportsWebhooks / REST
Typical path
- Week 0–1Tenant, API keys, and sandbox merchants provisioned in the first working week
- Week 1–3Map channels + routing policies for a pilot merchant cohort
- Week 3+Fraud dual control, settlement UAT, and production checklist
Request sandbox from contact (intent=sandbox, industry=processors-and-psps). Credentials and channel simulators during sales-assisted onboarding.
Security and compliance
Multi-tenant controls you can operate — RBAC, dual control, and audit trails.
Tenant isolation
Merchant books and operator scopes are separated by tenant policy with logical isolation and optional dedicated tenancy.
Maker-checker
Routing rules, fee profiles, and settlement calendars can require dual control before activation.
Audit trail
Onboarding, routing, and financial overrides retain actor, timestamp, and reason codes.
FAQ
Deal-killing objections, answered plainly.
Can merchants integrate with each PSP separately?
They do not have to. Merchants integrate with Flagship; Flagship talks to contracted channels. Direct PSP contracts can still sit commercially with you or the merchant.
Do you support MPGS and regional PSPs together?
Yes. Gateway covers card/MPGS-class acceptance; Orchestrator treats regional PSPs as policy-routed channels alongside card rails.
Will AI change production routing automatically?
No. Assisted suggestions can recommend policy changes; promotion still goes through your maker-checker path.
How fast is merchant onboarding really?
Structured onboarding reuses KYC and entitlements across channels so ops are not repeating forms per PSP — calendar depends on your KYC depth and channel contracts.
What if a PSP we need is missing?
New adapters are scoped as integration work with lead time based on provider API maturity. Bring the provider name and API docs to a walkthrough.
Related products
Stand up the merchant book
Book a technical walkthrough to map multi-tenant gateway, orchestration, routing, and settlement — or request sandbox for a pilot cohort.