Payrails
A Berlin payment orchestration platform with workflow-based routing, a PCI DSS Level 1 vault and 100+ integrations.
Payrails sells payment orchestration to enterprise merchants and platforms, connecting them to 100+ PSPs, acquirers, fraud tools, local payment methods and ERPs through one integration. Routing is built as workflows: conditions on card BIN, issuing country, card scheme, fraud score or metadata send each payment to a provider, and a configured cascade retries declines on the next PSP, reusing the 3-D Secure cryptogram. Its Token Vault is PCI DSS Level 1 and works standalone. Payrails does not publish pricing.
- Website
- payrails.com
- Infrastructure layers
- Payment orchestration, tokenization
- Products (as published)
- Payment orchestration (workflow routing, PSP cascade, A/B tests)
Token Vault (PCI DSS Level 1, standalone or with orchestration; proxy to third parties)
Network tokenization and card lifecycle updates
Reconciliation and Fee Monitoring
Chargebacks
Payouts, Payment Links, Unified Analytics, in-person payments - Client types
- Enterprise merchants and platforms (named: Puma, Vinted, Flix, inDrive, Just Eat Takeaway, Careem)
- Regions served
- Europe, Middle East and Africa; teams in Berlin, London, Paris, Dublin, Cairo and Dubai
- API documentation
- docs.payrails.com
- Date checked
- Profile type
- Standard
Questions
Can the Payrails vault be used without its orchestration?
Does Payrails repeat 3-D Secure when it retries another PSP?
Where does Payrails operate?
See also
Sources
- Payrails: Series A (June 12, 2025)
- Payrails: platform
- Payrails: orchestration
- Payrails docs: provider routing with conditions
- Payrails docs: server-to-server reference architecture
- Payrails docs: Token Vault
- Payrails docs: getting started
- Payrails: Middle East headquarters in the DIFC (February 24, 2026)
- Payrails: Playtomic goes live with dLocal (July 14, 2026)
- Checked September 27, 2026.
Source: each provider’s own documentation, product pages, official announcements and filings, and official registers for licences, as linked in each profile. Fields a provider does not publish stay empty. How we build profiles: methodology.