emerchantpay
emerchantpay directly offers gaming merchants payment processing through its own gateway and in-house acquiring capability. The current gaming product also covers card and alternative payment methods, deposits and payouts, fraud controls, reporting, and merchant-facing account and risk support.
Page updated
emerchantpay is an active multi-entity payments brand. Emerchantpay Limited, UK company 05153270, operates alongside subsidiaries and related undertakings, an EU partner institution, and US sponsor relationships. One defined platform arrangement uses the UK company, but there is no universal merchant counterparty. The contracting and regulated entity depends on market, product, and signed terms, so no single legal name is assigned to the brand.
Buyer decision brief
Use this summary to decide whether the offer belongs on your shortlist and which terms need a written answer.
Fit and use case
Editorial fitGaming operators that need a merchant-facing gateway and acquiring provider rather than an orchestration layer that only connects external accounts.
Primary offer: Gaming Payment Processing and Acquiring · 1 additional offer below
Primary offer delivery
- API
Integration boundary: A gaming operator completes merchant review and integrates through the emerchantpay gateway API or a hosted payment form.
Critical contract questions
Start with unresolved terms, negotiated terms, and dependencies that need a named owner.
Resolve before shortlist
No usable standard answer is available on the public terms.
- Pricing and reservesNot disclosed
- Gaming Payment Processing and Acquiring · Commercial terms
- Gateway, PSP, and reserve termsNot disclosed
- Gaming Local Payment Method Access · Commercial terms
- Portability and terminationNot disclosed
- Gaming Payment Processing and Acquiring · Exit and portability
- Method and PSP exitNot disclosed
- Gaming Local Payment Method Access · Exit and portability
Fix in the signed order
The answer changes by operator, market, package, or negotiated order.
4 of 12 shown- Merchant and jurisdiction approvalSet in contract
- Gaming Payment Processing and Acquiring · Market and approvals
- Method-level gambling approvalSet in contract
- Gaming Local Payment Method Access · Market and approvals
- Contracting and regulated partiesSet in contract
- Gaming Payment Processing and Acquiring · Contract and supplier
- Merchant relationshipSet in contract
- Gaming Local Payment Method Access · Contract and supplier
Next buyer step
Ask emerchantpay to resolve “Pricing and reserves” and “Gateway, PSP, and reserve terms” before moving Gaming Payment Processing and Acquiring to a commercial shortlist. Then compare the answer with the complete product record below.
Confirm every selected term in the proposal and signed order. No price, market approval, availability, or contracting entity is implied unless it is stated above.
What this provider offers
2 offerings- TypePayments · Multi ProductOwnership and packagingFirst Party · StandaloneDeliveryAPICompare in
- iGaming Payment Providers · Service Provider
- High-Risk Gambling Payment Processors · Service Provider
- TypePayments · Multi ProductOwnership and packagingMixed · Standalone and BundledDeliveryAPI, iFrameCompare in
- iGaming Local Payment Method Providers · Aggregator
Gaming Payment Processing and Acquiring
Multi ProductFirst PartyAvailability: Standaloneemerchantpay directly offers gaming merchants payment processing through its own gateway and in-house acquiring capability. The current gaming product also covers card and alternative payment methods, deposits and payouts, fraud controls, reporting, and merchant-facing account and risk support.
The brand operates through a UK electronic money institution, an EU partner institution, and US sponsor relationships. Each operator must confirm its contracting provider, regulated permissions, settlement route, and available methods.
Products
Integration: A gaming operator completes merchant review and integrates through the emerchantpay gateway API or a hosted payment form. The exact acquiring entity, supported payment methods, payout route, and settlement arrangement are set by the approved merchant configuration and contract.
Delivery options
API
Delivery modelDirect gateway API or hosted payment form access for an approved gaming merchant under the applicable payment-provider relationship.
Included
- + Card acquiring and payment processing
- + Gateway API and hosted payment form options
- + Supported alternative payment methods and payouts
- + Fraud, chargeback, reporting, and reconciliation tools
Not included
- ! Guaranteed merchant approval
- ! Universal country or payment-method coverage
- ! Fixed reserves, settlement schedules, or fees
Procurement record
Current product boundaries and the terms that still have to be fixed in the signed order or service agreement.
Known is usable now. Contract specific changes by order or market. Not disclosed has no usable standard term. Unknown remains unresolved. Outside provider scope is handled by the operator or another supplier.
Contract and supplier
- Contracting and regulated partiesContract specific
- The brand can use Emerchantpay Limited, an EU partner institution, or United States sponsor relationships. The order must name the gateway provider, acquirer, processor, collecting agent, sponsor bank, and settlement party used by the gaming merchant.
- Merchant relationshipContract specific
- The operator applies as a gaming merchant for direct gateway and acquiring services. Some payment routes can rely on another PSP or sponsor relationship, so the contract must distinguish in-house acquiring from referral, processing, or collection roles.
Implementation
- Cards, methods, and integrationContract specific
- The approved configuration can include cards, alternative methods, deposits, payouts, direct API, hosted payment form, fraud controls, reporting, and chargeback tools. Methods, countries, currencies, directions, credentials, and settlement routes require a merchant schedule.
Operating responsibilities
- Payment data and security scopeContract specific
- Server-to-server and hosted payment-form integrations create different PCI and data boundaries. The agreement needs controller and processor roles, payment-data locations, token ownership, subprocessors, retention, breach duties, fraud-data exchange, and access rights for every route.
Operations and service
- Settlement and reconciliationContract specific
- The acquiring service includes authorization, processing, and settlement, while connected routes can use other providers. Settlement company, safeguarded account, currency, cutoffs, netting, payout funding, deductions, exceptions, and finance reports must be defined for the merchant.
- Chargebacks and disputesContract specific
- Chargeback operations are available. The order must assign fraud monitoring, alerts, evidence, representment, deadlines, scheme monitoring, dispute fees, loss allocation, player contact, ledger adjustment, and escalation across emerchantpay and any underlying provider.
Commercial terms
- Pricing and reservesNot disclosed
- Gateway, acquiring, processing, method, payout, foreign-exchange, dispute, minimum, reserve, collateral, and termination charges are not published for gaming merchants.
Market and approval scope
- Merchant and jurisdiction approvalContract specific
- Approval must cover the operator entity, owners, gambling licenses, domains, player countries, products, currencies, methods, transaction directions, and underlying financial providers. Acceptance is never transferable from the general gaming offer to an unapproved merchant or market.
Exit and portability
- Portability and terminationNot disclosed
- Token portability, transaction exports, pending payouts, open chargebacks, safeguarded balances, reserve release, provider handoff, data deletion, and post-termination reporting are not established outside the merchant agreement.
Strengths
- + The gaming offer combines merchant support with in-house acquiring and a first-party gateway.
- + Integration options include direct API and hosted payment flows, with operational reporting and chargeback handling.
What to verify in procurement
- ! Gaming merchant acceptance criteria, reserves, settlement schedules, and fees are not disclosed.
- ! The regulated provider, license responsibility, merchant-of-record role, data-controller role, and accepted gambling jurisdictions are contract-specific.
Gaming Local Payment Method Access
Multi ProductMixedAvailability: Standalone and Bundledemerchantpay gives approved gaming merchants a gateway route to local and alternative methods. Pix, BLIK, and Bancontact are expressly available for gaming deposits; a wider catalog of bank, wallet, voucher, and cash-based methods requires method-level merchant approval.
This is mixed delivery rather than ownership of every listed method. Emerchantpay Ltd can act as gateway and primary contact while an authorized PSP supplies payment services under a direct contract, referral arrangement, or collecting-agent route. Each method needs its own provider, country, transaction direction, gambling approval, settlement, and data-role allocation.
Products
Integration: The operator completes gaming-merchant review, agrees the exact method and PSP schedule, and uses either the gateway API or hosted Web Payment Form. A method can require a separate PSP contract. Settlement can come directly from that PSP or through emerchantpay as collecting agent only when the contract says so.
Delivery options
API
Delivery modelServer-to-server gateway access for the local methods approved in the operator's merchant and PSP configuration.
- Operator license
- Operator
- Merchant of record
- Operator
- Player data controller
- Unknown
Included
- + Gateway connection to approved local-method and acquiring providers
- + Method activation, transaction status, reporting, and reconciliation tooling
- + PSP application and referral support where required
- + Direct PSP settlement or optional emerchantpay collecting-agent settlement under the signed schedule
Not included
- ! Ownership of third-party local payment methods
- ! Automatic gambling acceptance for every catalog method
- ! Guaranteed deposit and payout support in both directions
- ! A universal underlying PSP, contracting entity, settlement route, or reserve policy
iFrame
Delivery modelHosted Web Payment Form access for enabled local methods, with payment information collected and processed on emerchantpay-hosted infrastructure.
- Operator license
- Operator
- Merchant of record
- Operator
- Player data controller
- Unknown
Included
- + Hosted payment-data collection for enabled methods
- + Lower merchant PCI scope than the server-to-server route
- + Gateway routing to the approved underlying PSP or method provider
- + Transaction reporting through the merchant setup
Not included
- ! Transfer of the operator's gambling or merchant obligations
- ! Proof that every catalog method is available to gaming merchants
- ! A universal GDPR controller allocation
- ! Automatic payout support for deposit methods
Procurement record
Current product boundaries and the terms that still have to be fixed in the signed order or service agreement.
Contract and supplier
- Method supplier chainKnown
- Emerchantpay Limited can supply the gateway and primary merchant contact while an underlying PSP supplies the payment service through a direct contract, referral, or collecting-agent arrangement. Each method schedule must name both roles.
- Merchant relationshipContract specific
- The operator contracts directly with an underlying PSP when required. Emerchantpay can receive PSP-originated settlement as collecting agent only when that role is expressly included; connector access alone does not create a merchant account.
Implementation
- Local methods and directionsContract specific
- Pix, BLIK, and Bancontact are available for gaming deposits; every other method needs its own gambling approval. The schedule must list country, currency, deposit, payout, refund, limit, API or hosted flow, PSP, and credential owner.
Operating responsibilities
- Payment data and PCI allocationKnown
- Server-to-server integration leaves more payment-data handling with the merchant; the hosted Web Payment Form handles payment information on emerchantpay infrastructure. Each route still needs controller roles, subprocessors, retention, breach duties, method-provider data flows, and access controls.
Operations and service
- Settlement and safeguardingContract specific
- Settlement can come directly from the underlying PSP or pass through emerchantpay as collecting agent when agreed. The schedule must define safeguarded balance treatment, currency, cutoffs, deductions, payout funding, bank credits, reconciliation records, and exception ownership.
- Refunds, returns, and disputesContract specific
- Deposit availability does not establish withdrawals or refunds. Each method needs rules for returns, reversals, consumer complaints, failed payouts, evidence, deadlines, fees, loss allocation, and escalation between the merchant, emerchantpay, and the underlying PSP.
Commercial terms
- Gateway, PSP, and reserve termsNot disclosed
- Gateway fees, separate PSP rates, method charges, foreign exchange, payout and refund fees, minimums, reserves, collecting-agent deductions, and termination costs are not published as one gaming tariff.
Market and approval scope
- Method-level gambling approvalContract specific
- Every method requires approval for the operator, gambling license, domain, player country, currency, transaction direction, underlying PSP, and settlement route. Connector availability and gaming eligibility are separate decisions.
Exit and portability
- Method and PSP exitNot disclosed
- Notice, replacement-provider assistance, token migration, pending payment treatment, safeguarded-balance release, open disputes, complete exports, and post-termination access are not disclosed across the underlying method providers.
Strengths
- + The gaming offer names real local methods instead of relying on an undifferentiated logo count.
- + Merchant contracts separate gateway services, third-party PSP agreements, settlement, safeguarding, and payment-data responsibilities.
What to verify in procurement
- ! Pix, BLIK, and Bancontact are available for gaming deposits; other catalog methods require separate gambling approval.
- ! The brand markets in-house acquiring, but the standard merchant agreement also supports third-party PSP, referral-agent, and collecting-agent routes. The signed schedule must identify the actual processing and settlement chain.
- ! Withdrawals, refunds, reversals, and merchant-initiated payouts require their own method approval even when deposits are available.
- ! Hosted and server-to-server routes put payment data in different systems. Each route requires its own DPA and controller allocation.
Reference documents8
Key public documents supporting the company identity, primary offer, delivery route, and highest-priority questions above.
- DocumentUK Companies House — find-and-update.company-information.service.gov.uk / company / 05153270
- Documentemerchantpay — emerchantpay.com / privacy policy
- Documentemerchantpay — cdn.emerchantpay.com / uploads / EMP AGR Terms TT DR03 20250602
- Documentemerchantpay — emerchantpay.com / gaming
- Documentemerchantpay — emerchantpay.com / acquiring
- Documentemerchantpay — docs.emerchantpay.com / payments / payment integrations
- Documentemerchantpay — emerchantpay.com / legal
- Documentemerchantpay — cdn.emerchantpay.com / uploads / EMP MSA Тerms and conditions v03 20240501