Legal
The terms under which organizations use the platform.
Scope
What is provided, and the environments it is provided in.
What the platform may and may not be used for.
Who is responsible for value issued to customers.
Service levels and how incidents are communicated.
Who owns the data in an organization, and portability.
What happens to wallets, balances and data on exit.
Meanwhile
Terms of service put numbers and remedies around behaviour. The behaviour itself is decided earlier, in the architecture — and several of the commitments organizations care most about are already specified and, where a database can enforce them, enforced. They are stated here as engineering facts so a team evaluating the platform can weigh them before any contract exists.
By design
/v1 is never modified in place — a breaking change requires a new version. A deprecated endpoint announces itself in Deprecation and Sunset response headers, and migration documentation is published before removal, never after.
Every credential is scoped to one environment. A sandbox key pointed at production fails with a specific error rather than silently switching — tested as one of the isolation scenarios.
Customers, activity and analytics leave through export jobs that any authorized administrator can start. Portability is a designed capability, not a support ticket.
The audit trail is append-only, enforced by a database trigger rather than by convention — and posted ledger transactions are immutable, with corrections made by reversal so the history stays whole.
Every financial operation on the surface declares idempotency. A network timeout retried with the same key returns the original result instead of moving value twice.
Commercial and legal questions get a direct answer while the formal terms are being prepared.