Set the controls, and every payment obeys
Attach approvals, limits, delays, and screening to any payment and compose them into the precise workflow your policies require.
Pre-Escrow Stage
Checks before funds are locked in escrow
Chainalysis Sanctions Screening
OFAC, SDN, and global sanctions list checking
Amount Limit
Validates transaction amount against configurable limits
Post-Escrow Stage
Monitoring after escrow, before release
Reaper (Auto-Refund Fail-Safe)
Mandatory fail-safe. Refunds the transaction if a control fails or the deadline elapses.
Pre-Release Stage
Final checks before funds are released
Time Delay
Configurable time delay before funds auto-release from escrow
Controls execute across all four phases of the Coinbax Execution Framework. Screening controls run at Verify, holds and monitoring at Fund, approvals and review windows at Confirm, and settlement actions at Settle. Every control that runs is recorded with its result.
Compose the workflow a payment must clear
Controls attach to the payment
Each control is a rule that runs during the payment lifecycle: before funds are escrowed, while they are held, or before they are released.
Compose them into a workflow
Stack controls in the order your process requires: a time delay, then a second approver, then a sanctions check. The payment only proceeds when every control passes.
Reusable across products
Define a control set once and apply it as a template across every payment type your institution runs.
Policy enforced by the payment, not by paperwork
Policy without code
Encode approval policy, limits, and delays as configuration. No smart-contract engineering required.
Segregation of duties
Multi-party approval and role separation are enforced by the payment itself, satisfying internal controls.
Built for review
Every control that ran, and its result, is recorded, so approvals are provable after the fact.
Questions
Time delays, 2FA, SMS confirmation, multi-party approval, spend limits, and compliance checks like sanctions screening and KYC. Each is a reusable Coinbax Control you attach and configure, no contract code required.
No. Controls are composed as configuration in the Template Builder, so your payments and compliance teams can encode approval policy, limits, and delays without smart-contract engineering.
Yes. You sequence controls across the four phases of the Coinbax Execution Framework: screening at Verify, holds at Fund, approvals and review windows at Confirm, and settlement actions at Settle. A payment only advances when each control passes.
You define who must approve and in what order, and the payment itself enforces it. Role separation is applied by the contract, not by process, satisfying internal controls without manual policing.
Every control that executed, and its result, is recorded on a tamper-evident trail, backed by SOC 2 attestation and independently audited smart contracts. Approvals are provable after the fact.
Across all four phases of the Coinbax Execution Framework. Screening controls run pre-escrow at Verify, monitoring at Fund, approvals and rollback triggers at Confirm, and settlement actions at Settle.