iGaming Platform Payments & Cashier Comparison

Yes

Modular routing, 3DS/AVS/CV2 routing, rules, monitoring and reporting are supported; a universal smart-cascade guarantee is not included.

Yes

Rules, transaction management, reconciliation, and managed payment operations support automated processing; exact approval logic is operator-specific.

Partial

Depends on the selected instant-payment/open-banking provider and market.

PSP- and market-dependent

A universal payout-time SLA is not established.

Yes

Risk monitoring, disputes, fraud alerts, reconciliation, and managed fraud/chargeback services are available.

model-dependent

The operator brings the merchant relationship while EveryMatrix orchestrates payments; liability allocation depends on the operator, PSP/acquirer and contract.

Yes

Operators can combine, back up and switch between gateways, which is cascading and failover routing.

Yes

Partial

Whether a payout is instant depends on the chosen gateway and method.

PSP- and method-dependent; instant payout is possible but not universal

Playtech orchestrates the cashier and approval workflow; the chosen payment rail and operator risk controls determine actual arrival time.

Partial

Chargeback handling depends on the connected gateway rather than a dedicated Playtech tool.

operator

The operator holds the player and merchant relationship and normally carries chargeback risk under a platform and content supplier model.

Unresolved

Operators can configure connected PSPs; a native smart-routing or cascading engine across the platform is not established.

Yes

Operators can accept or cancel payout requests in the back office, and managed-services teams can run payout processing on their behalf.

Partial

Crypto and Pay N Play withdrawals can clear in minutes. Fiat payout speed depends on the chosen provider and is not guaranteed instant.

Rail-dependent: crypto and open banking can be minutes; fiat can take longer

SOFTSWISS supplies the cashier and integrations, while the operator, KYC checks and chosen PSP determine the actual withdrawal time.

Partial

The anti-fraud system has customizable settings; dedicated chargeback-management tooling is not established.

operator

Under turnkey and standalone the operator holds the license and is the merchant of record, so chargebacks sit with the operator.

Yes

Intelligent processing and configurable controls are available; routing depth remains unresolved.

Unresolved

Native end-to-end payout automation beyond integrated PSP capabilities remains unresolved.

Yes

Available through rails such as Zimpler where market, KYC and provider rules permit.

Provider-dependent; instant rails are available

Partial

The PAM can expose fraud and transaction controls; acquiring disputes remain operator/PSP processes.

operator

Payment providers and third-party services sit under operator contracts and responsibility.

Unresolved

Smart-routing and cascading specifications remain unresolved.

Unresolved

Managed payment operations are available; a native payout-automation workflow is not established.

Unresolved

Payout speed depends on PSP, KYC and risk review; instant payout is not a standard entitlement.

Unresolved

A cross-product payout benchmark remains unresolved.

Unresolved

A native chargeback workflow is not established.

Unresolved

Allocation depends on the operator, merchant, PSP/acquirer and managed-service contract.

Yes

Available through integrated PSP technology, particularly Praxis; it is not established as an Altenar-native routing engine.

Unresolved

A player-withdrawal automation workflow is not established.

Unresolved

Fast bet settlement and Pay N Play do not establish instant player withdrawals.

Unresolved

Player-withdrawal speed and B2B settlement benchmarks remain unresolved.

Partial

Fraud and chargeback capabilities depend on the selected PSP. An Altenar-native chargeback case-management product is not established.

Unresolved

Chargeback liability among operator, B2C licensee, Altenar and PSP is contract-specific.

Yes

Multi-provider integration supports configurable routing at PAM and cashier level; the exact rule engine remains unresolved.

Yes

The full-service PAM manages banking across the player lifecycle; final payout speed and controls depend on the operator and PSP.

Partial

The PAM can automate withdrawals, but actual instant payout availability depends on the selected PSP, payment rail, KYC status and market.

PSP-, KYC- and operator-policy dependent

Partial

Cashier and risk integrations can surface payment disputes, while acquiring-side chargeback execution remains with the PSP/operator.

operator

Payments and their chargebacks are operator-side.

Yes

Supported by OPS payment integrations.

Yes

Supported through OPS and connected PSPs.

Partial

Available where connected PSP and market support it.

PSP, KYC and operator-risk dependent

Partial

Supported through PSP/risk integrations.

operator

Operator/merchant unless contract assigns service responsibility.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Unresolved

Pariplay has no cashier or payment-orchestration product.

operator

Operator/merchant.

Yes

Paydrom supports multiple merchant accounts, transaction diversification, auto reconciliation and regional routing.

Yes

Partial

The Paydrom-integrated Aircash wallet supports instant deposits and withdrawals; Bitcashier also supports instant withdrawals. This is route-specific and not a universal payout SLA across all Paydrom providers.

Instant on supported Aircash and Bitcashier routes; provider-dependent otherwise

Paydrom has no platform-wide payout-time SLA. Speed remains dependent on the payment provider, operator approval, KYC and risk checks, currency and market.

Partial

Paydrom automates refunds and reversals and provides transaction case management and fraud controls. Dedicated chargeback representment, evidence-pack and card-scheme dispute workflows remain unresolved.

model-dependent

White label can bundle licence and payment processing, while turnkey is operator-licensed and Paydrom or PSP relationships are configured per project. Chargebacks, fraud losses, reserves and recovery rights require contract-specific allocation.

Yes

Features include BIN routing and rescue/alternative processing paths.

Yes

Operators can configure withdrawal rules and automated decisioning.

Partial

Speed depends on the chosen PSP, method, risk checks and operator workflow rather than a universal instant-payout promise.

Method- and risk-dependent; no platform-wide SLA

Yes

Risk/fraud managed services and cashier workflows support dispute handling; a separate chargeback module is not established.

Model-dependent

The licensed operator/merchant ordinarily bears chargeback exposure; allocation can shift under a managed payment structure.

Yes

Yes

Partial

Crypto can settle quickly; fiat speed depends on the selected PSP, banking rail, KYC state and operator approval policy.

Crypto near-real-time to tens of minutes; fiat method-dependent

Yes

operator

Yes

Yes

Partial

Instant payout support depends on the selected PSP, payment rail, market and operator approval workflow.

Real-time to several business days depending on PSP, KYC status and market

Yes

operator

Chargeback exposure sits with the operator in standard platform deals.

Yes

Configurable across integrated PSPs; exact smart-routing rules are private.

Yes

Supported through PAM workflows and managed operations.

Partial

PSP and market dependent, not guaranteed by Bragg.

Depends on operator risk review, method and PSP; no standard Bragg benchmark

Partial

Fraud and risk workflows support chargeback handling; exact tooling remains unresolved.

operator

Primarily operator/merchant/PSP risk, allocated contractually in managed-service deals.

Yes

Moneygrator can switch processors after a failed transaction.

Unresolved

Moneygrator routes deposits and withdrawals; automated payout approval, release and exception handling remain unresolved.

Partial

Instant withdrawals are available only where the selected rail supports them; actual speed remains subject to PSP, method, KYC and approval.

No universal SLA; instant processing only where the selected rail supports it

No

Fraud and transaction monitoring exist, but no dedicated chargeback-management workflow is demonstrated.

Unresolved

Chargeback liability among the operator, Slotegrator, licensed entity and PSP is contract-specific and unresolved.

Yes

Yes

Partial

Fast Shift supports instant payments and mass payouts, while cards, bank transfers, PSP reviews and operator approval can add delay.

Instant to rail-dependent after operator and compliance approval

There is no platform-wide percentile or guaranteed withdrawal time. Fast Shift can move eligible payments quickly; other rails depend on the PSP, bank, jurisdiction and review status.

Partial

Risk management uses a closed-loop method and automated deposit/withdrawal checks to cut fraud and chargebacks, not a dedicated dispute workflow.

provider

Likely sits with BetConstruct on white label where it holds the licence and payments, and with the operator on turnkey or standalone; the exact split is contract-specific.

Yes

The gateway supports automated card cascading: after a decline it retries the next configured provider without asking the player to re-enter details. One July 2026 deployment moved repeat-deposit acceptance from 60% to 95%; the result is implementation-specific and does not establish least-cost routing.

Yes

Partial. Withdrawals are processed in the back office and can use integrated rails; universal straight-through auto-approval remains unresolved.

Partial

Available on supported crypto and payment rails; not universal.

Rail-, operator-review- and KYC-dependent

Partial

Handled through PSPs; a native dispute suite is not established.

model-dependent

The licensed or merchant entity faces the PSP, while the operator contract may reallocate chargebacks, fraud and fines. The standard allocation is unresolved.

Yes

Smart routing, cascading, route A/B testing, and provider performance analytics.

Yes

Partial

Fast or instant withdrawal options are available where the payment method and market support them.

Method-dependent; automated withdrawals

No universal withdrawal-time guarantee.

Yes

model-dependent

The licensed merchant ordinarily faces chargebacks and fraud losses: this can be a Soft2Bet group entity in provider-licensed white label or the operator in turnkey. The agreement must allocate reserves, recoveries, fines and losses explicitly.

Yes

Wallet conversion is supported; settlement currencies and FX terms depend on the connected PSP/acquirer.

Yes

The platform supports real-time wallet conversion.

Unresolved

PCI DSS certificate XM4iOBPG9K81QRa expired on August 17, 2026. A current replacement certificate and the detailed assessed cashier-service scope are not established, so the selected implementation cannot be treated as covered without current scope evidence.

Yes

Trustly Pay N Play is supported; availability is market-dependent.

Yes

Trustly and other bank-transfer/open-banking integrations are available.

Yes

Yes

Yes

Yes

Optional via integrated open-banking/identity partners. Not a native Playtech-branded product and not available in every jurisdiction.

Partial

Account-to-account payments come through gateway partners rather than a native Playtech open banking product.

Yes

Multi-currency operation is supported through operator-selected PSP and CoinsPaid configurations; the exact settlement set is project-specific.

Yes

Multi-currency wallets are supported; on-the-fly FX conversion mechanics are unresolved.

Yes

PCI DSS certificate entity, level and cashier scope remain unresolved.

Yes

Delivered through Trustly Pay N Play, letting players deposit and start without registration.

Yes

Available through open-banking and A2A partners such as Trustly, Brite, and Yaspa rather than a SOFTSWISS-owned rail.

Yes

Settlement currencies are determined by operator and PSP contracts.

Yes

FX and settlement conversion depend on the selected PSP.

Yes

PCI DSS status lacks an exact service-provider level and Attestation of Compliance.

Yes

Available through external integrations such as Zimpler rather than as a native identity/payment rail.

Yes

Available through integrated bank-payment providers, not an owned banking product.

Unresolved

Multi-currency operation does not establish a cross-product settlement entitlement.

Unresolved

FX pricing source, spread and settlement workflow remain unresolved.

Unresolved

A current combined-division PCI AoC and its cashier scope remain unresolved.

Unresolved

No current named Pay N Play integration or market scope is established.

Unresolved

Market-specific banking integrations are available; the current open-banking roster and coverage remain unresolved.

Unresolved

Multi-currency payment acceptance does not establish operator settlement in multiple currencies.

Yes

The optional CoinsPaid integration provides built-in exchange across 20+ cryptocurrencies and 40+ fiat currencies. This is partner-enabled conversion, not a native Altenar treasury or settlement-FX service.

Unresolved

Integrated payment providers do not establish the PCI scope or compliance status of Altenar's cashier.

Yes

Altenar launched Pay N Play-style sportsbook widgets with two clients in 2020. Current availability depends on payment partner and jurisdiction.

Yes

Available through selected payment integrations; support is PSP- and market-dependent.

Yes

The global PAM/cashier stack supports multi-currency operator deployments; exact settlement currencies are provider- and contract-dependent.

Yes

Multi-currency account and payment flows require currency-aware handling, while conversion rates and settlement remain PSP/operator-configured.

Yes

Regulated card acceptance is handled through compliant payment integrations; a standalone PCI Attestation of Compliance for the PAM is not established.

Yes

Trustly Pay N Play is integrated in the inherited payment estate.

Yes

Trustly Pay by Bank, Brite, Sofort and other bank-payment integrations are available by country and operator deployment.

Yes

Yes

Supported by PSP and wallet configuration.

Unresolved

PSP- and deployment-dependent; a universal L&W PCI level is unresolved.

Yes

Available through eligible third-party integrations.

Partial

Available through eligible payment providers.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Unresolved

Pariplay has no cashier or payment-orchestration product.

Yes

Yes

Paydrom supports multi-currency processing, and the Bitcashier route offers real-time crypto conversion and fiat settlement; rates and spreads are contract-specific.

Yes

No

Digitain and Paydrom have no registration-free Trustly-style Pay-N-Play product.

Partial

Paydrom offers real-time and online bank-transfer routes including SPEI and Multibanco. A native PSD2/Open Banking consent flow, AIS/PIS API and complete bank-coverage matrix remain unresolved.

Yes

Multi-market fiat operations imply multi-currency PSP settlement; currencies and merchant arrangements are deployment-specific.

No

White Hat supports multi-market fiat payments; a proprietary real-time FX or in-wallet conversion engine is not established.

Yes

The cashier has PCI DSS SAQ A scope; this is scoped validation, not enterprise-wide PCI Level 1 certification.

No

A standard Pay-N-Play registration/payment product is not offered.

Partial

A2A or open-banking methods can be supplied by selected PSPs; a native or universally included open-banking product is not established.

Yes

Yes

Yes

No

Bank and local rails are available, but GR8 offers no named Pay N Play identity-plus-payment flow.

Partial

Open-banking-capable PSPs can sit behind the gateway, but GR8 does not market a proprietary open-banking product.

Yes

No

CoreX supports multiple currencies and settlement configurations, but no native real-time FX engine is established; conversion normally sits with the PSP, acquirer or operator treasury.

Yes

A compliant cashier can be assembled through PCI-scoped partners such as Nuvei and Paysafe; GiG itself is not established as a Level 1 service provider.

Yes

Trustly remains in the integration estate. Pay N Play is established for the earlier GiG Core platform; current CoreX activation remains market-specific.

Yes

Yes

Supported through operator/PSP arrangements.

Yes

Handled through PAM/PSP configuration; rates and settlement model are contract-specific.

Yes

Designed to work with PCI-compliant PSPs; the group-wide Bragg PCI level remains unresolved.

Yes

Possible through market-specific identity/payment integrations; not a named standard module.

Partial

Available where an integrated PSP provides it; no Bragg-owned open-banking rail.

Yes

Moneygrator supports 150+ currencies; exact settlement-currency terms depend on each PSP.

Unresolved

Moneygrator supports 150+ currencies, but conversion, rate locking and settlement-currency mechanics are unresolved.

Unresolved

Slotegrator and Moneygrator PCI DSS attestation is unresolved, so the cashier cannot be labelled PCI-compliant solely because connected PSPs may be.

No

Moneygrator does not present a Pay N Play product or named identity/open-banking partner.

No

A standard open-banking product and coverage matrix are not established for Moneygrator.

Yes

Yes

Yes

Regulated card flows use established PSP integrations, while BetConstruct's own PCI attestation and scope remain unresolved. Responsibility and tokenisation are PSP- and acquirer-specific.

Unresolved

No dedicated Trustly-style Pay-N-Play product was established.

Unresolved

Bank, SEPA and SWIFT rails are supported; a specific open-banking or account-to-account integration remains unresolved.

Yes

Yes

Partial through multicurrency ledger and PSPs.

Yes

Card scope is delegated to PCI-compliant PSPs. SoftGamings' own current PCI Attestation of Compliance remains unresolved.

Yes

Available through selected bank-payment partners. Trustly-style account-to-account flows can support Pay N Play where licensed; it is not established as a universal native feature.

Partial

Available through integrated PSPs.

Yes

Yes

Built-in currency conversion and multi-currency reporting.

Yes

Yes

A Pay N Play flow is offered in compatible markets.

Yes

No

MoneyMatrix Limited ceased licensed financial-institution activity in 2021 and its MFSA license ended on July 26, 2022. The current product is a gateway/orchestrator.

operator-brings

EveryMatrix connects PSPs and provides orchestration, risk, KYC, reconciliation, and payment consulting. It is not a currently licensed financial institution or universal merchant of record.

No

operator

The operator and its contracted PSP/acquirer hold/process player funds; EveryMatrix is not a B2C license holder.

Yes

Unresolved

EveryMatrix does not operate a provider-licensed white label or collect player funds for later payout to the operator.

Unresolved

EveryMatrix does not operate a provider-licensed white label or hold the operator's player proceeds.

No

The operator holds its own merchant and payment relationships. Playtech offers payment reconciliation and processing services on top of the operator's own setup, but does not provide the merchant account itself.

operator-brings

Playtech provides the payment platform and provider integrations, but the operator holds its own merchant accounts.

No

Operators handle their own banking. Playtech can layer payment processing and reconciliation services on top.

operator

Yes

Unresolved

Not a provider-to-operator white-label payout schedule: Playtech is a B2B supplier and average B2B invoice terms are 30 days. Player settlement remains with the operator and its payment stack.

Contractual net terms after reconciliation

No

SOFTSWISS integrates the operator's selected PSP relationships; it is not the merchant of record for a standard turnkey operator.

operator-brings

Operator must hold its own agreements with each payment provider.

No

Bank accounts and corporate banking remain the operator's responsibility.

operator

Operator / contracted PSP. The operator owns the player relationship and contracts payment providers; custody can sit with the operator or its PSP, not a universal SOFTSWISS player-funds account.

Yes

SOFTSWISS helps test payment accounts and integrate them through its payments hub.

Unresolved

The operator and its PSP control player funds and payouts; SOFTSWISS does not run a provider-licensed white-label remittance cycle.

Unresolved

Player-payout timing is controlled by the operator's review workflow and chosen PSP, not by a SOFTSWISS remittance cycle.

No

operator-brings

Operator brings; provider assists integration.

No

One 2023 customer agreement places player funds, merchant relationships and payment counterparties with the operator and PSPs.

operator

The established customer model leaves player funds and merchant/PSP relationships with the operator; exact structures remain deal-specific.

Yes

Unresolved

A platform-vendor payout schedule is not applicable; one 2023 customer agreement uses monthly invoicing.

Unresolved

Player payout speed is PSP- and operator-dependent. One 2023 customer agreement sets supplier invoices at net 30 days.

No

No for new white-label deals.

operator-brings

Operator-brings; integrations and payment operations can be supported.

No

No for new white-label deals.

operator

Operator in retained turnkey model.

Yes

Unresolved

The B2B settlement schedule is contract-specific across platform, content, sportsbook and managed-payment agreements.

Unresolved

Settlement-delay commitments are contract-specific; player payouts and supplier settlement are separate processes.

Unresolved

Payment gateways and partner infrastructure do not establish whether merchant accounts or acquiring relationships are included in Altenar's white-label package.

Unresolved

Payment integrations are available; merchant-underwriting assistance, acquiring approval and account ownership remain unresolved.

Unresolved

Bank-account provision and the standard white-label fund-flow arrangement remain unresolved.

Unresolved

The exact player-funds holder is partner- and contract-specific. It may be the licensed B2C partner, merchant entity or PSP; Altenar is not the universal fund holder.

Yes

Local support covers regional payment preferences, payment-method selection and technical localisation. It does not include merchant underwriting, acquiring approval, banking or ownership of payment accounts.

Unresolved

The B2B operator settlement schedule is contract-specific; player withdrawal timing and PSP settlement are different questions.

Unresolved

The Altenar B2B settlement-delay term is contract-specific; PSP settlement and player withdrawals are separate questions.

No

Payments/merchant setup are operator-side.

operator-brings

Yes

Banking is explicitly included in Kambi's optional full-service PAM; the operator still holds funds and contracts with merchant/PSP providers.

operator

Kambi never holds player funds; the operator does.

Yes

The PAM/integration team helps operators select and connect payment services, while acquiring contracts and merchant accounts remain with the operator.

monthly

Enterprise B2B revenue share and service fees are ordinarily reconciled on a monthly accounting cycle; exact invoicing terms are contractual.

Contractual net terms after monthly reconciliation

No

operator-brings

No

operator

Operator/merchant.

Yes

Integration support across 40+ PSPs.

Unresolved

Not applicable to OGS content revenue; operator/PSP controls player payouts.

Unresolved

Not applicable to OGS content revenue.

No

operator-brings

No

operator

Operator/merchant.

No

No core service.

Unresolved

Operator/PSP controls player payouts.

Unresolved

Operator/PSP controls player payouts.

model-dependent

Paydrom integrates payment methods and supports merchant-account routing. Digitain-owned merchant accounts are not included by default; the contracting merchant and settlement chain remain contract-specific.

provider-assists

Paydrom supplies payment-provider orchestration and integration support. Digitain-owned merchant accounts are not included by default; underwriting remains provider-, market- and operator-dependent.

No

Digitain offers payment orchestration and licensing guidance, not a provider-held corporate bank account or guaranteed bank-account opening service.

Unresolved

The white-label licensed entity, merchant account holder and PSP settlement chain remain contract-specific. Turnkey is operator-licensed and operator-held, but no universal white-label fund holder can be assigned.

Yes

Unresolved

The B2B operator settlement schedule is contract-specific.

Unresolved

No routine delayed operator settlements are established; the contractual schedule is deal-specific.

Model-dependent

White Hat controls the cashier and payment relationships in a provider-licensed full-service structure; merchant arrangements remain partner- and contract-specific.

provider-assists

White Hat provides the cashier and can integrate approved tools, while sportsbook, content and third-party supplier agreements generally remain with the customer.

Model-dependent

Payment orchestration and PSP access are available, but bank, acquirer, safeguarding and settlement structure remains contract-specific.

provider

In provider-licensed white label, White Hat Gaming Limited is the B2C licensee responsible for player liabilities; the safeguarding account or PSP structure remains unresolved. In operator-licensed PAM, the operator holds the liability.

Yes

White Hat optimises routing, payment limits, automated withdrawals and risk flows as part of managed payments.

Unresolved

Contract- and merchant-model dependent. Relevant mainly where White Hat is the licensed B2C entity or manages settlement.

Unresolved

A standard B2B settlement or white-label partner payout SLA is unresolved. Player-payment processing time is a different metric.

No

A payment gateway and PSP integrations are included; GR8 itself does not supply a universal merchant account.

provider-assists

GR8 integrates and optimizes PSPs; the operator or licensed entity signs the acquiring/merchant agreement.

No

Payment orchestration is software, not banking. The licensed white-label entity or operator still needs PSP/acquirer and settlement arrangements.

Unresolved

The Light White Label B2C entity, merchant account holder, PSP settlement chain, safeguarding terms and player-funds holder remain unresolved.

Yes

Unresolved

B2B settlement schedules are deal-specific; player withdrawal timing and supplier settlement are different questions.

Unresolved

Operator settlement-delay commitments are deal-specific.

No

The operator normally contracts and is approved by payment providers, with GiG assisting integration and operations.

provider-assists

CoreX integrates operator-selected PSPs and ServiceX can manage payments and reconciliation, but the operator remains the merchant and subject to PSP approval.

No

operator

A legacy B2C arrangement creates restricted player-money balances inside the group, but this is not the standard new-business model.

Yes

Unresolved

Standard GiG business is operator-licensed SaaS: GiG does not periodically remit player proceeds to the operator. The residual SkyCity white-label model is exceptional, and its exact settlement schedule remains unresolved.

Unresolved

Player withdrawals and operator funds are controlled by the operator and its PSPs in standard deployments; GiG has no remittance step in this model.

No

No standard Bragg merchant account.

operator-brings

Operator-arranged; Bragg integrates PSPs and can manage payment operations.

No

operator

Operator and its payment/merchant providers.

Yes

Yes through PAM implementation and managed operations.

Unresolved

Supplier invoicing and settlement are contract-specific.

Contract-specific; standard unresolved

Yes

White-label marketing includes merchant/banking setup, but the account holder and PSP contracts are private.

Provider-assists

Moneygrator helps select and connect PSPs, while the client signs directly and completes due diligence with each provider.

Yes

White-label banking and payment support are included; exact account ownership is contract-specific and unresolved.

Unresolved

The white-label licensed entity, merchant-account holder, safeguarding arrangement and settlement chain are unresolved. Slotegrator cannot be assumed to hold funds universally.

Yes

Unresolved

The operator settlement schedule is contract-specific and may differ among content, white-label and payment arrangements.

Unresolved

Settlement-delay and withdrawal-delay commitments are contract-specific and unresolved.

Yes

Part of the provider-managed white-label financial operation, subject to PSP/acquirer approval and market rules.

provider-assists

Yes

White label includes provider-managed financial operations and payment gateways; it does not mean the operator receives its own unrestricted bank account.

Unresolved

The fund holder varies across white-label markets. The licensed affiliated operator, merchant entity and PSP settlement chain must be named in the contract; turnkey operators maintain their own licence and wallet.

Yes

Turnkey includes multiple local payment rails and payment partners; merchant approval and acquiring terms still come from the payment provider or bank.

Unresolved

The white-label settlement schedule is contract-specific and unresolved.

Unresolved

Operator settlement-delay performance remains unresolved.

Yes

Yes for white label, subject to PSP and project approval.

provider-assists

Yes

Payment and banking setup assistance; account ownership varies.

provider

The provider entity and PSPs hold funds in white label; the operator and PSPs do so in turnkey. SoftGamings supplies white-label financial infrastructure. Crypto wallets are non-custodial to SoftGamings, but fiat settlement and reserve arrangements remain contract- and PSP-specific.

Yes

Unresolved

PSP- and contract-specific.

Settlement timetable contract-specific

Allegations of withheld or delayed balances are not adjudicated, but settlement timing and reserve release need explicit contract terms.

model-dependent

A provider-licensed white label can bundle a provider-side merchant and acquiring structure, while turnkey operators normally undergo their own PSP and acquirer approval. Soft2Bet does not promise one universal merchant account across markets.

provider-assists

Soft2Bet integrates PSPs, local methods, routing, sandbox testing and operational monitoring. The operator or licensed white-label entity still faces underwriting and signs the applicable merchant/acquiring arrangement.

model-dependent

Payment orchestration and PSP onboarding support are included. Provider-licensed white label can use group-side settlement arrangements, while turnkey operators retain their own banking responsibilities; a guaranteed corporate bank-account service is not included.

Unresolved

Fund custody depends on the exact B2C licensee, merchant, safeguarding institution, PSP and contract. The white-label label alone does not establish physical or legal custody.

Yes

Unresolved

Contract-specific.

Unresolved

Contract-specific.