Lightning & SDK Integration

Payment Infrastructure
Inside the Game Engine

From game-event triggers to programmable micro-payments, wallet orchestration and Lightning settlement

TRUSTED BY INNOVATIVE STUDIOS & PLATFORMS

TAPNATION

AZUR GAMES

PIXEL UNITED

FARAWAY

MYTHICAL

BITKRAFT

Game Engine Payment Architecture

LATEST UPDATE

As of 20 August 2026

Content reviewed and updated weekly.

Game Engine Payment Architecture

Our SDKs and APIs connect game events to programmable payments using the Lightning Network. Build reward systems, in-game purchases, creator payouts, and tournament prizes with instant settlement.

GAME ENGINE Unity / Unreal / Web

→

EVENT TRIGGER Action / Achievement

→

PAYMENT ORCH. Rules • Routing

→

LIGHTNING RAILS BOLT11 / BOLT12

→

RECIPIENTS Players / Creators

Unity & Unreal Integration Section

Unity

Unity Integration

Official Unity SDK for embedded payments
Reward ads to satoshis
In-app purchases via Lightning
Cross-platform (iOS, Android, PC, WebGL)
C# APIs with full documentation

C# Reward Example 📋 ↗

using Zbd.Sdk;

public class RewardManager : MonoBehaviour
{
public void OnQuestCompleted()
{
var reward = new PaymentRequest
{
AmountSats = 250,
Memo = "Quest Completed",
CallbackUrl = "https://yourgame.com/webhook"
};
ZbdPayment.Send(reward);
}
}

UNREAL
ENGINE

Unreal Engine Integration

Unreal Engine plugin for Blueprints & C++
Micro-payments and reward distribution
Marketplace & entitlement support
Cross-platform (PC, Console, Mobile)
Dedicated developer support

Server-to-Server API & Lifecycle Section

Server-to-Server API

RESTful APIs for secure, scalable backend integration and custom payment flows.

Create payments & invoices
Verify payments
Payouts & mass payments
Wallet & balance management
Compliance & KYC status

POST /v1/payments

{

"amount": 500,

"currency": "sats",

"memo": "Tournament entry",

"metadata": {

"user_id": "12345",

"event_id": "abcde"

}

Lightning Payment Lifecycle

From invoice creation to final settlement in seconds.

Invoice Created

→

Player Pays

→

Payment Settles

→

Webhook Notifies

BOLT11 vs BOLT12 Section

BOLT11 vs BOLT12

Both standards are useful. Support varies across Lightning implementations.

BOLT11 (Invoices)

Widely supported
Single-use invoices
Best for one-time payments
Broad wallet compatibility

BOLT12 (Offers)

Reusable & extensible offers
Enables recurring / programmatic payments
Support still uneven across stacks
Core Lightning, Eclair, LDK: Yes
LND: No native support (as of Aug 2026)

⚡ BOLT12 introduces reusable Lightning offers and enables useful recurring or programmatic payment patterns, but implementation support remains uneven across Lightning stacks.

Implementation	BOLT11	BOLT12
Core Lightning	Yes	Yes
Eclair	Yes	Yes
LDK	Yes	Yes
LND	Yes	No
c-lightning (CLN)	Yes	Yes

Ready to Integrate Banner Section