BroSettlement · Security Before Scale

Wallet infrastructure
before predictable volume

Launch crypto deposits, withdrawals, player wallets, ledger records, transaction signing, network broadcast, and WebSocket events through one API. Built for iGaming and crypto-native teams that need serious wallet operations before enterprise volume.

Book a DemoGet Sandbox Access
USDT / USDC readySelf-hosted Co-SignerEd25519 Auth10 chains
The Problem

Security should not be unlocked only after volume

Early teams are often asked to prove monthly volume before they get fair wallet security, pricing, or onboarding attention. That is backwards: they need the infrastructure to create the volume in the first place.

01

The startup honesty tax

If a founder says the truth — we are launching and do not know volume yet — the market often answers with worse terms, slow sales cycles, or a request to come back later.

02

Weak controls before first traction

The riskiest moment to use fragile wallet operations is exactly when deposits, withdrawals, and player balances are being tested for the first time.

03

Checkout is not infrastructure

A gateway can help accept crypto. BroSettlement is for teams that need control over wallets, balances, withdrawals, reconciliation, and settlement events.

Platform

Core stack.
One API.

01

Embedded Wallets

DKG-generated MPC wallet per player, merchant, user, or account. Create deposit addresses at API speed.

02

10-chain broadcast

Broadcast signed transactions across the stablecoin-heavy networks your product actually uses: TRON, ETH, BNB, BTC, SOL, and more.

03

Immutable Ledger

Append-only journal as the operating record for reconciliation, audit, and customer balances.

04

Open Co-Signer

Self-hosted signing service in your environment. You hold a key share and signing policy.

05

API Security

Ed25519 signed requests, IP allowlist, nonce replay protection, and scoped org access before signing or ledger flows.

06

10-chain broadcast coverage

ETH · BTC · SOL · BNB · TRON · TON · POL · OPT + more

USDT/USDC first. Additional networks expand around the client production flow.

Security & Compliance

No party can
move funds alone.

Platform share + partner share combine only inside an approved signing session. The full private key is never reconstructed.

  • DKG + MPC 2-of-3 threshold signing
    Keys are generated in parts; no full private key exists in one place
  • Ed25519 API authentication
    IP whitelisting + replay protection + key rotation
  • RBAC with 5 permission levels
    Owner, admin, operator, reader, service
  • Nonce replay protection
    Every request is unique — replay attacks blocked
  • IP allowlist per API key
    Restrict access to your infrastructure only
MPC-CMP Signing Model
Wallet (2/3 threshold)
Partner Co-Signer
BroSettlement Signer
Recovery Share
K1 + K2 sign the normal path; K3 stays offline for recovery
Co-Signer

You run the Co-Signer.
BroLabel can't sign without you.

The Co-Signer runs in your environment, holds the partner key share, and asks your policy callback before signing. BroSettlement coordinates K2 without ever holding full custody.

vs. competitors
Custodial PSPs or platform-owned rails become a strategic dependency.
BroSettlement gives you API-first MPC, self-hosted Co-Signer, ledger, and WebSocket events under your product layer.
Open-source
Full source on GitHub — audit every line before you deploy
Docker-deployable
Runs anywhere: your cloud, on-prem, private VPC
Client-controlled
You own and operate Share B — no BroLabel dependency at signing time
Policy enforcement
Co-Signer enforces your spending limits, allowed chains, and confirmation thresholds
Architecture

From your backend
to blockchain broadcast.
Through a controlled sign path.

Your backend creates wallets, deposit addresses, and transaction intents. BroSettlement moves the intent through API auth, ledger, MPC signing, blockchain gateway, and event delivery.

Ed25519 signed requests, IP allowlist, nonce replay protection
Ledger intent is created before the signing flow
WebSocket lifecycle: created, signed, broadcast, confirmed
Transaction Flow

How a signed transaction moves

The flow keeps API, policy approval, signing, ledger, and network broadcast separate while still working as one synchronous operating path.

API GatewayMPC SignerImmutable LedgerBlockchain Gateway
Partner Environment
1
API Client creates an intent

Your backend sends a signed API request for a wallet or transaction intent.

POST /v1/transactions
2
Policy callback approves signing

The Partner Co-Signer asks your Callback Handler whether this operation is allowed.

tx_sign_request
BroSettlement Gateways
API Gateway
Ed25519IP allowlistNonce
MPC Signer
K1 + K2 create a network-valid signature without reconstructing the private key.
K1 + K2
Core Services
Immutable Ledger
Creates the operating record for deposits, withdrawals, transfers, reconciliation, and audit.
Blockchain Gateway
Blockchain Gateway broadcasts the transaction, the ledger updates, and WebSocket delivers lifecycle events.
WS /v1/events
Use Cases

Built for embedded wallet products

iGaming & Betting

Per-player TRON/USDT wallets without a custodial PSP

  • TRC20 USDT deposit address for every player account
  • deposit.observed and deposit.confirmed events
  • Operator policy before payout signing
  • Append-only ledger for player balance reconciliation
Request a Demo
Primary flow
TRON / USDT
Wallet model
Per player
Dependency
No PSP
Vertical Use Case

iGaming player wallet flow

A betting operator needs USDT deposits and payouts without handing wallet logic to a closed payment provider.

01
Situation
The operator wants a dedicated deposit address for each player, early visibility into incoming funds, and control over when a player balance is credited.
02
BroSettlement role
BroSettlement creates embedded wallets through API, tracks network events, routes payouts through Co-Signer, and records every money movement in the operating ledger.
03
Operational result
The product team keeps its player account UX, bonus rules, and payout policy, while finance gets a clear reconciliation trail across deposits, balances, and withdrawals.
1

Create player wallet

API returns a TRON/TRC20 USDT deposit address for the player account.

2

Observe deposits

Events tell your backend when funds are observed and confirmed on-chain.

3

Credit by policy

The operator decides when to credit the player balance.

4

Approve payout

Co-Signer checks operator policy before MPC signing.

Lifecycle events
deposit.observeddeposit.confirmedwithdrawal.signedwithdrawal.confirmed
Fast deposit UX
Show incoming funds before final confirmation, then credit by policy.
Clean reconciliation
Ledger connects player balances to on-chain movements.
Controlled payouts
Operator policy and Co-Signer approval happen before signing.
Independent stack
No custodial PSP dependency for wallet infrastructure.
Read the full case study
Developer Experience

Three integration surfaces
for production flows.

  • Public API: POST /v1/wallets, POST /v1/transactions, GET /v1/ledger
  • Co-Signer: policy callback, tx_sign_request, partial signature
  • WebSocket Events: deposits, withdrawals, MPC sessions, API keys
  • Security perimeter: Ed25519 signed requests, IP allowlist, nonce replay protection
Get Sandbox AccessOpen Docs
brolabel-api.sh
# Create a wallet
POST /v1/wallets
Authorization: Bearer $API_KEY

{
  "blockchain": "ETH",
  "label": "user_wallet_001"
}

# Subscribe to events
WS wss://api.brolabel.io/events
→ { "event": "deposit.confirmed",
    "amount": "0.5", "chain": "ETH" }
Comparison

Built for teams that need control

BroSettlement position

Embedded MPC wallet infrastructure for stablecoins and iGaming.

For teams evaluating Fireblocks, Dfns, Utila, Blockdaemon, or Safeheron, BroSettlement provides focused DKG/MPC wallet infrastructure and goes deeper on stablecoin flows: 10-chain broadcast, deposit monitoring, ledger reconciliation, and WebSocket events.

DKG + Noncustodial MPCEmbedded WalletsSelf-hosted Co-Signer10-chain BroadcastLedger + WebSocket

Fireblocks

Deep enterprise custody platform. BroSettlement is narrower and faster for embedded stablecoin wallets, iGaming deposits, payouts, ledger, and WebSocket flows.

Enterprise custodyBroad platform

Dfns / Utila

Strong wallet infrastructure and policy tooling. BroSettlement adds a vertical stablecoin stack: DKG/MPC, 10-chain broadcast, embedded wallet provisioning, ledger, and events.

Wallet infraPolicy controls

Blockdaemon / Safeheron

Institutional key management and custody infrastructure. BroSettlement targets teams that need the MPC layer plus stablecoin wallet operations, ledger records, and events.

Institutional MPCCustody infra

BroSettlement

API-first Embedded Wallets with DKG, noncustodial MPC, Co-Signer, 10-chain broadcast, WebSocket events, and ledger as the operating record.

StablecoinsiGaming
Pricing

Start free. Scale with transparent SaaS pricing.

Free

$0
Testnet only
10 wallets
1 user · 1 API key
Full API access

Starter

$299/mo
$1M volume · 100 wallets
5 chains · Mainnet
3 API keys · 5 users
Community support
0.20% overage
Most Popular

Business

$999/mo
$15M volume · 5,000 wallets
10 chains · Mainnet
10 API keys · 25 users
Email 48h support
99.5% SLA
0.12% overage

Scale

$3,499/mo
$30M volume · 15,000 wallets
Expanded chain set
50 API keys · 100 users
Priority 8h support
99.9% SLA
0.07% overage

Enterprise

Custom
Unlimited everything
Custom chain coverage
Unlimited wallets & users
Dedicated 24/7
Custom SLA review
Custom overage
Onboarding

From sandbox to production in three steps

Step 1

Sandbox today

Full API access, WebSocket events, and test wallets with no credit card.

Step 2

Integrate in days

POST /v1/wallets, transaction intents, event subscription, and auto-populated ledger.

Step 3

Go live in a week

Co-Signer deployed, production keys issued, first real transaction.

The BroLabel Ecosystem

BROsettlement
powers everything.

BROwallet and BROcard can remain products on top of BroSettlement, while this page now sells Embedded Wallet infrastructure for B2B builders that need DKG, MPC signing, chain broadcast, ledger, and WebSocket events.

BroSettlement as the DKG/MPC and Embedded Wallet infrastructure
BROwallet and BROcard as product layers on top
Or the client product layer built directly on the BroSettlement API
Operator proof

What teams keep control of

Operational outcomes from wallet, ledger, card, and settlement integrations.

Player wallets · payout policy · ledger
“We needed player deposit addresses, withdrawal policy, and reconciliation before our volume was predictable. BroSettlement gave us an API layer our product and finance teams could actually own.”

Head of Payments

iGaming operator

USDT player wallet flow

Wallet and card stack connected
“After a false start with outsourcing, the useful difference was operational clarity: wallet events, card controls, and the support path were all in one integration plan.”

Andriy Ilkiv

CEO, crypto neobank

wallet + card launch

Trading flow moved to MPC wallets
“We wanted wallet infrastructure rather than a closed custody dependency. BroLabel gave us DKG/MPC, policy controls, and event records we could fit under our trading flow.”

Karina Getsko

Head of Operations, trading platform

wallet operations

Ready to ship
Embedded Wallets?

DKG, noncustodial MPC, 10-chain broadcast, self-hosted Co-Signer, ledger, and a sandbox-ready API for stablecoin and iGaming products.

Book a DemoGet Sandbox Access