StablecoinGateways

Stablecoin gateway country restrictions: eligibility comes before fees

Published November 8, 2026 · By the StablecoinGateways research team. Public-source research; no account approval or integration test performed.

Sources checked November8,2026. This is a provider-research checklist, not legal advice or a comprehensive jurisdictional survey. It does not approve a business for a service.

The short answer

A gateway's token list and headline fee tell you little if the merchant cannot open the required account. Check merchant jurisdiction, customer geography, product/account eligibility and settlement destination separately before recommending a provider.

“Customers globally” is not the same as “merchants everywhere.” “USDC supported” is not the same as “this US business can receive USDC through this checkout.” And a technically reachable website is not proof that its terms permit you to use it.

This matters today: NOWPayments' official terms updated October19,2026 say its services are not rendered to residents or citizens of the EU, UK, US, UAE or Russian Federation. A generic US-facing recommendation to “use NOWPayments for USDT” leaves out a decisive restriction.[1]

Four checks an agency should not collapse into one

Check The actual question Evidence to retain
Merchant eligibility Can this legal/business type in this country/state use this exact product? Current provider terms, product availability page and the client's own approval status
Customer access Which customers/wallets/countries can pay? Customer restrictions and supported asset/network instructions—not the merchant location list
Account/product permission Does the account have the required payment method, platform capability or preview access? Account owner's nonsensitive confirmation; a public launch article isn't account entitlement
Settlement destination What asset/currency arrives where, and can this business withdraw it? Exact payout route, bank/wallet conditions, minimums, fees and timing

Record each separately as documented / account-specific confirmation needed / not established. A single “available worldwide” checkbox is not a defensible scope.

Example 1: Stripe's customer reach is broader than merchant availability

Stripe's stablecoin overview describes global customer locations subject to restricted-country limitations, but its setup guide says stablecoin payments are available to businesses in all US states except New York. The business requests the Stablecoins and Crypto method; it remains Pending while Stripe reviews it.[2][3]

The same product documentation describes private-preview merchant access for businesses in the EU, Hong Kong, Mexico and Switzerland. “Private preview” should remain that label, not become general availability in a comparison table.[2]

For a Georgia merchant with an existing Stripe account, the location is not the specific New York exclusion. That is only a first filter. It does not prove business-model approval or that the account already has the feature enabled.

Stripe's public standard stablecoin processing price is1.5%. That useful number should come after eligibility in the shortlist, not before it.[4]

Example 2: NOWPayments' terms override a broad token/checkout impression

Section15.1 of NOWPayments' official terms lists the EU, UK, US, UAE and Russian Federation restriction. It speaks to residents or citizens, not just the IP address used to visit the site. Section15 also reserves market selection and restriction rights.[1]

For an agency serving a US merchant, that is a reason not to recommend this route as available based on a token list or marketing comparison. Do not infer permission from being able to register, load the checkout, connect a wallet or reach the API. Do not suggest a VPN, different address or foreign account to bypass terms.

An affiliate arrangement would be a separate eligibility/contract question; a public affiliate page does not establish an exception for a US publisher or a US merchant. This pilot assumes no affiliate approval or commission.

Example 3: An incomplete country list is not a “yes” or a comprehensive “no”

CoinGate has an official supported-countries page. Our accessible text extraction returned a short list of countries; it did not establish US merchant eligibility or provide a reliable basis to claim that every omitted country is prohibited.[5]

The correct output is US eligibility not established in this research. Ask for the relevant current provider/account confirmation before putting it on a client's launch-ready shortlist. Do not fill a research gap with an aggregator's flag icon or assume every EU-based provider serves all US businesses.

A documented unknown is more valuable than a green check that the agency later has to retract.

A token can be accessible while the intended service is not

Ripple's current RLUSD network docs list eight networks. Its Coinbase announcement describes RLUSD access and XRPL/Base/Ethereum deposits/withdrawals. Neither establishes a complete merchant checkout, refund or bank-payout product for every account.[6][7]

Likewise, Circle's native USDC-on-XRPL announcement shows that the token exists on the network; it does not prove your processor's USDC integration supports XRPL or your merchant account.[8]

The route to document is specific:

merchant + business model + provider product + account permission + token/network + settlement destination.

Change any one of those, and the answer may change. A fee comparison with those fields missing is an incomplete buying document.

The 15-minute agency pre-shortlist

This is a research workflow, not a promise that a provider will answer in15minutes:

  1. Write the merchant's country/state, business model, current platform and required settlement currency. Use nonsensitive descriptors, not identity documents.
  2. Open the provider's current legal/availability page and identify the exact product/entity. Record the effective date and the date you checked it.
  3. Separate merchant restrictions from payer restrictions, preview access and account approval.
  4. Confirm the asset/network pair, not merely the token symbol.
  5. Identify the payout, refund and recordkeeping path. Leave unverified fees/permissions unknown.
  6. Remove clearly incompatible candidates before doing an elaborate fee model.
  7. Hand the remaining account-specific questions to the client/provider and label launch readiness accordingly.

The 15-minute shortlist can prevent hours of quoting the wrong build. It is not a substitute for a client's professional advice or the provider's underwriting.

What to put in the agency's statement of work

Keep researched facts separate from dependencies: - “Provider public docs describe this feature as of [date].” - “Merchant account activation and current terms must be confirmed by the account owner.” - “No production launch until the implementation owner validates the exact checkout, order and refund flow.” - “If eligibility or supported route changes, re-scope before implementation.”

Avoid “fully compliant,” “approved everywhere,” “no KYC needed,” “guaranteed access,” and “we can work around the restriction.” Those statements are not established by this research.

Need a defensible shortlist for one client?

Use our existing fee calculator and small-business acceptance guide to organize the next research step. These free resources do not establish account eligibility, guaranteed savings or compliance approval. Paid memo orders are on hold.

Once eligible routes are established, use the existing fee calculator and gateway fee checklist as supporting worksheets. Fees alone are not an eligibility decision.

Primary sources

  1. NOWPayments terms, updatedOctober19,2026, §15: https://nowpayments.io/doc/fd-tos.pdf?v=1.4.2 (query-string version is not proof of a different effective date)
  2. Stripe product availability/properties, official docs CLI: https://docs.stripe.com/payments/stablecoin-payments
  3. Stripe Checkout setup/access request, official docs CLI: https://docs.stripe.com/payments/accept-stablecoin-payments?payment-ui=checkout
  4. Stripe public pricing: https://stripe.com/pricing
  5. CoinGate supported countries, extraction limitations noted: https://coingate.com/supported-countries
  6. Ripple current networks: https://docs.ripple.com/products/stablecoin/overview/supported-chains-and-networks
  7. Ripple Coinbase announcement October28,2026: https://ripple.com/ripple-press/ripple-and-coinbase-partner-to-expand-access-to-rlusd/
  8. Circle USDC-on-XRPL launch June12,2025: https://www.circle.com/blog/now-available-usdc-on-the-xrpl

Method: primary public-source comparison, no account approval or integration tests. No affiliate link or commission was assumed. Recheck terms before recommending or purchasing a service.

Related agency research: RLUSD vs USDC payment routes