Skip to main content
Compliance Architecture
The Open Money Stack includes compliance as a core layer, not a third-party add-on. KYC, KYB, AML screening, and transaction monitoring are built into the regulated fiat access infrastructure. Institutions can use the OMS compliance layer directly, or bring their own verification process where they already have one.

Consumer onboarding (KYC)

Every consumer transacting through the OMS must complete identity verification before their first transaction. This satisfies AML obligations across supported jurisdictions. There are two paths:

Option 1: Use the OMS KYC process

The OMS handles the full KYC flow on your behalf. Users complete identity and document verification through the built-in process. No additional identity infrastructure required. What is collected:
  • Government-issued ID (passport, driver’s license, national ID)
  • Liveness check
  • Name, date of birth, address
  • OFAC and PEP screening

Option 2: Bring your own KYC

Organizations with an existing KYC process can pass verified user identities to the OMS directly. The OMS accepts KYC status from approved organizations, so users who have already been verified do not need to repeat the process. This is the preferred path for regulated fintechs, neobanks, and PSPs that already operate licensed identity verification.

Business onboarding (KYB)

For B2B and B2B2B flows, the OMS supports business onboarding with Know-Your-Business (KYB) verification. This is required for business customers transacting above standard thresholds or in regulated corridors. What is collected:
  • Legal company name and registration details
  • Date and jurisdiction of incorporation
  • Company type and tax identification number
  • Registered address
  • Ultimate Beneficial Owner (UBO): full legal name and identity verification
  • Business contact: phone and email
KYB is structurally similar to consumer KYC but scoped to the entity and its controlling persons. The OMS handles collection, screening, and ongoing monitoring.

Transaction monitoring (AML)

Compliance does not end at onboarding. The OMS applies continuous transaction monitoring across all payment flows:
  • Onchain screening: every wallet address and transaction is screened against sanctions lists and risk databases before settlement
  • Risk scoring: transactions are scored in real time based on counterparty risk, geography, and behavior patterns
  • OFAC and PEP checks: applied at onboarding and re-screened on an ongoing basis
  • Suspicious activity: flagged transactions are reviewed before funds are released; reporting obligations are handled by the OMS compliance infrastructure

Regulatory coverage

The OMS compliance infrastructure operates under Money Transmitter Licenses (MTLs) across 38 US states and internationally. Institutions building on the OMS inherit this coverage rather than obtaining it independently.

Get early access

Contact us to learn more about OMS compliance coverage and integration options.

Building your own compliance stack

For teams building custom payment infrastructure outside the OMS, the following providers are used in production by payment applications on Polygon.

Identity verification (KYC/KYB)

ProviderDetails
SumsubGlobal KYC/KYB, document verification, liveness checks
OnfidoDocument and biometric verification
PersonaModular identity platform, KYC and fraud prevention

Transaction monitoring (AML)

ProviderDetails
ChainalysisOnchain transaction screening and risk scoring
TRM LabsBlockchain risk intelligence and compliance
EllipticCrypto asset risk management
Polygon does not endorse or provide support for third-party compliance providers. Regulatory requirements vary by jurisdiction. Consult legal counsel for your specific product.