Attach approvals, limits, delays, and screening to any payment and compose them into the precise workflow your policies require.
Checks before funds are locked in escrow
OFAC, SDN, and global sanctions list checking
Validates transaction amount against configurable limits
Monitoring after escrow, before release
Mandatory fail-safe. Refunds the transaction if a control fails or the deadline elapses.
Final checks before funds are released
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.
Each control is a rule that runs during the payment lifecycle: before funds are escrowed, while they are held, or before they are released.
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.
Define a control set once and apply it as a template across every payment type your institution runs.
Encode approval policy, limits, and delays as configuration. No smart-contract engineering required.
Multi-party approval and role separation are enforced by the payment itself, satisfying internal controls.
Every control that ran, and its result, is recorded, so approvals are provable after the fact.
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.