Mangopay vs Lemonway
Verified facts in one table - licence, EEA data residency, rails, cards and published pricing. Shared ground: BaaS, IBAN sponsor, Payment gateway. No verdict - which one fits depends on your build, and that is what the match request is for.
The facts, side by side
Every row comes from the source-verified catalogue - blank means not documented at source, not absent. Full context on each profile.
| Mangopay | Lemonway | |
|---|---|---|
| Origin | EU core (Luxembourg) | EU core (France) |
| EEA data residency | Yes | Yes |
| Licence type | EMI | EMI |
| Status | Active | Active |
| Verified | Verified 2026-07-19 | Verified 2026-07-19 |
| Product categories | BaaS, IBAN sponsor, Card issuing software, Payment gateway | Payment gateway, IBAN sponsor, BaaS |
| Local IBAN country codes | LU | FR |
| Payment rails (documented) | SCT; SCT Inst; SDD Core; FPS | SCT; SDD Core; SDD B2B |
| Account model | Virtual; Named virtual | Virtual |
| Account currencies | EUR; GBP; USD | EUR |
| Published entry price | not published (sales-led) | not published (sales-led) |
How to read the sovereignty rows: EEA data residency explains Yes / Partial / No, the sovereignty framework covers origin and ownership, and the card-scheme map explains why the scheme row looks the way it does. Pricing context: what is published vs negotiated.
FAQ
What licences do Mangopay and Lemonway hold?
Mangopay operates as an e-money institution (EMI) headquartered in Luxembourg; Lemonway as an e-money institution (EMI) headquartered in France. Both are verified at source, and their official register entries are linked from their profiles.
Do Mangopay and Lemonway keep data in the EEA?
Mangopay runs fully on EEA data rails (EEA: Yes). Lemonway runs fully on EEA data rails (EEA: Yes). What Yes / Partial / No mean - and why an EEA data centre alone is not the whole answer - is explained in the EEA data residency guide.