Playbook: Merchant KYB
The wedge: packet completeness + evidence binder for PayFac onboarding.
How we're different
- Ops-first KYB workflows (not just checks).
- Exception handling and follow-ups built in.
- Binder export with approvals and evidence links.
Trust rule: AI drafts; humans decide for sensitive outcomes.
Required steps
- Intake normalization and case creation
- Doc request + chasing loop
- Business verification (vendor/adapters)
- UBO collection and KYC checks
- Sanctions/watchlist screening
- Exception remediation and approval gate
- Evidence binder export (PDF + JSON)
What KYBRIQ automates
Checklist engine
Deterministic requirements by policy + risk tier.
Follow-ups
Auto-draft doc requests and reminders with approval gates.
Binder builder
One-click packet export with evidence links.
What needs approval
- Sending external emails (policy-configurable)
- Final approve/reject decisions
- Any high-risk overrides or exceptions
Evidence captured
- Uploaded documents + hashes
- Vendor check requests/responses
- Approval history + rationale
- Immutable action timeline
Time-to-first-value
Illustrative:
- Day 1: connect intake + storage; import 25 cases
- Day 7: deterministic checklist + follow-up sequencing live
- Day 14: evidence binder exports + approvals in production pilot
Run this playbook in a pilot
Start with one KYB packet format and make it repeatable.