Checks protect merchants, platform integrity, and counterparties. They help reduce abuse, enable traceability, and support compliance obligations.
Why checks exist
- Prevent misuse and high-risk abuse patterns before transaction access is granted.
- Verify identity and ownership context for merchants that receive funds.
- Maintain auditability and transparent risk controls while keeping payer checkout lightweight.
Automated vs manual checks
Automated in background
- Sanctions and AML screening on required identity subjects.
- Risk scoring and policy checks tied to onboarding data.
Merchant actions required
- Email verification.
- Enable MFA in Security settings as a strongly recommended security layer, even though it is no longer a hard requirement for live transaction access.
- Complete KYC verification flow.
Wallet and asset setup
Live transaction access also depends on operational readiness, not only identity review. Merchants still need at least one configured payout wallet and at least one accepted cryptocurrency before they can create live payment requests.
- Add wallet addresses carefully, because payouts and direct payment settlement depend on correct merchant wallet data.
- Enable only the chains and assets you actually want to receive, so checkout stays clean and intentional for the payer.
- Use MFA anyway if the account controls public payment pages, merchant wallets, or operational checkout settings.
Open the individual and business checklists for step-by-step completion requirements.