emerchantpay
Product sources reviewedIdentity not reviewedemerchantpay 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.
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 different payment relationships by market. Its legal page identifies a UK electronic money institution, an EU partner institution, and US sponsor relationships, so the contracting provider, regulated permissions, settlement route, and available methods must be confirmed for each operator.
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
Direct 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
- ! Publicly fixed reserves, settlement schedules, or fees
- + The current gaming page expressly combines gaming merchant support with in-house acquiring and a first-party gateway.
- + Public integration documentation covers direct API and hosted payment flows as well as operational reporting and chargeback functions.
- ! The reviewed public pages do not publish gaming merchant acceptance criteria, reserves, settlement schedules, or fees.
- ! The applicable regulated provider, license responsibility, merchant-of-record role, data-controller role, and accepted gambling jurisdictions are not established at group level.
- emerchantpayVendorchecked 2026-07-11— The current gaming page explicitly offers gaming businesses an in-house acquiring and gateway product, card and alternative payment methods, payouts, fraud controls, and merchant-facing account and risk support.
- emerchantpayVendorchecked 2026-07-11— The current acquiring page states that emerchantpay acts as both a payment gateway and an acquirer and handles authorization, processing, settlement, and merchant risk.
- emerchantpayVendorchecked 2026-07-11— Current technical documentation describes server-to-server API, hosted Web Payment Form, and virtual terminal integrations, plus card payment, payout, reporting, and chargeback operations.
- emerchantpayVendorchecked 2026-07-11— The current legal page identifies the UK electronic money institution, an EU partner institution, and US sponsor relationships; the applicable provider and regulated role therefore depend on the merchant contract.
Gaming Local Payment Method Access
Multi ProductMixedAvailability: Standalone and Bundledemerchantpay gives approved gaming merchants a gateway route to local and alternative methods. Its current gaming page specifically names Pix, BLIK, and Bancontact for gaming deposits, while the technical catalog documents a wider set of bank, wallet, voucher, and cash-based methods.
This is mixed delivery rather than ownership of every listed method. The currently linked merchant agreement names Emerchantpay Ltd as the gateway and primary contact, but says payment services can be supplied by authorized PSPs, a direct PSP agreement may be required, and emerchantpay may instead act as referral agent or collecting agent. Each method needs its own provider, country, transaction-direction, gambling-approval, settlement, and data-role confirmation.
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
Server-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 according to 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
Hosted 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 published universal GDPR controller allocation
- ! Automatic payout support for deposit methods
- + The current gaming page names real local methods instead of relying only on an undifferentiated logo count.
- + The public merchant terms expose the gateway, PSP-contract, settlement, safeguarding, and payment-data boundaries unusually clearly.
- ! Pix, BLIK, and Bancontact are the methods explicitly named on the gaming page; the wider technical catalog is not evidence that every method accepts gambling transactions.
- ! 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.
- ! Deposit availability does not prove withdrawals, refunds, reversals, or merchant-initiated payouts for the same method.
- ! Hosted and server-to-server routes put payment data in different systems. The public sources do not replace a route-specific DPA or establish one universal controller allocation.
- emerchantpayVendorchecked 2026-07-11— The current gaming page explicitly offers gaming businesses an in-house acquiring and gateway product, card and alternative payment methods, payouts, fraud controls, and merchant-facing account and risk support.
- emerchantpayVendorchecked 2026-07-11— The current legal page identifies the UK electronic money institution, an EU partner institution, and US sponsor relationships; the applicable provider and regulated role therefore depend on the merchant contract.
- UK Companies HouseFilingchecked 2026-07-11— The official company register lists the UK operating company Emerchantpay Limited, company number 05153270, as active and records its latest confirmation statement in June 2026; it is not treated as the universal counterparty for the brand.
- emerchantpayVendorchecked 2026-07-13— The current method page identifies card, wallet, bank-transfer, real-time, and local payment-method access. Its catalog is explicitly subject to change and merchant activation, so the list is not treated as universal gaming coverage.
- emerchantpayVendorchecked 2026-07-13— Current documentation names Bancontact, BLIK, Boleto, Efecty, MyBank, Neosurf, OXXO, P24, Pago Facil, Paysafecard, PayU, PIX, Redpagos, and SEPA Direct Debit as local methods. The catalog does not prove gambling acceptance or payout support for every method.
- emerchantpayVendorchecked 2026-07-13— The merchant agreement currently linked from the legal page names Emerchantpay Ltd, company number 05153270 and FCA reference 900778. It defines the gateway, PSP-referral, optional collecting-agent, safeguarding, merchant-account, payment-page, transaction-data, and third-party-provider boundaries.
- emerchantpayVendorchecked 2026-07-13— Current integration documentation separates server-to-server use, where the merchant stores and processes customer data and carries the larger PCI scope, from the hosted Web Payment Form, where payment information is handled on emerchantpay servers.
- emerchantpayVendorchecked 2026-07-13— The current legal hub continues to link this safeguarding notice. It says client funds received by emerchantpay are segregated in safeguarding accounts and are not covered by the Financial Services Compensation Scheme.