Platform API
Connect the bank’s systems to custody workflows. Define the relevant instructions, permissions and system boundaries during integration design.
FOR YOUR ENGINEERING TEAM
Connect your systems to the custody workflow.
Plan the integration around transaction instructions, policy decisions, approvals and evidence.
An API and event model around custody decisions.
The implementation includes 175 API endpoints and 64 event types across the platform. These figures describe its interface surface, not throughput or the number of endpoints a particular integration needs.
Event model
Use the platform’s event model to connect workflow state with the bank’s systems. The integration documentation defines the event scope for the deployment.
Approval boundary
API access does not replace transaction policy, maker-checker approval or joint device/platform signing.
How it works
Prepare an instruction
The bank’s system supplies a custody instruction through the agreed integration.
Apply policy and approvals
The platform checks the instruction against policy and the required maker-checker roles.
Approve and sign
The device displays the transaction for biometric approval; the two MPC participants sign together.
Connect state and evidence
The event model connects workflow state to bank systems; the WORM log preserves the decision evidence.
Give your engineers a controlled evaluation environment.
Request integration documentation and sandbox access for the bank’s engineers under NDA. Agree the relevant workflows and acceptance criteria during the discovery and design stages.