The controls your providers expect. Live before they ask.
Your providers hold you responsible for monitoring users, answering their questions fast and proving your controls work. Most teams learn that only after the first fraud alert. Rehive is building the rules, alerts and workflows that you can map to your provider agreements and internal policies.
In active development. We're building compliance as an end-to-end layer alongside our design partners. Some capabilities are live today; others are on the roadmap. If it matters to your program, let's shape it together.
- 14:02Provider recall received. Customer paused automatically.
- 14:02Case opened and assigned to risk review.
- 14:06RFI: source of funds. Documents requested in-app.
- 15:11Documents received and reviewed.
- 16:40Response sent to provider, inside the window.
- +1dFunds returned. Evidence logged to the record.
The bar stablecoin infrastructure providers hold fintechs to.
< 0.5%
the fraud ratio where providers start restricting programs
90 days
from a formal warning to being offboarded
2 days
to answer a provider's request for information
30+
controls providers expect you to run, and don't build for you
The controls in place before you need them.
When a fraud alert lands
A provider pauses a customer and expects an investigation, a response and possibly a fund return. Launch with the workflow already in place, and the controls that stop the next one.
When an audit or review comes
Spot checks and information requests come with short deadlines. Evidence, audit trails and answers, ready to export when asked.
When the application asks about your AML policies
Answering "no" works until volume grows. Go live with reviewed policies and the controls that back them up, before it becomes the blocker.
From the very first day
Start with the controls in place instead of retrofitting them after your first incident.
Not a checklist. Built to run as an operation.
01 · Policies
Request templatesPolicies you can stand behind
A reviewed policy library for stablecoin programs, provided through a specialist third-party compliance provider. Adopt, sign and show where every clause came from, with your own changes tracked against the source.
- Adopted
AML & CTF Program
provider library + your edits
- Adopted
Sanctions screening
provider library + your edits
- In review
Customer due diligence
provider library + your edits
02 · Controls
Every obligation becomes a control you can prove
We work with you to build a control layer for your program: built-in rules that run directly on the Rehive platform, plus checks integrated through specialized third parties. Each control is typed by how it runs, and is the actual enforced behaviour with system evidence behind it, not just an attestation.
- Automated
OFAC & sanctions screening
onboarding + ongoing
- Automated
PEP & adverse-media screening
risk-scored
- Automated
Velocity & structuring detection
38 monitoring rules
- Third-party
Device & session risk scoring
via Sardine
- Configurable
New-account limits & step-up auth
tuned per program
- Hybrid
Source-of-funds RFI on breach
auto-triggered
- Manual
Independent AML program review
attested annually
03 · Monitoring
Monitoring that runs the playbook
Alerts route to your team with the next step attached: pause, verify, request documents, respond, return funds. Every decision lands in an audit trail you can hand to a provider or a regulator.
- Velocity spike · 14 transfers in 1hAuto-limited
- New device + payout detail changeStep-up auth sent
- Name mismatch on incoming wireRouted to review
Every decision logged
04 · Risk stack
A risk stack we keep tuning
We wire up tools like Sardine and SumSub for your use case, then keep tuning them as fraud patterns and provider rules change. What one program learns, every program's config benefits from. Not a one-off setup.
28 Junsardine.device_velocity3/day → 2/day
Card-onramp ring pattern flagged
12 Junsumsub.doc_check (NG)basic → enhanced
Provider requirement update
03 Junlimits.first_week_cap$2,500 → $1,000
New-account recall trend
05 · Evidence
Evidence, ready when asked
Point-in-time proof per control, a reviewer trail behind every decision, and exports in the formats partners, auditors and regulators expect. The answer to "prove it" is a button.
- 135 controls with point-in-time proof
- Reviewer trail on every decision
- Provider and auditor formats
Every control maps to a defined standard for stablecoin programs.
Policies, vendor configs and evidence all trace back to one published set of requirements, shaped with the providers and reviewers who hold programs to account. Meet the standard and you can show it: to your provider today, to independent auditors as certification matures.
- RCS-01Customer verification before first transaction
- RCS-07Velocity limits on new accounts
- RCS-12Device and session risk signals in scoring
- RCS-19RFI response inside the provider window
- RCS-24Point-in-time evidence for every control
Build it with us.
We're shaping compliance with a small group of design partners. Come help define what launch-ready looks like.