Solutions
Payment Hub
A unified processing core that connects your applications to multiple banks, PSPs, card processors and local payment methods through a single integration — with routing, settlement tracking and reconciliation built in.
Business problems addressed
- Fragmented, one-off provider integrations
- No central routing, failover or consolidated reporting
- Inconsistent payment statuses across providers
- Slow onboarding of new providers or markets
Who it is for
- EMIs and payment institutions
- Multi-provider payment platforms
- Marketplaces and cross-border platforms
- Technology companies embedding payments
Where it is used
EMI payment infrastructureMulti-provider payment platformMerchant payment routingLocal payment method aggregationCross-border payment platformsMarketplace payment infrastructureProvider migrationRedundancy and failover
Core capabilities
Unified Payment API
Provider Connector Layer
Provider Management
Rules-Based Routing
Smart Routing
Provider Failover
Retry Logic
Payment Status Normalisation
Authorization
Capture
Refund
Reversal
Void
Settlement Tracking
Fee Calculation
Multi-Currency Transactions
Reconciliation
Webhooks
Idempotency
Reporting
Provider Health Monitoring
Audit Logs
System architecture
Client ApplicationsAPI GatewayCardElse Payment HubRouting and Rules EngineProvider Connector LayerBanks / PSPs / Card Processors / Local Payment Methods
Example flow
- 1Client application calls the Unified Payment API
- 2API Gateway authenticates and forwards the request
- 3Routing and Rules Engine selects the appropriate provider
- 4Provider Connector Layer submits the transaction
- 5Status is normalised, returned, and a signed webhook is emitted
- 6Settlement tracking and reconciliation records are updated
Provider and integration categories
BanksPSPsCard processorsLocal payment methodsOpen bankingDigital wallets
Operational controls
- Rules-based routing configuration
- Provider priorities, weights and limits
- Retry and failover policies
- Fee configuration and reporting
Security considerations
- Scoped API access and keys
- Idempotency keys on write operations
- Signed webhooks
- Audit logs and data segregation
Implementation options
- Full platform build
- Payment Hub as a module in your existing stack
- Provider migration or redundancy engagement
Related CARDELSE products
How we deliver this
Frequently asked questions
Discuss this solution
Tell us what you are building. Our engineering team will help you scope the right architecture and delivery model.