Platform scope
01Which API family the application may call.
Trust & security
Access is earned at the transaction—not assumed at the platform.
A partner connection establishes identity and capability. It does not provide blanket visibility across TradeVow, its participants or their evidence.
Access decision
1Valid partner application
2Permitted API scope
3Transaction relationship
4Active purpose-bound grant
5Field and jurisdiction policy
Explicit allow — otherwise deny
Layered authorisation
One token is not the whole permission decision.
Every protected action combines application status, platform scope, transaction relationship, sharing purpose, active grant and field-level policy.
Partner status
02Whether this application and environment remain active.
Transaction role
03Why the organisation is involved in this transaction.
Data-sharing grant
04What may be read or changed, for which purpose and until when.
Contextual policy
05Sensitivity, corridor, jurisdiction and lifecycle restrictions.
Coordination without consolidation
Share the proof required for the purpose—not the entire underlying record.
Data minimisation
Partner-safe projections and field allow-lists keep unrelated commercial and personal information out of responses.
Evidence provenance
Issuer, subject, source, hash, validity and verification method travel with important evidence.
Immutable history
Corrections supersede earlier facts and events rather than rewriting the audit trail.
Signed events, controlled delivery
- HTTPS endpoints with source verification
- Unique delivery ID and timestamp
- Raw-body signing and replay protection
- Bounded retries, attempt history and dead-letter state
- Permission recheck before sensitive delivery
- Key rotation without losing the event chain
High-value integrations
Stronger controls where the consequence is higher.
Finance and settlement interactions can add sender-constrained tokens, mTLS, message signatures, step-up approval and stronger operational certification. The security profile grows with risk—not with marketing labels.
Standards direction
OAuth security best practice · FAPI-aligned controls · RFC 9457 errors · CloudEvents envelopes · HTTP message signatures where required
Operational trust
Security must remain visible after go-live.
Credential suspension and emergency revocation
Connector pause, reconciliation and recovery
Webhook inspection and authorised replay
Cross-tenant access monitoring
Evidence access and policy decision audit