6-8 weeks from contract to production on live application data. Payment platform connectivity, compliance system integration, and risk policy rule configuration occupy the first phase, followed by parallel testing on live application volume before handover.

Your payment platform for merchant activation and account write-back; your compliance system for KYC record storage and audit trail; your business registry interface for entity verification; and your PEP and sanctions screening provider. Specific connectors confirmed during scoping.

A targeted request is sent directly to the merchant or relationship manager identifying the specific document required and the reason it is needed. The application is held and resumes automatically when the document is received and validated. No manual follow-up is needed.

The ownership threshold, typically 25%, is encoded in the workflow configuration. UBOs at or above the threshold are identified from the submitted ownership structure and screened automatically. Where the ownership structure is complex or layered, the case routes to the compliance specialist with the structure and the identified UBOs documented.

High-risk MCC codes, merchants operating in high-risk jurisdictions, UBOs with PEP status, adverse media hits, and declared transaction volumes above the standard tier threshold. All of these route to the compliance specialist with the complete screened and validated file assembled rather than a blank application.

The business verification result, the UBO identification with screening outcomes, the document validation status, the specific risk indicators identified, and a structured case summary. The specialist reviews the substance of the risk rather than assembling the evidence from scratch.

No. Activation follows from the acquirer's encoded risk policy applied to the verified and screened merchant record. The AI layer handles application intake, business verification, and evidence assembly. The rules layer governs every approval and activation action. No merchant is activated without a complete KYC record and a policy-compliant approval.

Yes. Required document packs, screening requirements, and risk assessment criteria are configured independently by merchant category and risk tier. A standard retail merchant runs against different criteria than a high-risk e-commerce merchant or a financial services intermediary.

Standard merchant onboarding software collects documents and routes them to a reviewer - it was built for intake, not for verifying business entities against registries, identifying UBOs from ownership structures, running PEP and sanctions screening per UBO, validating document packs by merchant category, assessing merchants against acquirer risk policy, and activating in the payment platform with a complete KYC audit trail. KYC verification software purpose-built for this workflow eliminates the manual review loop on standard cases. Merchant onboarding automation software that covers only one step still requires the compliance team to bridge the rest. Noxus runs the full onboarding chain end to end on the existing payments and compliance stack.

Screening platforms run PEP and sanctions checks in isolation - they do not verify the business entity, identify UBOs from the ownership structure, validate the document pack by merchant category, assess the merchant against the acquirer's risk policy, or activate the merchant in the payment platform with a complete KYC audit trail. Merchant onboarding solutions that collect documents still require manual verification. KYC verification solutions that run checks still require a human to assess the output and route the outcome. Noxus runs the full onboarding chain end to end on the existing payments and compliance infrastructure.