Integration Guides
  1. Direct Acquiring

Phase 5 — Automated Screening

Steps 14–16 of reseller onboarding — automated document legitimacy, sanctions / MATCH screening, and compliance Jira ticketing. No reseller action required.

📘

Part of Merchant Acquiring Reseller — Phase 5 of 6 · Actor: System

Everything in this phase runs automatically once the wallet creation call in Phase 4 succeeds. No reseller action is required — these steps are documented so you understand what happens behind the scenes and can correlate inbound Jira tickets to the right merchant case.

Step 14 — Document legitimacy checks

Each uploaded document is validated by a type-specific processor.

Actor: System

ProcessorValidates
certOfRegistrationCERT_OF_REGISTRATION / CERT_OF_INCORP
businessLicenseBUSINESS_LICENSE if uploaded
nationalIdentityCustomer ID documents
proofOfAddressPROOF_OF_ADDRESS
bankStatementBANK_STATEMENT

Step 15 — Sanctions and MATCH screening

MATCH, OFAC, PEP, UN, EU, and internal blacklist checks run in parallel.

Actor: System

CheckSource
matchCheckMastercard MATCH — terminated merchant list
ofacCheckUS Treasury Office of Foreign Assets Control
pepCheckPolitically Exposed Persons
unCheckUN Security Council consolidated list
euCheckEU sanctions list
internalBlackListCheckEFT Corporation internal blacklist

Step 16 — Compliance Jira ticket auto-raised

Fires only if any screening processor returns hits. A clean result produces no ticket and the flow continues to Phase 6 compliance review.

Actor: System

When a hit is returned, JiraRatifyResultAlerter opens an issue in the compliance project automatically.

Jira ticket summary format

TenantID - {tenantId}, OrgID - {orgId} -- KYB Organisation Compliance agency Checks Result
📘

Tenant configuration required

Jira auto-creation depends on compliance.jira.ticket.config.* being configured on the tenant.

Navigation