Compliance that runs inside the payment
Sanctions screening, KYC, and risk scoring execute before a single dollar moves, so every payment is checked before it clears.
Transactions
Compliance anchors the Verify phase of the Coinbax Execution Framework, and re-checks can run at Confirm before release. Every check and score is recorded in the payment’s audit trail.
Checked before a single dollar moves
Screening before settlement
Wallet and counterparty screening runs through integrations like Chainalysis at the moment of payment, not in a nightly batch. A payment that fails screening never enters escrow.
Risk scoring on every transaction
Each payment is scored across amount, counterparty history, behavior, geography, and velocity. Low risk proceeds, elevated risk routes to review, high risk is rejected automatically.
Fail-safe by default
If a screening provider is unreachable, the payment is treated as high risk and held. The system fails closed, never open.
Screening enforced in the payment, not after
Provable screening on every payment
Show exactly which checks ran on which payment, with results recorded on a tamper-evident trail.
Your risk appetite, encoded
Thresholds, routing, and escalation follow the policy your institution sets, not a vendor default.
Examiner-ready evidence
Screening evidence is complete by default, not assembled under deadline when the exam letter arrives.
Questions
Coinbax integrates established compliance providers like Chainalysis for sanctions and wallet screening, running them inside the payment flow rather than as a separate step. You keep the vendors your program already relies on.
At the moment of payment, pre-escrow, in the Verify phase of the Coinbax Execution Framework. Screening runs before funds ever lock, not in a nightly batch, and a payment that fails never enters escrow.
Each payment is scored across amount, counterparty history, behavior, geography, and velocity. Low risk proceeds automatically, elevated risk routes to review, and high risk is rejected before funds move.
The system fails closed. If a provider cannot be reached, the payment is treated as high risk and held rather than allowed through, so an outage never becomes a compliance gap.
Screening and risk scoring are enforced in the payment path, and every check and score is recorded, so your BSA/AML obligations are met on the transaction itself rather than reconstructed afterward.
Yes. Every check that ran and its result is captured on a tamper-evident trail, backed by SOC 2 attestation and independently audited smart contracts, so you can show examiners exactly what was screened and when.