Platform overview
The CashXChain platform is organized around business resources that map to real payment operations.
Core resources
| Resource | Purpose |
|---|---|
| Account | A verified business, platform, entity, or sub-entity. |
| User | A person with access to an account. |
| API key | A credential used by a server-side integration. |
| Wallet | A logical balance container. |
| Beneficiary | A person or business receiving funds. |
| FX quote | A priced conversion and route proposal. |
| Payment | An instruction to move value. |
| Statement | A reconciliation export for a period. |
| Webhook endpoint | A URL that receives event notifications. |
| Event | A signed notification about a resource change. |
Typical implementation path
- Create or access a business account.
- Complete KYB and risk review.
- Generate sandbox API keys.
- Create a beneficiary.
- Request an FX quote.
- Create a payment using the quote.
- Receive webhook events.
- Reconcile with statements and ledger records.
- Move to production after review.
Hosted and API-only flows
CashXChain supports two integration models:
- API-only: your platform owns the user experience and calls CashXChain APIs from your backend.
- Hosted: CashXChain provides secure hosted steps for onboarding, payment confirmation, or additional verification where required.
The exact model depends on your product, jurisdiction, partner requirements, and risk review.
Account hierarchy
A platform customer may operate one master account and create connected accounts for sellers, merchants, suppliers, or internal entities. Enterprise customers may use multiple accounts for subsidiaries, treasury entities, or operational separation.
Event-driven operations
CashXChain is designed for event-driven automation. Webhooks notify your system when payments change state, account verification is updated, a balance changes, a quote expires, or an action is required.
Production readiness
Before production, CashXChain reviews your use case, expected corridors, transaction volumes, compliance model, webhook handling, error handling, and security posture.