Operations
The public money-movement model is centered on OperationView. Multiple
families use different request bodies, but they converge on one lifecycle
shape, one status model, and family-specific read surfaces for operators and
integrations.
Conceptually, this is the page that turns many endpoints into one execution story.
Mental Model
An operation starts as a family-specific request, then becomes a canonical readable object with lifecycle, fee, attribution, and approval context.
That lets an integrator do two useful things:
- submit different financial families through the correct request surface
- consume one normalized runtime model after submission
Family Types
The current public families include:
depositwithdrawalconversionexternal_settlement_conversioninternal_transferon_rampoff_ramp
Lifecycle Status
OperationStatus tracks the lifecycle from request to outcome, including:
requestedadmissiblepending_approvalpending_admissionpending_complianceexecutingexecutedpartially_settledsettledledger_visiblefailedcancelled
Nested Structure
OperationView is not just an amount and a status. It usually combines:
account_refprincipal_amountfee_summaryapproval_refsubject_attributionfailure_reasonfamily_params
Read that as a layered object:
- execution boundary
- monetary intent
- governance context
- attribution
- family-specific details
Operation View
The canonical operation read model includes:
account_refprincipal_amountfee_summaryapproval_reffailure_reasonsubject_attributionfamily_params
This lets integrators render one lifecycle model across multiple financial families.
How This Appears In The API
Request Body
{
"account_ref": "client-accounts/b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"amount": {
"currency": "EUR",
"value": "100.00"
},
"rail": "fiat",
"withdrawal_destination_id": "b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b"
}Withdrawal read response
{
"account_ref": "client-accounts/b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"approval_ref": null,
"created_at": "2026-05-01T10:00:00Z",
"destination_id": "b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"dispatch_attempt_id": null,
"failure_reason": null,
"family": "withdrawal",
"family_flow_id": "b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"fee_summary": {
"components": [
{
"amount": {
"currency": "USDC",
"value": "1.00"
},
"kind": "network_fee"
}
],
"total": {
"currency": "USDC",
"value": "1.00"
}
},
"fee_transaction_ids": [],
"fill_rate": null,
"hold_id": "b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"id": "b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"leg_attempt_id": "b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"network": "ethereum",
"principal_amount": {
"currency": "USDC",
"value": "250.00"
},
"principal_transaction_id": null,
"rail": "ethereum",
"rail_class": "crypto",
"release_transaction_id": null,
"settled_at": null,
"settlement_evidence": null,
"status": "executing",
"subject_attribution": {
"actor": null,
"approved_by": null,
"authenticated_principal": {
"id": "b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"kind": "user",
"tenant_ref": "enterprises/b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b"
},
"enterprise_binding": {
"tenant_type": "enterprise",
"topology_ref": "enterprises/b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b"
},
"federation": null,
"identity_source": "platform-managed",
"initiated_by": null,
"subject": {
"id": "b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b",
"kind": "user",
"tenant_ref": "enterprises/b8e2f1a0-4c3d-4e5f-9a1b-2c3d4e5f6a7b"
}
},
"updated_at": "2026-05-01T10:00:00Z",
"withdrawal_attempt_id": null
}