Risk and compliance
A sanctions screen that runs inside the posting, before money moves, so a blocked payment is refused rather than recalled — and every alert becomes a case with a decision and a name against it.
Compliance officers, risk teams, partners performing due diligence and regulators.
Part of the platform itself: it is present wherever BitriPay runs.
The problem
Many platforms screen asynchronously: the payment goes, a job runs, and a hit becomes a recall request and a difficult letter. By then the money has usually moved again.
How it works
- A pre-commit hook screens both parties inside the posting, before any entry is written.
- A hit refuses the transaction and opens a case rather than letting it settle.
- Monitoring rules watch velocity, structuring below limits, bursts to new recipients and high-risk corridors.
- Every alert becomes a case with a decision, a reviewer and a record of why.
What you can check
Facts about the running platform rather than adjectives. Each one is visible in the product, the API reference or the ledger.
- Screening is a pre-commit hook on the ledger posting: the check happens before entries are written, not after they settle.
- Official consolidated sanctions sources are registered on first start and refreshed daily.
- Monitoring produces cases, not just flags; a case carries the decision, the reviewer and the reasoning.
- A beneficiary added for the first time can require a step-up and a cooling-off before a large amount moves to it.
- Settlement destination changes are a protected action, separate from ordinary profile edits.
What it costs
Not charged separately. It is a condition of operating, not an upsell.
Questions
Why was my payment refused?
A refusal with a compliance code means the transaction did not pass a check. Support cannot always explain which one — that is a legal constraint, not evasiveness — but a case exists and is reviewed by a person.
Does screening slow every payment down?
The check runs inside the posting, so it costs the time of a lookup rather than the time of a batch job. Customers do not experience it as a delay; they experience it only when something is refused.
What stops a legitimate customer being blocked forever?
Every alert becomes a case with a reviewer and a decision, not a permanent silent flag. Cases are worked by people, and the decision is recorded with its reasoning so it can be revisited rather than guessed at.
Read next
Identity and tiers
Tiers that let somebody start with a phone number and grow into higher limits, so verification is a ladder rather than a wall at the front door.
The ledger
A double-entry ledger where balances are derived from postings rather than stored, corrections are opposing entries rather than edits, and invariants are enforced at write time instead of checked by a nightly job.
E-money and safeguarding
An issuance rule the platform refuses on rather than reports on: e-money cannot be issued beyond cleared safeguarded funds, checked at the moment of issuance rather than at the end of the month.