Integrations
Connect the source. Keep the authority separate.
Every integration declares whether it reads evidence, prepares an accounting handoff or performs a regulated action through a separately authorised partner.
Fixture and contract qualification
Launch source connections
| Integration | Permission model | Current evidence |
|---|---|---|
| VALR | Read-only | Contract + deterministic fixtures |
| Luno | Read-only | Contract + deterministic fixtures |
| Binance | Read-only | Contract + deterministic fixtures |
| Generic CSV | Customer-provided file | Implemented ingestion + coverage |
| BTC addresses | Public observation | Contract + fixtures |
| EVM addresses | Public observation | Contract + fixtures |
Accounting and operations
| Integration | Purpose | Current evidence |
|---|---|---|
| Xero | Draft journals | OAuth adapter implemented; app acceptance pending |
| Sage | Release-bound journal bundle | Implemented; target import pending |
| QuickBooks | Release-bound journal bundle | Implemented; target import pending |
| CASP rail | Quote/order/settlement | Standard mock adapter; partner pending |
| KYT / Travel Rule | Specialist compliance | Interfaces; contracts pending |
Admission rule
A logo is not an integration claim. A provider moves from planned to available only after authentication, pagination or callbacks, rate limits, idempotency/recovery, representative fixtures, failure paths and downstream reconciliation are accepted.