Platform/Orchestrator
One portal,
every provider.
A merchant-facing platform that brings FawryPay, Paymob, PayTabs, Kashier and bank card schemes (Mastercard via partner bank) together. Merchants onboard once, enable the channels they're contracted for, create bills and invoices, and share pay-links — the platform routes by policy.
Outcomes
One orchestration layer instead of one-off pipes to every PSP.
Enable or sunset channels per merchant with policy, not code deploys.
Operator and customer journeys in EN or AR without parallel products.
How it works
Capture KYC, contracts, and channel entitlements once.
Turn on PSPs and card rails the merchant is contracted for.
Create invoices, pay-links, or hosted checkout sessions.
Send each payment to the allowed channel with failover rules.
Unified statuses and exports across channels.
Security & operations
- Role-based access to merchant and operator consoles
- Audit trail on routing and configuration changes
- Maker-checker for sensitive policy updates
Product preview
Integrations
Integration snippet
Example request shape for sales and solution engineering — replace endpoints and credentials with your environment.
curl -sS https://api.flagship.example/v1/orchestration/invoices \
-H "Authorization: Bearer $FLAGSHIP_TOKEN" \
-H "Content-Type: application/json" \
-d '{"merchant_id":"m_8KQH","amount":{"value":"1250.00","currency":"EGP"},"scheme":"Meeza"}'Where this product sits
Four layers — from people-facing surfaces down to durable records.
Compliance & attestations
- Orchestration APIs do not store PAN — card data stays in the certified gateway domain.
- Maker-checker applies to routing rules, fee profiles, and settlement calendars.
- SOC 2 Type II and PCI scope are aligned to your deployment model during onboarding.
FAQ
No. Merchants integrate with Flagship; Flagship integrates to contracted channels on their behalf.
Yes. Routing is policy-driven per merchant, amount, currency, and channel health.
No. RTL layouts and copy workflows are first-class across operator and customer surfaces.
Next step
Map Payment Orchestrator to your stack in a working session — no slide-only promises.