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. Users and API keys can only access resources permitted by their account roles and scopes.

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.

Metadata isolation

Metadata is scoped to the resource and account. Do not use metadata to store secrets, passwords, private keys, or raw payment credentials.

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.