EST. 2012 CODEGO GROUP LTD · MALTA BANKING AS A SERVICE EU IBAN · 6 COUNTRIES SEPA · SEPA INSTANT · SWIFT PCI DSS CERTIFIED 2025 API FIRST · WEBHOOKS 79 COUNTRIES DEPOSITS MULTI-CURRENCY · EUR · GBP · USD $1.1BN PROCESSED 2025 EST. 2012 CODEGO GROUP LTD · MALTA BANKING AS A SERVICE EU IBAN · 6 COUNTRIES SEPA · SEPA INSTANT · SWIFT PCI DSS CERTIFIED 2025 API FIRST · WEBHOOKS 79 COUNTRIES DEPOSITS MULTI-CURRENCY · EUR · GBP · USD $1.1BN PROCESSED 2025
```html
Codego · Industry · est. 2012 Gaming & Creator Economy · Vol. XII · Issue 04/2026 ● 12 countries · Malta HQ
IND

Banking infrastructure for gaming, esports and the creator economy.
From prize-pool payouts to branded cards — financial plumbing built for platforms that move fast.

Gaming platforms, esports tournament operators and creator-economy apps sit at an awkward intersection: they move money at consumer-internet velocity but face financial-services compliance requirements that most legacy banks were never designed to handle. Instant prize payouts across 18 currencies, branded prepaid cards for streamers, MCC-level spend controls that distinguish gambling from gaming, and KYC flows rigorous enough for regulated prize pools — none of this comes standard from a corporate bank account. Codego's Banking-as-a-Service stack was built for exactly this operating model: a 15-day end-to-end launch, native crypto support, dual Visa and Mastercard BIN sponsorship, and EU IBAN issuance with SEPA Instant settlement, all configurable through a self-service portal without bespoke engineering contracts.

01
The industry challenge

The industry challenge

Gaming and esports platforms occupy a regulatory grey zone that is, paradoxically, becoming more clearly defined every year — and more demanding as a result. In the EU, prize-pool tournaments that cross the threshold into "games of chance" fall under national gambling-licence frameworks; those that remain skill-based sit under a patchwork of digital-goods and consumer-protection rules. The practical consequence is that a single platform may need to handle payouts under MCC 7993 (video-game arcades, skill-based gaming), MCC 7995 (gambling and lotteries) and MCC 5816 (digital goods) — sometimes within the same session, depending on the product line. Getting those merchant category codes wrong is not a minor administrative error: it triggers card-scheme chargebacks, acquiring-bank termination clauses and, in regulated markets, potential licence jeopardy.

Layered on top is the velocity problem. Competitive gaming operates on tournament schedules — events conclude and players expect prize money within hours, not the three-to-five business days that a standard SEPA Credit Transfer would require. Multi-currency exposure compounds this: a mid-sized esports operator running a global ladder may owe prize money denominated in EUR, USD, GBP, BRL, PLN, TRY and a dozen other currencies simultaneously. Hedging, conversion and settlement infrastructure that can handle this in near-real time is simply not available off the shelf from most European banks.

The creator-economy dimension introduces further complexity. Streamers and content creators monetise through subscription revenue shares, brand-deal disbursements, tips and micro-donations — often in amounts below €1. The cost of a standard bank transfer frequently exceeds the value of the payment itself. Platforms that route these micro-revenues through conventional bank rails either absorb prohibitive fees or push the cost onto creators, both of which are commercially damaging. At the same time, regulators in Germany, France and the Netherlands have tightened requirements around e-money wallets held on behalf of third parties, meaning platforms cannot simply sit on creator balances without an appropriate electronic-money framework.

Responsible-gaming obligations add a further layer. Operators in licensed jurisdictions must demonstrate that their payment infrastructure actively supports deposit limits, self-exclusion enforcement and age-verification at the point of financial onboarding — not merely as a post-hoc compliance box, but as a structurally embedded control. Legacy bank integrations almost never provide the API surface required to implement these controls programmatically. The result is that most platforms bolt on compliance tooling at the application layer, creating fragile dependencies and audit exposure.

Finally, the rise of crypto-native gaming — play-to-earn models, NFT-based item economies, stablecoin prize pools — has created demand for payment infrastructure that treats crypto as a first-class settlement rail rather than a speculative add-on. Platforms that want to accept USDC prize entries and convert them to EUR for EU-resident winners need a provider whose compliance and conversion infrastructure spans both fiat and digital assets natively.

02
What banking infrastructure must deliver

What banking infrastructure must deliver

Instant, multi-currency prize and revenue payouts

Tournament prizes and creator revenue shares must land in recipients' accounts within minutes of an event concluding, not days. Infrastructure must support SEPA Instant for EUR-denominated payouts (settlement in under ten seconds), SWIFT for international corridors, and internal ledger transfers for platform-wallet-to-card moves. Multi-currency ledgering across at minimum EUR, GBP, USD, PLN, CZK and major LatAm currencies is a baseline requirement, not a premium feature. Conversion should occur at transparent, API-queryable rates with no hidden spread loaded into the transaction fee.

MCC-level spend controls and merchant category enforcement

A gaming platform issuing prepaid cards to players or creators must be able to configure precisely which merchant categories those cards can transact at — and, critically, which they cannot. The distinction between MCC 7993 (skill gaming), 7995 (gambling) and 5816 (digital goods) is legally material in most EU jurisdictions. Card-issuing infrastructure must expose MCC-level allow/block controls at the programme level and, ideally, at the individual card level, so that a responsible-gaming product can structurally prevent spend at gambling MCCs without relying solely on application-layer controls that a determined user could circumvent.

Branded white-label cards on Visa and Mastercard

For creator platforms and esports organisations, the payment card is a brand asset as much as a financial instrument. White-label card programmes on both Visa and Mastercard — with full BIN sponsorship and the ability to carry platform branding, custom card art and co-branded scheme marks — allow platforms to extend their identity into the wallet. Virtual cards must be available on day one of the programme (for immediate digital wallet provisioning), with physical cards following within a standard production cycle. Apple Pay and Google Pay provisioning within 24 hours of virtual card issuance is now table-stakes for a Gen-Z user base.

KYC and age-verification integrated into the financial onboarding flow

Prize-pool payouts above regulatory thresholds require verified identity, and age-verification (over-18 confirmation) is a hard requirement in every licensed gaming jurisdiction. The financial onboarding layer must support tiered KYC: a lightweight identity check for micro-transaction wallets, and a full document-plus-liveness flow for accounts that will receive prize disbursements or hold significant balances. Critically, this KYC must be embedded within the financial infrastructure layer — not bolted on as a third-party widget — so that the verification status is structurally linked to the account's transaction permissions rather than stored as a metadata flag that can be bypassed.

Micro-payment architecture and low-cost ledger transfers

Creator tip flows, in-game item purchases and subscription micro-shares routinely fall below €1. Routing these through standard card-processing or bank-transfer rails makes them economically unviable. The correct architecture uses an internal ledger — an e-money wallet layer that aggregates micro-credits within the platform's own account structure — with batched or triggered settlement to external bank accounts when balances cross a meaningful threshold. This requires an e-money framework, proper float segregation and a ledger API that the platform can post to in real time without incurring a per-transaction external fee on every micro-credit.

Native crypto and stablecoin rails for crypto-gaming

Play-to-earn, NFT economies and stablecoin prize pools are no longer niche. Infrastructure that treats crypto as a bolt-on — converting to fiat at the perimeter and discarding the digital-asset context — cannot serve these models. First-class crypto infrastructure means stablecoin-funded wallets (USDC, USDT), on-the-fly conversion to fiat at the point of card spend or SEPA payout, and white-label crypto card programmes that allow a player to spend in-game earnings at any physical or online merchant without a manual withdrawal step. Regulatory compliance — VASP registration, travel-rule handling — must be built into the infrastructure, not left to the platform operator to resolve independently.

03
How Codego's stack maps to gaming and creator platforms

How Codego's stack maps to gaming and creator platforms

Codego's architecture maps directly onto the operating requirements of gaming, esports and creator-economy platforms — not by approximation, but because the infrastructure was designed around exactly the kind of multi-party, high-velocity, compliance-sensitive money movement these businesses require.

The foundation is Banking-as-a-Service: a single API integration that exposes account issuance, ledger management, payment initiation and card controls under one contract. For a gaming platform, this means a single compliance relationship — structured under Codego's NBB electronic-money distribution licence, with Codego Europe SIA in the EMI licensing process and pan-EU passporting — rather than separate agreements with an acquiring bank, a card processor, an IBAN provider and a crypto desk. The operational and legal overhead reduction is substantial.

For prize payouts, Codego's native EU IBAN issuance across six countries with full SEPA, SEPA Instant and SWIFT capability means that a tournament operator can disburse prize money to EU-resident winners within seconds of a match concluding, and to international recipients via SWIFT within the same operational workflow. Multi-currency wallet architecture supports holding and disbursing in 18+ currencies, with no requirement to pre-fund separate currency accounts — conversion is handled at the ledger layer.

For branded card programmes, Codego holds BIN sponsorship on both Visa and Mastercard — a genuinely rare capability that allows platforms to choose scheme by market (Mastercard-dominant in parts of Central and Eastern Europe; Visa preferred elsewhere) rather than being locked into one network. The white-label card programme supports full custom branding, virtual card issuance on day one of launch, and physical card production within the standard 15-day onboarding timeline. Apple Pay and Google Pay are provisioned within 24 hours of virtual card activation — critical for platforms whose users live inside mobile ecosystems.

MCC controls are configured through Codego's self-service portal at the programme level, allowing a gaming operator to define precisely which merchant categories their cards can transact at. A responsible-gaming product can structurally block MCC 7995 at the card-programme level; a creator-economy card can be restricted to MCC 5816 and adjacent digital-goods categories for a curated spend experience. The card issuing platform exposes these controls via API, so programmatic, real-time card-level overrides — for example, temporarily blocking all spend for a self-excluded player — can be implemented without a support ticket.

For crypto-native gaming platforms, Codego's white-label crypto infrastructure treats stablecoin and crypto-funded cards as a primary product rather than a compatibility shim. Players can hold USDC prize winnings in a Codego-issued wallet, spend via a Visa or Mastercard card at any physical or online merchant with on-the-fly conversion, and receive SEPA payouts from the same balance. VASP-compliant transaction monitoring and travel-rule handling are built into the infrastructure layer.

The core banking layer provides the ledger infrastructure required for micro-payment aggregation — creator tip batching, in-game micro-purchase crediting — with internal transfers that do not incur external payment-network fees. Combined with the white-label bank product, platforms can offer creators and players a fully branded digital banking experience — named accounts, card, wallet, transaction history — under their own brand, without holding an EMI licence themselves. The time-to-launch benchmark of 15 days end-to-end (virtual cards available day one) means a platform can move from API integration to live user onboarding faster than most legal review cycles.

04
Real-world architecture

Real-world architecture

Case A: Esports tournament operator, 18-currency prize-pool disbursements. A European esports platform running global ladder competitions across PC and mobile titles faced a structural problem: prize pools were funded in EUR and USD by sponsors, but winners were distributed across 34 countries with local-currency payout expectations. Their legacy approach — manual bank transfers from a corporate account — introduced three-to-seven-day delays, high FX conversion costs loaded by their corporate bank, and a KYC bottleneck where winners above €600 required document verification that the platform had no infrastructure to collect.

The platform integrated Codego's BaaS layer to issue individual e-money wallets to registered tournament participants at sign-up, with tiered KYC embedded in the onboarding flow: a lightweight check for players entering free brackets, and a full document-plus-liveness verification for anyone eligible for cash prizes above the regulatory threshold. Prize disbursements are now processed as internal ledger transfers — from the platform's float account to the individual player wallet — in real time at match conclusion, with SEPA Instant settlement to EU-resident winners' external bank accounts within seconds, and SWIFT routing for non-EU corridors. The platform operates prize accounts in EUR, USD, GBP, PLN, CZK, SEK, NOK and nine additional currencies, with conversion handled at the Codego ledger layer at transparent interbank rates.

Case B: Creator-economy app, branded debit card programme. A mid-sized streaming and content platform wanted to offer its top-tier creators a branded debit card — a tangible benefit that would also serve as a retention mechanism for high-value creators being courted by competitors. The requirement was a Mastercard-network card carrying the platform's brand and colour scheme, with spend restricted to a curated set of creator-relevant MCCs (digital goods, software subscriptions, professional equipment, advertising platforms) and a hard block on gambling MCCs to satisfy the platform's advertiser commitments.

Using Codego's white-label card programme, the platform configured a Mastercard BIN programme with custom card art, MCC-level allow-list controls via the self-service portal, and virtual card issuance on the day the programme launched. Creator revenue shares — calculated daily from the platform's subscription and ad revenue data — are posted to individual creator wallets via the ledger API, net of the platform's revenue-share margin, and are immediately spendable on the card. Physical cards were in creators' hands within 18 days of the programme kick-off. Apple Pay provisioning was live within 24 hours of virtual card activation, which the platform surfaced as the primary onboarding step in its creator dashboard.

05
Frequently asked questions

Frequently asked questions

Does Codego support MCC-level controls for gaming vs gambling vs digital goods?

Yes. Codego's card issuing platform exposes merchant category code controls at both the programme level and the individual card level via API and the self-service portal. You can configure allow-lists, block-lists and conditional rules that distinguish MCC 7993 (skill gaming), MCC 7995 (gambling and betting), MCC 9406 (government-licensed lotteries) and MCC 5816 (digital goods) — and apply different rules to different card tiers within the same programme. Changes can be applied programmatically in real time, which is essential for responsible-gaming self-exclusion enforcement.

How quickly can prize-pool payouts reach winners across different countries?

For EU-resident winners with euro-denominated payouts, SEPA Instant delivers to external bank accounts in under ten seconds, 24/7/365. For other EU currencies (PLN, CZK, SEK, etc.) and non-EU corridors, Codego routes via SEPA Credit Transfer or SWIFT as appropriate. Internal ledger transfers — from platform float to individual player wallet — are real-time regardless of geography. The practical outcome for an esports operator is that EU prize payouts can be in a winner's bank account before the post-match ceremony is over.

What KYC is required for prize-pool disbursements to players?

Codego's onboarding supports tiered KYC aligned to transaction limits set by the applicable EMI framework. Low-value wallets (for micro-transactions and small prize tiers) can be opened with a lightweight identity check. Accounts eligible for prize disbursements above regulatory thresholds require full document verification plus liveness check, which is integrated into the financial onboarding API — not a separate third-party widget. Age verification (over-18 confirmation) is a configurable hard gate that can be applied to any prize-eligible account tier, with the verification status structurally linked to transaction permissions.

Can Codego support crypto-funded cards for play-to-earn and NFT gaming platforms?

Yes. Codego's white-label crypto infrastructure supports stablecoin-funded (USDC, USDT) and crypto-funded wallets with on-the-fly conversion to fiat at the point of card spend or SEPA payout. Players can hold in-game earnings in a stablecoin wallet and spend at any Visa or Mastercard merchant without a manual withdrawal step. VASP-compliant transaction monitoring and travel-rule handling are built into the infrastructure. For crypto-gaming platforms operating under the EU's MiCA framework, Codego's compliance architecture is structured to support the relevant VASP obligations.

How does the micro-payment ledger work for creator tip flows and in-game purchases?

Codego's core banking layer provides an internal ledger on which platforms can post micro-credits — creator tips, in-game item revenue shares, subscription micro-splits — as real-time ledger entries without incurring a per-transaction external payment-network fee. The platform controls the aggregation logic: balances accumulate on the internal ledger and trigger external settlement (via SEPA or SEPA Instant to the creator's bank account) when a configurable threshold is crossed. This makes sub-€1 creator payments economically viable without the platform absorbing bank-transfer costs on every transaction.

What is the realistic timeline for a gaming platform to launch a branded card programme?

Codego's end-to-end onboarding benchmark is 15 days: virtual cards are available on day one of programme configuration (and can be provisioned to Apple Pay and Google Pay within 24 hours of activation), with physical cards completing standard production and personalisation cycles within the 15-day window. Programme configuration — MCC controls, card art, spend limits, KYC tiers — is handled through the self-service portal without bespoke engineering engagement on Codego's side, which is the primary driver of the compressed timeline. The practical constraint is usually the platform's own legal review and card-art sign-off, not infrastructure readiness. See card issuing glossary for scheme-specific programme requirements.

```