Week 1
of a licence deadline
The requirement arrives with a date attached and no room to evaluate.
By industry
Compliance that does not slow the roadmap
A sandbox key, one endpoint and a signup flow that still converts — with the audit trail your first regulated partner will ask to see.
What you switch on
What a fintech switches on first
The minimum a sponsor bank accepts, without a platform migration later.
Why this matters here
Compliance arrives the week your bank partner asks for it.
Most fintechs buy AML tooling under deadline: a sponsor bank, a licence application or a payment scheme wants evidence by a date. Tooling chosen that way is integrated badly and lived with for years.
Conversion
dies in the signup flow
Every second added to onboarding costs users you paid to acquire.
Two engineers
for six weeks
Integration work nobody planned, taken from the product roadmap.
15 min
Sandbox key to first call
1
Endpoint at onboarding
150 ms
Median response
0
Procurement calls to start
Journey · Sideways
Scroll to advance
A customer through your funnel
-
Step 01
Sandbox key, no call
Generated in the browser with test data loaded and a copyable curl command.
-
Step 02
One POST in the signup flow
Synchronous screening inside the request your form already makes. No queue, no second screen.
-
Step 03
Register for monitoring
One PUT and the customer stays in scope. Everything after that arrives as a webhook.
-
Step 04
The evidence your partner wants
Decision trail and evidence packs, ready for the sponsor bank’s review rather than assembled for it.
complead / sandbox
- Time to keyinstant
- Test entities5,000
- Rate limit60/min
complead / screening / search
- EndpointPOST /v1/screening/search
- Median148 ms
- Added to signup0 screens
complead / monitoring / register
- Registered48,102
- Interval15m
- Webhookconfigured
complead / audit
- Decisions retained48,102
- Exportper case or period
- Retentionto policy
Sandbox
Screen
Monitor
Evidence
What you answer to
Who will actually audit you
Before a regulator does, your sponsor bank and your payment scheme will. Their questions are the same, asked earlier.
Read the compliance guides
Sponsor bank
Programme evidence and decision trail
Before launch
Payment scheme
Screening coverage and response times
On onboarding
Regulator
Risk assessment and named officer
On licensing
Auditor
Retrievable decisions per period
Annual
Case study · Fintech
Read the case study
From sandbox key to sponsor-bank sign-off in a month
A lending app integrated screening in an afternoon, then spent the remaining time on the evidence pack rather than the plumbing. The sponsor bank review took one meeting.
1 day
To first live call
4 weeks
To sign-off
0
Extra signup screens
Cross-family links
Where teams like yours go next
FAQ
Before you ask us
Do we need a contract to start?
No. The sandbox key is generated in the browser and works against test data immediately.
Will this slow our signup?
Screening is synchronous at around 150 ms, which fits inside the request your form already makes.
What does our sponsor bank get?
A decision trail per customer and an evidence pack per period, generated rather than assembled.
What happens when we grow?
Rate limits scale with the plan; nothing about the integration changes when volume does.
Get a sandbox key and screen a name in fifteen minutes
No call, no contract. If it fits your flow, the commercial conversation is easier afterwards.
3,000+
Data sources checked
220+
Countries covered
15 min
Always real-time data