← Back to the directory

Payment channel profile

Fawry

PSP / aggregator · Egypt

EgyptPrimary marketMain service market
PSP / aggregatorRole / typePayment aggregator
Usually requires a local entityEntity requirementOnboarding conditions
T+2 / T+3SettlementPayout timing

Overview

Fawry is listed as payment aggregator in the LocalPayMap public directory. Use this page to prepare due-diligence questions; product availability and terms must be verified directly.

Role in the payment stack

PSP / aggregator

This is closer to a provider route than a buyer-facing payment method. Confirm which local methods it can enable, where your merchant entity can be onboarded, and who handles settlement, refunds, and disputes.

Merchant usage and connection route

Fawry in the payment stack

Fawry is relevant for Egypt-focused merchants that need local acceptance beyond international cards, including cash collection, bill-style payment, wallet or card-adjacent flows depending on the provider route. Evaluate it for customer reach, checkout instructions, payment confirmation, reconciliation, refunds, and operational support.

Connection route

Merchants may work with Fawry directly for a merchant product or access Fawry-supported flows through a PSP, gateway, bank, platform, or cash-collection aggregator. Confirm whether the route is direct or bundled, which Fawry product is involved, and who owns settlement, support, and transaction reporting.

Verification questions

  • Which Fawry product or merchant payment flow is required: online, bill reference, cash collection, wallet, card, or POS?
  • Is the route direct with Fawry or through a named PSP, gateway, bank, platform, or aggregator?
  • How are payment instructions, expiry, confirmation callbacks, refunds, reversals, and reconciliation references handled?
  • What Egyptian entity, documentation, category, customer-service, and settlement requirements must be reviewed?
  • Who resolves customer payment disputes, late confirmations, failed references, and operational exceptions?

Merchant caveats

  • Fawry-branded acceptance can mean different products with different operational requirements.
  • Cash collection confirmation timing may not behave like card authorization.
  • Refund, expiry, and reconciliation processes should be verified before launch.
  • Provider examples are discovery examples only, not recommendations or support evidence.

Provider examples to verify

FawryAcceptCIB Pay Nowareeba EgyptAman

Related markets

Egypt

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Sources

What merchants should confirm

  • Whether the product is available to merchants incorporated outside the target country.
  • Whether a local entity, local bank account, licence, or local tax registration is required.
  • Supported checkout flows, currencies, refunds, disputes, reconciliation fields, and payout options.
  • Industry restrictions, reserve policies, onboarding documents, and implementation support.

Merchant eligibility

A local entity, local account, or additional licensing may be required.

Pricing and settlement

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.

Settlement timing, payout currency, foreign exchange, reserves, and withdrawal rules must be confirmed with the provider.

Capability verification checklist

Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.

  • Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
  • Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
  • Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.

Official links to open

Commercial terms to confirm

Pricing modelpsp or aggregator quote
Pricing basisofficial public pricing or terms
Fields still to confirm
  • Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.

Integration route to confirm

No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.

Fields still to confirm
  • API / checkout route: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.

Operational features to confirm

No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.

Fields still to confirm
  • Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.

Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.

Visit the official website