Build embedded wallets into your product

Create wallets for your users, track deposits, and manage withdrawals through one API. Run the Co-Signer in your own environment and apply your signing policies.

Create an accountExplore the sandbox

No upfront payment. Your first payment is after a month of use. Trial month terms

USDT / USDCCustomer-hosted Co-SignerEd25519 request signingProduction API available

From account to your first test wallet

You will need a developer and an environment to run your Co-Signer. Start with the Free plan on testnet to validate your integration.

  1. Step 1

    Create your account

    Register in the BroSettlement app and set up your organization to access the console.

  2. Step 2

    Set up API access and Co-Signer

    Configure your API credentials and deploy the Co-Signer in your environment to prepare for wallet creation and signing.

  3. Step 3

    Create your first test wallet

    Use the API to create a wallet on testnet, then validate deposit and withdrawal flows before connecting your product.

Read the integration guide

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.

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.

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.

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.

Wallet infrastructure. Ready to integrate.

Embedded Wallets

Create DKG-generated MPC wallets for players, merchants, users, or accounts.

Network Broadcast

Submit signed transactions to enabled networks. Check supported networks and assets through the Assets API.

Operations Journal

Use the operations journal for reconciliation, audit trails, and customer-balance operations.

Customer-hosted Co-Signer

Run a Co-Signer in your own environment with a customer-controlled key share and signing policy.

API Controls

Authenticate requests with Ed25519 signatures, IP allowlists, nonce checks, and scoped organization access.

Threshold signing. Shared control.

The signing flow uses a 2-of-3 threshold: two designated shares are required to produce a signature. A single share is not sufficient to sign.

  • DKG + MPC 2-of-3 signingThree distributed shares; two are required to produce a signature
  • Ed25519 in the production contractRequest signing is described in the current API documentation
  • RBAC with 5 rolesOwner, admin, operator, reader, service
  • Nonce validationUnique nonces help reject repeated signed requests
  • IP allowlist per API keyRestrict API-key use to configured network sources
MPC-CMP Signing ModelMPC · 2/3
Wallet2/3 threshold
K1Customer Co-Signer
K2BroSettlement signer
K3Recovery share
Normal path uses K1 + K2; K3 remains a separate recovery share

Customer-hosted Co-Signer. Your signing control.

The Co-Signer runs in your environment, holds your key share, and evaluates your policy callback. The normal signing path requires both your share and the BroSettlement platform share.

Co-Signer

BroSettlement includes a customer-hosted Co-Signer in the production signing path.

Positioning

Some wallet platforms keep the signing component entirely inside platform-operated infrastructure.

Source access

Inspect the Co-Signer source in the official BroLabel repository

Container deployment

The intended deployment targets include customer cloud, on-premises, and private VPC environments

Customer-operated Share B

You operate Share B; normal signing also requires the BroSettlement platform share

Policy checks

Your callback can evaluate configured limits, enabled networks, and approval thresholds before signing

From a customer request to network delivery. One connected flow.

Wallet creation, transaction intents, API controls, journal entries, threshold signing, network delivery, and event updates in one integration.

  1. 01

    API requests use Ed25519 signatures, IP allowlisting, and nonce validation

  2. 02

    The operations journal records a transaction intent before signing

  3. 03

    Your Co-Signer evaluates policy and returns an approval decision

  4. 04

    The normal MPC path requires your share and the platform share to produce a signature

  5. 05

    Follow network delivery and transaction lifecycle updates through WebSocket events

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.

  1. 01API Gateway
  2. 02MPC Signer
  3. 03Immutable Ledger
  4. 04Blockchain Gateway
Transaction Flow01 — 04

Partner Environment

01
API Client creates an intentYour backend sends a signed API request for a wallet or transaction intent.
POST /transactions
02
Policy callback approves signingThe Partner Co-Signer asks your Callback Handler whether this operation is allowed.
tx_sign_request

BroSettlement Gateways

03
API GatewayEd25519IP allowlistNonce
04
MPC SignerThreshold signing produces the final signatureK1 + K2 create a network-valid signature without reconstructing the private key.
K1 + K2

Core Services

05
Immutable LedgerCreates the operating record for deposits, withdrawals, transfers, reconciliation, and audit.
06
Blockchain GatewayBroadcast and events close the loopBlockchain Gateway broadcasts the transaction, the ledger updates, and WebSocket delivers lifecycle events.
WS /events
API Gateway · MPC Signer · Immutable Ledger · Blockchain Gateway

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 flowTRON / USDT
Wallet modelPer player
DependencyNo PSP

iGaming player wallet flow

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

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.

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.

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.

BroSettlementLifecycle events
01

Create player wallet

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

02

Observe deposits

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

03

Credit by policy

The operator decides when to credit the player balance.

04

Approve payout

Co-Signer checks operator policy before MPC signing.

deposit.observeddeposit.confirmedwithdrawal.signedwithdrawal.confirmed
01

Fast deposit UX

Show incoming funds before final confirmation, then credit by policy.

02

Clean reconciliation

Ledger connects player balances to on-chain movements.

03

Controlled payouts

Operator policy and Co-Signer approval happen before signing.

04

Independent stack

No custodial PSP dependency for wallet infrastructure.

Production API. Start building today.

  • Production Swagger and API documentation
  • Ed25519-signed requests
  • Customer-hosted Co-Signer and policy callback
  • WebSocket events, IP allowlisting, and nonce validation
View Sandbox Demo Open Docs Open Swagger
brosettlement-production.txt
# Production Integration API
REST https://brosettlement-api.brolabel.io/api/v1
Authentication: Ed25519
Register: https://app.brolabel.io/register

# Integration features
Co-Signer · WebSocket · IP allowlist · nonce validation

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 custody · Broad 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 infra · Policy 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 MPC · Custody infra

BroSettlement

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

Stablecoins · iGaming

A trial month with no upfront payment

Free is for testnet only. Paid plans provide mainnet access with no upfront payment and monthly billing for the preceding period.

Free

$0/mo

Testnet only

  • $0 included volume
  • 10 wallets
  • 2 API keys · 1 user
  • 0.00% overage

Agent

$30/mo

Mainnet · Billed monthly in arrears

  • $200,000 included volume
  • 30 wallets
  • 2 API keys · 1 user
  • 0.30% overage

Starter

$300/mo

Mainnet · Billed monthly in arrears

  • $1,000,000 included volume
  • 100 wallets
  • 3 API keys · 5 users
  • 0.20% overage
Recommended

Business

$1,000/mo

Mainnet · Billed monthly in arrears

  • $15,000,000 included volume
  • 5,000 wallets
  • 10 API keys · 25 users
  • 0.12% overage

Scale

$3,500/mo

Mainnet · Billed monthly in arrears

  • $30,000,000 included volume
  • 15,000 wallets
  • 50 API keys · 100 users
  • 0.07% overage

A trial month with no upfront payment

  • Continue using

    If you continue, you pay for the first month after it ends under your chosen plan. Subsequent monthly payments also cover the preceding period.

  • Cancel in the first month

    If you cancel within the first month, you do not need to pay for that period.

  • Return later

    If you later resume using the same account, you will need to pay for the previous unpaid period.

Create an account

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.

  • 01

    BroSettlement as the DKG/MPC and Embedded Wallet infrastructure

  • 02

    BroWallet and BroCard as product layers on top

  • 03

    Or the client product layer built directly on the BroSettlement API

BroSettlementpowers everything.
01DKG + MPC
02Embedded Wallets
03Immutable Ledger
0410-chain Broadcast
BroSettlementDKG + MPC · Immutable Ledger

Try BroSettlement with no upfront payment

Integrate embedded wallets and evaluate them in your own workflows during the first month.

Create an account

No upfront payment. Your first payment is after a month of use. Trial month terms