One integration.Every payment provider.
Phoenix Pay is payment infrastructure that abstracts away PSP complexity. Crypto and fiat, deposits and payouts, local and global providers, all through a single API.
Integrated payment providers
Live| Coming soon
Ship in minutes, not weeks
Create a deposit in a single API call. We handle PSP routing, status tracking, and webhook delivery.
1curl -X POST https:"text-zinc-600">//pay.phoenixverse.io/api/deposits \2 -H "X-Key-Id: pk_live_abc123" \3 -H "X-Signature: ${SIGNATURE}" \4 -H "X-Timestamp: ${TIMESTAMP}" \5 -H "Content-Type: application/json" \6 -d '{7 "reference_id": "order_7291",8 "amount": 10000,9 "currency": "ETB",10 "channel": "checkout"11 }'Three steps to production
From zero to processing payments in minutes.
Integrate once
Drop in our REST API. One endpoint for deposits, one for payouts. That's it.
Configure your PSPs
Add your PSP credentials from the dashboard. Set priority, currency routing, and failover rules.
Accept payments
Crypto, bank transfers, mobile money, all flowing through a single integration. We handle routing, status tracking, and signed webhook delivery.
Payment infrastructure, not a wrapper
Everything you need to route, track, and reconcile payments at scale.
Multi-PSP Routing
Integrate once. We route to the right PSP by currency and priority, with automatic failover if one goes down.
Signed Webhooks
Cryptographic signatures on every callback. Automatic retries with exponential backoff. You always know a webhook came from us.
Crypto + Fiat
USDT, BTC, ETH on one rail. ETB, bank transfers, mobile money on another. Same API, same webhooks, same dashboard.
Fully Isolated
Your PSP credentials, API keys, and webhook endpoints are completely yours. Nothing shared, nothing leaked.
Resilient by Default
Background sync polls pending payments every 5 minutes. Missed a webhook? We catch it. Automatic retries with exponential backoff.
Built for Scale
Partitioned tables, read replicas, ETS caching, connection pooling. Designed from day one for 100M transactions/day.
A growing network of payment providers
Connect once to Phoenix Pay. We keep adding providers. You don't change a line of code.
Security is not optional
Every request signed. Every webhook verified. Every credential encrypted at rest.
Ed25519 Signatures
Asymmetric key pairs for request authentication and webhook delivery. Cryptographic non-repudiation, not just shared secrets.
Per-Key Permissions
Scope API keys to specific operations. Read-only keys for dashboards, write keys for transactions, full access for automation.
IP Allowlisting
Optional CIDR-based IP restrictions per API key. Lock production keys to your known infrastructure.
Credential Isolation
Your PSP credentials are encrypted at rest. No shared key material between accounts.
Why Ed25519 over HMAC?
HMAC uses shared secrets. Both parties can forge signatures. Ed25519 is asymmetric: we sign with a private key, you verify with the public key. Cryptographic proof of origin that holds up to third-party audit. This matters when money moves.
Your Account
Everything you need, nothing you don't
Your own dashboard, your own PSP credentials, your own webhook endpoints. Manage API keys, test in sandbox, and go live when you're ready.
- Your own PSP credentials and configuration
- Scoped API keys with granular permissions
- Machine-to-machine auth for your backend
- Sandbox and live environments per API key
Start processing payments today
Get your API keys, test in sandbox mode, and go live when you're ready. No contracts, no minimums.