Priority markets
- United States
- United Kingdom
- Brazil
- Mexico
- India
- Indonesia
- Philippines
- United Arab Emirates
- South Africa
- Singapore
Merchant entry sequence
- Write a neutral flow-of-funds memo covering customer payment, balance movement, redemption, refund, reversal, and payout paths.
- Pre-screen each provider for restricted categories, entity eligibility, prohibited jurisdictions, and required compliance documentation.
- Separate ordinary checkout, wallet-like balances, crypto-adjacent references, rewards, and payouts into distinct review tracks.
- Ask for written confirmation of allowed use cases, reporting fields, monitoring expectations, and escalation contacts before build work.
- Exclude sensitive or unsupported markets from launch materials and retain evidence for compliance review.
Payment needs
- A conservative pre-underwriting conversation before any payment integration, especially when funds movement, stored value, investment language, crypto assets, rewards, or payouts are involved.
- Clear separation between ordinary software subscriptions, fiat checkout, wallet funding, payouts, trading, yield, token sales, NFT sales, remittance, and regulated financial activity.
- Provider confirmation of whether cards, bank transfers, wallets, local instant payments, and payout routes are available through provider-confirmed PSP, acquirer, gateway, bank, or wallet-operator relationships.
- Compliance-ready documentation for product flow, source of funds, use of funds, customer identity, sanctions screening, transaction monitoring, refund/dispute handling, and restricted countries.
- Reconciliation across customer ID, account ID, invoice, fiat transaction, refund, dispute, payout, country, currency, FX, fee components, and settlement batch.
Recommended route categories
- Start with risk-screening and provider-fit questions, not integration work; many PSPs and acquirers treat crypto-adjacent, financial, rewards, and wallet-adjacent models as manual-review categories.
- If the product is only a software subscription, ask providers to confirm that no wallet funding, trading, custody, token sale, yield, gambling, investment advice, or remittance flow is present.
- If payouts, stored balances, fiat on-ramps, off-ramps, rewards, or user-to-user transfers exist, verify whether a provider-confirmed PSP, bank, payout provider, or regulated partner is required.
- Use payment-channel pages only to understand customer-facing methods, then verify access through provider underwriting; do not recommend direct use of local payment methods for crypto funding.
- Without a local entity, ask whether foreign fintech or crypto-adjacent merchants are considered at all and what licenses, compliance policies, local accounts, and settlement currencies are required.
Provider selection questions
- Will you review fintech and crypto-adjacent risk screening for the merchant's exact product model, content category, entity, and buyer countries before integration work starts?
- Which of the priority markets can be evaluated first for this use case: United States, United Kingdom, Brazil, Mexico, India?
- Can the current merchant entity apply for each target country, or should we evaluate a local PSP, global PSP, acquirer, gateway, wallet operator, or merchant-of-record style route?
- Which customer-facing methods can be considered for one-time payments, recurring payments, payment links, invoices, refunds, and failed-payment recovery in this category?
- What documents, website disclosures, product descriptions, prohibited-category checks, and compliance review steps are needed before method activation?
- How do API events and reports represent payment attempts, pending states, captures, refunds, partial refunds, chargebacks, reversals, webhook retries, and manual adjustments?
- Can reports include merchant order ID, customer or account ID, country, currency, FX fields, fee components, refund status, dispute status, payout or settlement batch, and provider reference?
- How should operations handle this stated need: A conservative pre-underwriting conversation before any payment integration, especially when funds movement, stored value, investment language, crypto assets, rewards, or payouts are involved.?
- How should finance and support handle this stated need: Clear separation between ordinary software subscriptions, fiat checkout, wallet funding, payouts, trading, yield, token sales, NFT sales, remittance, and regulated financial activity.?
- Which claims about method availability, settlement, coverage, onboarding, support channels, or compliance status should remain unpublished until confirmed in writing?
Risk and compliance notes
- Fintech, stored-value, investment, remittance, crypto-adjacent, rewards, or wallet-like models may require enhanced review before a provider will discuss integration.
- A payment route being listed for a country does not mean the merchant category, flow of funds, or customer geography is acceptable for that provider.
- Do not state or imply provider authorization, regulatory status, or category acceptance unless it is verified from the provider in writing.
- KYC, KYB, sanctions screening, source-of-funds checks, restricted jurisdictions, transaction monitoring, and suspicious-activity workflows should be treated as gating requirements.
- Russia, Venezuela, and Myanmar should appear only as compliance or risk-exclusion references, never as launch-market examples.
- Chargebacks, reversals, fraud losses, account freezes, reserves, and law-enforcement requests need documented ownership before launch.
- Marketing copy should avoid claiming financial, investment, or crypto capabilities beyond what the merchant and provider can substantiate.