Africa Fintech Regulatory Atlas · Egypt · FinTech
Egypt's FinTech rulebook: what the FRA expects non-bank fintechs to prove
Egypt regulates digital lending, insurtech and other non-bank financial services through Law No. 5 of 2022 and a growing stack of Financial Regulatory Authority (FRA) decrees. Since 2023 the FRA has set rules for infrastructure, digital identity, outsourcing, customer verification, cybersecurity and risk-scoring vendors, and in August 2026 it showed it will use them. This guide reads the official Arabic texts and turns them into the evidence a compliance team should hold.
Last reviewed: 11 October 2026 · Next review: 9 January 2027 · Written by Oluwafemi Ofobutu, founder
This guide is general information, not legal advice. The official text is the authority. Local legal interpretation should come from qualified counsel in Egypt.
Verification status, 11 October 2026: 76 statements are ledgered. 25 match the FRA website, Clyde & Co or Daily News Egypt automatically on every build. The other 51 come from Arabic gazette PDFs on fra.gov.eg that have no machine-readable text, so the StackWeaver compliance research team read them from an OCR of the official text and checked each quote line by line.
Executive summary
Sourced
- Two routes in. A new company needs an FRA licence; an existing FRA licensee needs FRA approval to deliver its licensed activity through FinTech, in-house or through a registered outsourcer (Law 5/2022, Art. 5). Operating without either is a crime (penalties).
- Consumer finance is paused for newcomers. Decree 43 of 2026 suspended new consumer finance FinTech licence applications for one renewable year (Decree 43/2026).
- Security is now a licence condition. Decree 227 of 2025 requires board-approved security frameworks filed with the FRA, annual cyber insurance and an annual penetration test, and makes compliance a condition of keeping the licence (Art. 3).
- Every customer is verified against the State. Decree 186 of 2024 requires checks on national ID data, phone ownership and AML and freeze lists at contract and renewal (Decree 186); lenders must also send a verification code (Art. 1).
- Vendors are regulated too. FinTech outsourcers must be on the FRA register (Decree 141), and since Decree 279 of 2025 so must risk-assessment and scoring providers (Decree 279).
Who is in scope
Sourced, with our reading marked
The law applies to anyone who carries on non-bank financial activities using financial technology (issuing law, Art. 1). "Non-bank financial activities" means the markets the FRA supervises: capital markets, insurance, mortgage finance, leasing, factoring, MSME finance and consumer finance (Art. 1). The law operates without prejudice to the Central Bank and Banking Sector Law (issuing law, Art. 1), which is why bank-led and payment products sit outside this guide.
The FRA's own explanation of the 2023 decrees names three groups: companies seeking a new licence to offer a non-bank service through technology; firms already licensed for a non-bank activity that want approval to use FinTech themselves or through an outsourcer; and companies that want to provide FinTech outsourcing services to the sector (FRA release). The decrees allow fully digital companies and let existing firms run a hybrid model (FRA release). A fourth group arrived in 2025: providers of technology systems for credit risk assessment, which now need their own registration (Decree 279/2025).
StackWeaver view · Put simply: a BNPL app, digital consumer lender, microfinance app, insurtech or robo-adviser is either a licensee or an approved firm, and the e-KYC, e-signature, contract-register and scoring vendors behind it are regulated suppliers. A vendor that sells to Egyptian non-bank lenders without the right registration is a liability for its clients, not only for itself.
The regulators and the rulebook
Sourced
The Financial Regulatory Authority. The FRA licenses and supervises FinTech activity, keeps the outsourcing register (Law 5/2022, Art. 6) and may run a regulatory sandbox for testing applications on real customers (Art. 9), which FRA Board Decree 163 of 2024 put in place (FRA portal). It must answer customer complaints within one month of receiving the required documents (Art. 12).
The decrees. Decree 58 of 2022 set the incorporation, licensing and approval conditions (FRA release). On 11 July 2023 the FRA issued Decrees 139, 140 and 141 (Clyde & Co): Decree 139 on infrastructure, information systems and security (FRA release), Decree 140 on digital identity, contracts and records (FRA release) and Decree 141 on the outsourcing register (FRA release). Decree 268 of 2023 added rules for FinTech start-ups (FRA portal). Later decrees cover customer data verification (Decree 186/2024), cybersecurity (Decree 227/2025), risk-assessment vendors (Decree 279/2025), directors' and officers' liability insurance (Decree 35/2026) and warning and negative lists (Decree 87/2026).
The Money Laundering Combating Unit. The law requires FRA rules for FinTech firms to include AML/CFT controls that follow the Unit's instructions (Art. 7). Customer data is also governed by the Personal Data Protection Law, which applies alongside the FinTech Law's confidentiality duty (Art. 13); our Egypt PDPL guide covers that regime.
Obligations and the evidence that demonstrates them
Sourced obligations · evidence column is StackWeaver view
The table pairs each FRA requirement with the document or record that proves it. An FRA inspector, a bank partner or an investor's diligence team will ask for the evidence column, so build it as you go.
| Obligation | Legal source | Applies to | Evidence | Deadline |
|---|---|---|---|---|
| Hold an FRA licence (new FinTech company) or an FRA approval (existing licensee adding FinTech) before offering non-bank financial services digitally. | Law 5/2022, Arts. 3–5 | Digital lenders, BNPL and consumer finance apps, insurtech, robo-advice, MSME finance platforms | Licence or approval letter; scope map of products to licensed activities | Before launch |
| Meet the FRA technology infrastructure, information systems and security requirements, including IT governance, service management and technology risk frameworks. | Decree 139/2023 | Licensees and approved firms | Architecture documents; ITG, ITSM, cyber and TRM framework documents | Condition of licence or approval |
| Board-approved information security manual, IT governance, IT risk and cybersecurity frameworks filed with the FRA; annual cyber insurance. | Decree 227/2025, Art. 1 | Non-bank financial firms designated by the FRA | Board minutes approving each framework; FRA submission receipts; insurance policy | Within the compliance period the decree sets |
| Annual penetration test and information security report, with results sent to the FRA. | Decree 227/2025, Art. 2 | Designated non-bank financial firms | Pen test report; remediation tracker; tester contract requiring disclosure to the FRA | Annually |
| Run digital identity, digital contracting and digital register processes to the FRA trust levels, with FRA-approved encryption. | Decree 140/2023 | Firms onboarding or contracting customers digitally | Trust-level matrix per product; encryption approval; contract journey logs | Before digital onboarding |
| Keep digital records archived for at least five years after the digital asset expires. | Decree 140/2023 | Digital platform operators | Retention schedule; archive restore test | Continuous |
| Semi-annual report on review results and error rates, approved by the board and sent to the FRA. | Decree 140/2023, compliance requirements | Providers using FinTech processes | Board-approved reports; sampling method; error log | Within four weeks of each half-year end |
| Verify national ID data and mobile number ownership, and screen AML and asset-freeze lists, when contracting or renewing. | Decree 186/2024 | Insurers, FinTech licensees and registered outsourcers | Verification results per customer from the FRA link; exception log | At contract and renewal |
| Send a verification code to the verified mobile number and keep proof of it. | Decree 186/2024 | Consumer finance and microfinance lenders | OTP logs linked to contract IDs | At contract, renewal and drawdown |
| Use only FRA-registered providers for FinTech outsourcing, under a written outsourcing agreement. | Law 5/2022, Arts. 5–6; Decree 141/2023 | Licensees using vendors; vendors offering e-KYC, contracts, registers | Vendor register check; outsourcing agreement; vendor insurance certificate | Before the service starts |
| Use only FRA-registered risk-assessment providers, notify the FRA before contracting, or get FRA approval for in-house scoring systems. | Decree 279/2025 | Non-bank lenders and credit-scoring vendors | FRA notification and contract copy; model approval; vendor register entry | Before contracting or use |
| Keep customer information confidential; disclose only with prior written or electronic consent. | Law 5/2022, Art. 13 | Firms, managers, advisers and staff | Consent records; disclosure log; staff confidentiality undertakings | Continuous |
| Apply AML/CFT controls set by the FRA in line with the Money Laundering Combating Unit. | Law 5/2022, Art. 7 | Licensees and approved firms | AML policy; screening records; suspicious activity escalation log | Continuous |
Digital identity, contracts and the digital register
Sourced from Decree 140, with our reading marked
Decree 140 builds the onboarding stack around three groups of factors, knowledge, possession, and presence and liveness (FRA release), combined into three trust levels (Decree 140). Even the basic level asks for at least two knowledge factors plus presence and possession factors (Decree 140), so a password and a photo of an ID card do not meet it.
Once a customer signs, the contract and every step before it must be stored in the digital register using encryption the FRA approves (Decree 140), and records must be archived for at least five years after the digital asset expires (Decree 140). The law backs this up by giving data held on these electronic media the evidential force of official documents (Law 5/2022, Art. 11).
The compliance section of the decree adds a recurring deliverable that teams often miss: a semi-annual report on "review results and error rates" (Decree 140), approved by the provider's board and sent to the FRA within four weeks of the period end (Decree 140).
StackWeaver view · The error-rate report is the closest thing Egypt has to a control-effectiveness test for onboarding. Treat it like an internal audit: define the sample, record every mismatch between the digital identity and the source data, and keep the working papers. If your e-KYC vendor cannot export what you need for it, that is a procurement problem to fix now.
Infrastructure and cybersecurity: Decrees 139 and 227
Sourced
Decree 139 sets the baseline: frameworks for IT governance, IT service management, cybersecurity management and technology risk management (Clyde & Co), plus a dedicated 24/7 customer service centre (Clyde & Co). A FinTech licence itself depends on having the required infrastructure, information systems and security means (Law 5/2022, Art. 4).
Decree 227 of 2025 raises the bar for firms the FRA designates. They must take the measures needed to strengthen cybersecurity and protect systems and sensitive data (Art. 1), prepare an information security manual approved by the board and send it to the FRA (Art. 1), and hold cyber risk insurance renewed every year (Art. 1). Article 2 adds an annual penetration test and annual information security reports for the FRA (Art. 2), and the contract with the tester must require the results to reach the FRA. Meeting the decree is a condition of keeping the licence (Art. 3).
Customer verification after the 2026 school-loan case
Sourced
Decree 186 of 2024 makes insurers, FinTech licensees and registered outsourcers verify customers' national ID data and mobile number ownership (Decree 186) and check money laundering and asset-freeze lists when they contract or renew (Decree 186). Consumer finance and microfinance lenders must also send a verification code to the verified number (Decree 186).
The rule stopped being theoretical in August 2026. Around EGP 321 million of consumer finance had been registered in the names of 819 parents without their knowledge or request (Ahram Online). The FRA began criminal proceedings, revoked a chief executive's licence and banned new contracts for a month at the lender involved (Daily News Egypt), finding breaches of its decisions on customer data inquiries, governance, credit controls and anti-money laundering (Daily News Egypt). It then warned every regulated entity to follow the identity and data-accuracy rules in Decree 186 (Daily News Egypt).
Outsourcers and risk-scoring vendors
Sourced, with our reading marked
Existing licensees may deliver services through a registered outsourcer under an agreement that sets out both parties' rights and obligations (Law 5/2022, Art. 5). Only registered providers may offer FinTech outsourcing services (Decree 141). The consolidated decree requires paid-up capital of at least EGP 10 million (Decree 141) and an undertaking to insure against technology and professional liability risks (Decree 141). Registration is mandatory (Clyde & Co) and the first registration lasts a year (Clyde & Co).
Decree 279 of 2025 applies the same logic to credit scoring. Lenders may use only registered risk-assessment providers (Decree 279), must notify the FRA and send it the contract before signing (Decree 279), and need FRA approval before using their own in-house scoring systems (Decree 279). Providers must disclose the methodology behind their algorithms (Decree 279), hold capital of at least EGP 10 million (Decree 279) and report to the FRA every quarter (Decree 279).
StackWeaver view · Decree 279 is the first Egyptian rule that asks a lender to explain its scoring model to the regulator before use. Model documentation, assumption logs and validation results are now licensing evidence, not just good practice.
Timeline of key dates
Sourced
-
Law 5/2022 published in the Official Gazette; it takes effect the next day · source
-
FRA issues Decrees 139, 140 and 141 on infrastructure, digital identity and contracts, and the outsourcing register · source
-
FRA announces criminal referral, licence revocation and a contract ban against a consumer finance company over unauthorised loans · source
The issuing law gave those covered six months from the executive decrees to regularise their position, with extensions possible (issuing law, Art. 4). Watch the renewal date of the consumer finance licensing pause, which runs for a renewable year from its effective date (Decree 43/2026).
Enforcement powers and penalties
Sourced, with our reading marked
The FRA Board's administrative toolkit ranges from a warning to a ban on operating or signing new contracts for up to six months (Law 5/2022, Art. 14) and, at the top, revoking the licence (Art. 14). The August 2026 case used the contract ban and licence revocation for an individual, under the Consumer Finance Law (Daily News Egypt).
The criminal penalties in the FinTech Law:
- Operating without a licence or approval: at least six months in prison and a fine of EGP 200,000 to EGP 1 million, or either (Law 5/2022, penalties).
- Breaching customer confidentiality: at least three months and a fine of EGP 200,000 to EGP 1 million, or either (penalties), with fines multiplied by the number of victims (penalties).
- Personal liability for the person who actually manages the company where the breach came from a failure of their duties (penalties), and a possible ban from the activity of up to five years (penalties).
- Prosecution needs a written request from the FRA Chairman (penalties), which keeps the regulator in control of when a case becomes criminal.
StackWeaver view · The confidentiality fine is the one to model. Because it multiplies per victim, a single leaked customer file is a manageable incident, but a leaked database is an existential one. Consent records and a disclosure log are the cheapest insurance against that exposure.
A practical 90-day plan
StackWeaver view
Days 1–15: confirm your regulatory position
Write down whether each product is licensed, approved or outside the law, and which register each vendor must be on. If consumer credit is on the roadmap, plan around the licensing pause rather than against it.
Days 16–45: close the governance gaps
Take the security manual and the IT governance, IT risk and cybersecurity frameworks to the board, file them, and buy or renew cyber cover. Book the penetration test with FRA reporting written into the contract.
Days 46–75: prove identity and consent
Reconcile a month of contracts against the verification checks and code logs. Trace every disclosure of customer data to a consent. Draft the semi-annual error-rate report from real samples.
Days 76–90: package the evidence
Index the evidence against the obligations table and have someone outside the team retrieve five items cold. Anything they cannot find in minutes will not survive an FRA visit.
Common mistakes
StackWeaver view
- Treating the PDPL as the whole data story. The FinTech Law's confidentiality rule and its per-victim fines apply on top.
- Buying e-KYC or scoring from an unregistered vendor. The registers make that the lender's breach, not only the vendor's.
- Relying on an ID image alone. Even the basic trust level combines several factor groups, and Decree 186 adds State data checks.
- Leaving board approvals for later. Decree 227 needs board-approved documents filed with the FRA, not drafts in a shared drive.
- Forgetting the semi-annual error-rate report. It has a four-week deadline and needs board sign-off.
Egypt FinTech evidence checklist
StackWeaver view, built on the sourced obligations above
| Area | Task | Owner | Evidence to keep |
|---|---|---|---|
| Scope | Map every product to an NBFI activity and confirm whether it needs an FRA licence or an approval. | Legal / compliance | Scoping memo |
| Scope | Record why no product falls under Central Bank of Egypt payment rules instead. | Legal | CBE boundary note |
| Licensing | Check the consumer finance licensing pause and its renewal date before planning a new entity. | Founders | Decree 43/2026 note in board pack |
| Infrastructure | Map controls to Decree 139 and the four frameworks it names. | CTO / CISO | Control map |
| Cyber | Have the board approve the security manual and the three frameworks, then file them with the FRA. | CISO / board secretary | Minutes and receipts |
| Cyber | Book the annual penetration test with a contract that requires results to go to the FRA. | CISO | Contract and report |
| Cyber | Renew cyber insurance with an Egyptian-licensed insurer. | Finance | Policy schedule |
| Digital identity | Document the trust level used for each product and the factors collected. | Product / risk | Trust-level matrix |
| Digital register | Test that archived contracts can be restored with their full pre-contract history. | Engineering | Restore test record |
| Reporting | Prepare the semi-annual review and error-rate report and calendar the four-week deadline. | Compliance | Board-approved report |
| Data verification | Reconcile contracts against national ID, phone ownership and list checks; for lenders, OTP logs too. | Operations | Reconciliation with exceptions |
| Vendors | Confirm each e-KYC, contract, register and scoring vendor is on the right FRA register. | Procurement | Register extracts |
| Confidentiality | Trace every customer-data disclosure to a written or electronic consent. | DPO / compliance | Consent-to-disclosure trace |
Control crosswalk: FRA requirements to SOC 2 and ISO 27001
Draft mapping, pending named reviewer sign-off. SWC numbers refer to StackWeaver's common controls; SOC 2 references are Trust Services Criteria and ISO references are ISO/IEC 27001:2022 Annex A controls. Use it to reuse evidence, not as a statement that one framework satisfies another.
| FRA requirement | StackWeaver control | SOC 2 | ISO 27001:2022 |
|---|---|---|---|
| Licence and approval scope (Law 5/2022, Arts. 3–5) | SWC-29 Regulatory registration and filings | CC2.3 | A.5.31 |
| Technology infrastructure and IT governance (Decree 139) | SWC-02 Named accountable roles; SWC-03 Board and management oversight; SWC-04 Risk assessment | CC1.2, CC5.2 | A.5.1, A.8.9 |
| Security manual and cyber frameworks (Decree 227) | SWC-01 Approved policy set; SWC-03 Board and management oversight; SWC-29 Regulatory registration and filings | CC5.3, CC7.1 | A.5.1, A.5.37 |
| Annual penetration test (Decree 227) | SWC-14 Vulnerability management; SWC-36 Independent testing of the compliance programme | CC4.1, CC7.1 | A.8.8, A.8.29 |
| Digital identity and authentication (Decree 140) | SWC-18 Encryption and key management; SWC-30 Customer due diligence and risk rating | CC6.1, CC6.2 | A.5.16, A.8.5 |
| Digital register, encryption and retention (Decree 140) | SWC-35 Record keeping | CC6.1, C1.2 | A.8.24, A.8.13 |
| Customer data verification and list screening (Decree 186) | SWC-30 Customer due diligence and risk rating; SWC-32 Sanctions and watchlist screening | CC3.2 | A.5.19 |
| Outsourcing and risk-assessment vendors (Decrees 141, 279) | SWC-07 Third-party and processor management; SWC-29 Regulatory registration and filings | CC9.2 | A.5.19, A.5.20 |
| Confidentiality and consent (Law 5/2022, Art. 13) | SWC-23 Lawful basis and consent | C1.1, P3.1 | A.5.34 |
| AML/CFT controls (Law 5/2022, Art. 7) | SWC-30 Customer due diligence and risk rating; SWC-32 Sanctions and watchlist screening; SWC-33 Transaction monitoring; SWC-34 Suspicious and threshold transaction reporting | CC7.2 | A.5.24 |
Decrees 139 and 227 line up closely with an ISO 27001 or SOC 2 programme, so evidence collected for one can serve the other. The registers, State data checks and error-rate reporting are Egypt-specific and need their own records. For the data protection side see our Egypt PDPL guide; teams also active elsewhere can compare Kenya and South Africa.
Frequently asked questions
Does the FinTech Law cover payment apps and banks?
Not directly. Law 5/2022 applies to non-bank financial activities supervised by the FRA, and it applies without prejudice to the Central Bank and Banking Sector Law. Banks and the payment services that law governs stay with the Central Bank of Egypt. Lending, insurance, leasing, factoring and investment products offered digitally answer to the FRA.
Does an existing consumer finance company need a new licence to go digital?
Not necessarily. An existing FRA licensee can apply for FRA approval to use FinTech for its licensed activity, either in-house or through a provider on the FRA outsourcing register under a written outsourcing agreement. A brand-new FinTech company needs its own licence. Both routes must meet the infrastructure and security requirements.
Can a new company get a consumer finance FinTech licence today?
Probably not yet. FRA Board Decree 43 of 2026 suspended new applications to incorporate or obtain a consumer finance licence under the FinTech Law for one renewable year, while applications already filed continue. Check the FRA legislation portal for any renewal or lifting before planning a new entity around consumer credit.
What is the FRA outsourcing register?
It is the list of providers allowed to deliver FinTech outsourcing services, such as e-KYC, digital contracting and digital registers, to non-bank financial firms. Only registered providers may offer those services. Registration requires minimum paid-up capital, governance, security capability and insurance against technology risk and professional liability.
Do credit-scoring and AI risk vendors need FRA registration?
Yes, if they serve non-bank lenders. Decree 279 of 2025 created a register of companies providing technology systems for risk assessment, and lenders may only use registered firms. Applicants disclose their algorithm methodology and assumptions, and lenders using in-house scoring need FRA approval of the system before use.
What does Decree 227 of 2025 require on cybersecurity?
Firms the FRA designates must have their board approve an information security manual and frameworks for IT governance, IT risk and cybersecurity, and file them with the FRA. They also need annual cyber insurance, an annual penetration test and an annual security report. Compliance is a condition for keeping the licence.
Which identity checks became mandatory for lenders?
Decree 186 of 2024 requires checks on national ID data, mobile number ownership and money laundering and asset-freeze lists when contracting or renewing. Consumer finance and microfinance lenders must also send a verification code to the verified number. The FRA pointed to these rules after the August 2026 enforcement case.
How does the FinTech Law relate to Egypt's data protection law?
They stack. Article 13 imposes strict customer confidentiality, disclosure only with prior written or electronic consent, without prejudice to the Personal Data Protection Law of 2020. So a FinTech lender must satisfy both FRA confidentiality and PDPL licensing, breach notice and transfer duties. Our Egypt PDPL guide covers the second set.
What are the penalties under the FinTech Law?
Operating without a licence or approval carries at least six months in prison and a fine of EGP 200,000 to EGP 1 million, or either. Breaching confidentiality carries at least three months and the same fine range, multiplied by the number of victims. Courts may also ban offenders from the activity for up to five years.
Is there a regulatory sandbox for start-ups?
Yes. The law lets the FRA run a regulatory sandbox where FinTech applications are tested on real customers under supervision, and FRA Board Decree 163 of 2024 set it up. Start-ups can also receive a temporary licence for up to two years, under rules the FRA Board set for FinTech start-ups.
How StackWeaver helps
FRA readiness is mostly a document problem: board approvals, framework filings, test reports, verification logs and vendor registrations, each with a date and an owner. StackWeaver keeps those records in one workspace, fingerprints every file, records every review, and exports an Evidence Package your counsel, auditor or bank partner can check offline. We are remote-first; we work with local counsel and advisory partners, and the Evidence Readiness Assessment shows where your FRA evidence stands today.
Next steps
- 1. Download the Egypt FinTech evidence checklist (Excel, free)
- 2. Book a 20-minute call
- 3. Partner with us
Advisory, audit or legal firm in Egypt? Partner with us
Firms that help Egyptian lenders, insurtechs and FinTech vendors through FRA licensing can run client evidence in StackWeaver workspaces and keep their own advisory work. Tell us about your practice.
Partner with usSources and method
We cite the official Arabic texts the FRA publishes on fra.gov.eg: Law No. 5 of 2022 as printed in the Official Gazette, and the FRA Board decrees in their consolidated or gazetted form. Those PDFs are scans or use legacy font encodings, so their quotes are recorded from an Arabic OCR and checked line by line; our build checks that each source is still online. The FRA's July 2023 release and its legislation portal, Clyde & Co's July 2023 briefing and Daily News Egypt's August 2026 report are matched automatically. Ahram Online blocks automated checks, so that one figure is checked by hand. Where a secondary summary disagreed with the official text, we followed the official text.
Every statement of law is recorded in a public claims ledger with its source, section, retrieval date and the exact supporting words. Facts are labelled “Sourced”; opinions and recommendations are labelled “StackWeaver view”, as our editorial policy explains. AI tools helped research, OCR and draft this guide; the StackWeaver compliance research team is accountable for it.
Spotted an error? Email [email protected]. More countries are in the Africa Fintech Regulatory Atlas.