Data isolation

CashXChain separates customer data, environments, credentials, and operational records to protect confidentiality and reduce cross-account risk.

Account boundaries

Resources belong to an account. Each request is limited to the account its credential belongs to — or, for a master key sending Cxc-Account, to a managed account it holds a live grant for. On the money and developer routes, another account's resource answers 404, as if it did not exist.

Platform accounts

Platforms with connected accounts must enforce tenant boundaries in their own systems. CashXChain resource IDs should be mapped carefully to the correct tenant, seller, customer, or entity.

Environment boundaries

Sandbox and production are separate environments. Sandbox data must not be treated as real financial data. Production credentials must never be used in sandbox tools.

Free-text fields

No money-API resource carries free-form metadata. Do not put secrets, passwords, private keys, or raw payment credentials in free-text fields such as a payout reference.

Partner data

Some data must be shared with regulated partners for onboarding, screening, payment execution, settlement, and legal compliance. CashXChain shares only what is required for the relevant workflow.

Data minimization

Customers should send only necessary data and use structured fields rather than free-form notes where possible.