Merchant KYB onboarding
Registry, UBO and sanctions checks in one flow; low-risk merchants start accepting payments the same day.
Merchant KYB onboarding
- Application #MB-3107: Demir Tekstil Ltd., MCC 5651, expected volume 850,000/month
- Registry record pulled: incorporated 2016, 2 signatories; tax number and circular match
- Plan: ownership chain → sanctions/PEP → risk tier → MSA → account
- Ownership: 2 UBOs (60% / 40%), chain depth 2, one intermediate legal entity
- 2 UBOs and the company screened for sanctions/PEP, 1 fuzzy match (0.58)
- Policy v2.1: MCC 5651 medium risk, volume above threshold → risk tier: high
- Risk tier high → compliance manager reviewed and approved the file
- MSA v4.2 sent to both signatories for e-signature, signed within 3 hours
- Merchant account MID 88231045 created, payment acceptance live
- Welcome email: MID, API key and T+1 settlement schedule
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Application form and document upload on the Merchant Portal
Merchant account live, risk tier assigned, MSA e-signed, decision trail stored
Agents
Merchant Onboarding Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Business Identity Agent
Verifies trade registry, tax number and signatory circular
extract_registry_fieldsverify_tax_numberparse_signatory_circularUBO Agent
Resolves the ownership chain, identifies and screens UBOs at ≥ 25%
resolve_ownership_chainidentify_uboscreen_sanctionsscreen_pepRisk Agent
Assigns a risk tier from MCC, volume and sector data
check_mcc_policyestimate_volumeassign_risk_tierContract Agent
Sends the MSA for e-signature, activates the merchant account
send_esigncreate_merchantsend_emailSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Merchant Onboarding Supervisor | Application #MB-3107: Demir Tekstil Ltd., MCC 5651, expected volume 850,000/month | — | 220 | — |
| 02 | tool | Business Identity Agent | Registry record pulled: incorporated 2016, 2 signatories; tax number and circular match | Trade Registry (MERSİS) | 480 | — |
| 03 | plan | Merchant Onboarding Supervisor | Plan: ownership chain → sanctions/PEP → risk tier → MSA → account | — | 300 | 210 |
| 04 | reason | UBO Agent | Ownership: 2 UBOs (60% / 40%), chain depth 2, one intermediate legal entity | — | 760 | 900 |
| 05 | tool | UBO Agent | 2 UBOs and the company screened for sanctions/PEP, 1 fuzzy match (0.58) | Sanctions Screening | 540 | — |
| 06 | verify | Risk Agent | Policy v2.1: MCC 5651 medium risk, volume above threshold → risk tier: high | — | 640 | 720 |
| 07 | approval | Merchant Onboarding Supervisor | Risk tier high → compliance manager reviewed and approved the file | — | 3,400 | — |
| 08 | write | Contract Agent | MSA v4.2 sent to both signatories for e-signature, signed within 3 hours | e-Sign | 620 | — |
| 09 | write | Contract Agent | Merchant account MID 88231045 created, payment acceptance live | Merchant Portal | 520 | — |
| 10 | notify | Contract Agent | Welcome email: MID, API key and T+1 settlement schedule | 260 | — |
AML transaction monitoring alert triage
Alerts arrive enriched with a draft narrative; the analyst always decides and the filing goes out in minutes.
BNPL instant instalment decision
Checkout instalment decision in seconds from bureau and open-banking data; large tickets go to underwriting.
Payment reconciliation exceptions
PSP settlement files matched to the ledger; small breaks fix themselves, large ones go to finance approval.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis