ISO Gaming Payments: Market Checklist

What should an ISO establish before discussing a gaming referral?

Begin with the business role and the precise activity. An operator accepting player funds, a company supplying software and a marketing business do not describe the same payment opportunity. Ask which entity is seeking processing, the operating brand and the actual product offered to customers. Do not use online gaming as a catch-all for unrelated business models.

This guide concerns legitimate licensed-operator referrals. The first task is to describe the requested payment arrangement precisely enough for a potential partner to assess it. Licensing questions belong with the relevant authority and the operator's qualified advisers; a processing discussion does not replace that work.

Sources: Gambling Commission: Remote sector guidance; Gambling Commission: Preventing credit card use

Why should the brief identify customer markets separately?

The Gambling Commission states that a license is needed to provide remote gambling facilities to consumers in Great Britain, including when the business is based abroad. Its guidance also distinguishes different licensed activities. This is a Great Britain example of why the location of the business alone does not answer the market question; it is not a summary of every jurisdiction's law.

MerchantBridge's suggested preparation is a market map: the operator's domicile, the markets it says it may serve, the relevant authority and the activities covered. Ask the operator to distinguish current permissions from an application or planned expansion. Do not turn a market listed in a business plan into a statement of confirmed authorization.

• Operator: the legal entity and brand seeking the arrangement.
• Activity: the specific licensed business, not a generic gaming label.
• Authority: the relevant regulator, public register reference and license status.
• Customer markets: current service areas, proposed expansion and excluded locations.
• Verification: who confirmed the information and when it was last checked.
• Uncertainty: any market or activity requiring further professional confirmation.

How should deposits and withdrawals be described?

Ask for two separate operational descriptions. The first explains how an eligible customer funds an account or makes a purchase. The second explains how a withdrawal or other outbound payment is requested, reviewed and delivered. A request for card acceptance does not establish support for every outbound function.

Record requested methods and currencies as requirements, not confirmed features. Identify the platform involved and the person who can answer implementation questions. If a provider has not confirmed a capability, keep it marked unconfirmed. This avoids presenting an attractive deposit feature as evidence that the entire operating workflow is ready.

What does a useful hypothetical brief look like?

Use one row of information for each market rather than a single licensed internationally label. The following fictional Great Britain example illustrates the questions to record; it is not a real license, placement or offer of regional support. Never invent a license number or mark permissions verified without checking the actual operator record.

The resulting question is specific: can an available partner consider this operator, licensed activity and market, and which requested functions could it assess? Expansion markets stay outside the confirmed scope until the operator establishes its permissions and the partner reviews them.

• Entity and activity: Example Gaming Ltd; proposed remote casino operations, not a software supplier or affiliate business.
• Market: Great Britain only for this example; any additional territory listed separately as a proposal.
• License check: insert the actual Gambling Commission register link, license status, permitted activity and date checked before sending the brief.
• Deposits: specify requested methods and currency; for Great Britain do not assume consumer credit-card funding is available, given the Commission's credit-card gambling ban.
• Withdrawals: request separate confirmation of a GBP bank-transfer workflow; no outbound capability has yet been confirmed.
• Implementation: name the platform and technical contact, and identify which player-verification responsibilities need clarification without sharing player records.

What should not be inferred from a license or platform?

Do not infer that a license guarantees payment acceptance, that a platform connection is available or that the operator can serve markets outside its permissions. Similarly, do not conflate licensed gambling with sweepstakes, fantasy contests, prediction products or ordinary video games. Ask for the exact model instead of importing assumptions from an adjacent sector.

A referral conversation should expose unanswered questions early. If the operator cannot clearly identify its activity or the relevant permission, pause the characterization and request clarification. The objective is an accurate introduction, not a workaround for a jurisdictional or provider restriction.

How can an ISO bring the opportunity to MerchantBridge?

Start with your own details, a concise description of the licensed business and the payment function that needs review. Public business and license references can provide context without sending player records, identity documents or account histories in the first message.

MerchantBridge can explore relevant acquiring relationships for a licensed opportunity outside your present channels. Bring the market map and the specific gap, such as an unconfirmed deposit method or outbound-payment requirement. Geographic scope, capabilities, acceptance and referral terms are reviewed individually; this guide promises no particular country, state or platform coverage.