Architecture Center
Remittance Platform Architecture
A layered, service-oriented design for cross-border money transfer — from front-end interfaces through core services to data stores and external integrations.
Quick Answer
A remittance platform architecture is a layered, service-oriented system. Customer-facing front ends communicate through an API gateway to core services — transaction, quote, FX, fee, ledger, compliance, payment and payout orchestration. Services persist to a relational database and event stream, and call external providers through adapter interfaces for KYC, sanctions, banking, FX, payouts and notifications.
Key Takeaways
- Layered separation keeps front ends, business logic and integrations independently evolvable.
- An event stream enables async processing of compliance checks and payout instructions.
- Adapter interfaces decouple core services from specific external providers.
- An immutable audit log supports regulatory reporting and dispute resolution.
Front-end layer
Customer-facing interfaces that call the API gateway.
API Gateway
Single entry point handling authentication, rate limiting, routing, idempotency and request validation.
Identity & Authentication
User registration, login, MFA, session management and role-based access control.
Core services
The business logic of the remittance platform, deployed as cooperating services.
Data layer
Durable storage, event streaming and immutable audit logs.
External integrations
Third-party providers accessed through adapter interfaces.
Key architectural principles
Service isolation
Each core service owns its data and exposes a contract. Services can be scaled and deployed independently.
Idempotency
Every state-changing API accepts an idempotency key so retries do not create duplicate transactions.
Event-driven processing
Compliance checks, payout instructions and notifications flow through an event stream for reliability and observability.
Adapter pattern
External providers sit behind adapter interfaces, so swapping a payout or KYC provider does not change core logic.
Immutable ledger
The ledger is append-only; corrections are new entries, preserving a complete audit trail.
Configurable rules
Fees, FX margins, limits and compliance rules are configuration, not code, where possible.
Explore the architecture
Related Resources
Review the architecture for your deployment
Request a demo to walk through the system design, deployment topology and integration points.