KYC / AML / OFAC Procedures

Identity verification and anti-money-laundering controls are not a single feature, they are handled by the payment processor for the payment side, and remain a decision the business needs to make for the settlement side. This page states plainly which is which.

1. What is true today

Every payment on this platform is collected through Stripe's hosted Checkout, described fully in PCI DSS Scope. That means the customer, the payment method, and the transaction itself are all screened by Stripe's own onboarding and transaction-monitoring systems, including sanctions-list checks, before a charge is ever completed. This platform inherits that baseline for every payment it processes, without any additional integration work, simply by virtue of routing all payments through Stripe.

This is genuinely meaningful coverage, not a gap being glossed over: Stripe is itself a regulated payment institution with its own KYC/AML/OFAC program that every merchant and every transaction on its platform is subject to. What is described below as "not yet built" is specifically the additional, business-level screening a company sometimes chooses to layer on top of its payment processor, not a missing basic control.

2. What is not yet built, and why it might matter to you

Depending on your business model, you may need controls beyond what Stripe provides, for example, if you plan to onboard enterprise accounts with very high transaction volumes, hold a balance on behalf of customers, or operate in a regulated vertical. The following would need to be built or contracted for, they are not present today:

Control areaWhat it would involveWhat already exists to build on
Know Your Customer (KYC)Verifying a business customer's legal entity, tax ID / EIN, and beneficial ownership before onboarding them at a higher tier or volume.None today beyond what Stripe requires at the account level. Would require integrating a third-party identity verification provider.
Anti-Money Laundering (AML) transaction monitoringWatching for unusual transaction patterns, structuring, or rapid movement of funds across accounts, beyond individual payment screening.The real, append-only ledger and settlement records already capture every transaction with a verified history, which is exactly the data an automated monitoring rule would need to run against. No anomaly-detection rules exist yet.
OFAC / sanctions-list screening at the account levelScreening an account holder or payout destination against sanctions lists at onboarding and periodically thereafter, independent of Stripe's own per-transaction checks.Would require a real-time sanctions-list matching service. Not yet integrated.

3. Recommended next step

If your current business model is standard SaaS subscription billing at the plan tiers described in Billing, Stripe's built-in screening is likely sufficient, and there is no urgent gap to close. If you plan to introduce features such as holding customer balances, enabling payouts between accounts, or onboarding enterprise customers at high transaction volumes, that is the point at which a proper KYC/AML program (and likely a conversation with a compliance advisor about which regulations actually apply to your business model) should be built before those features launch, not after.

Was this page helpful?