The neobank for
esports guilds.
Pass KYB once, fund a treasury with sponsor and prize money, hold USD and USDC, and pay your players — every transfer settling on real rails, not a mock.
From signup to payout,
in one flow.
The polished product flow and the real money flow are the same flow — nothing is faked, and nothing moves until KYB clears.
Onboard the guild
Submit your business details. KYB runs and your guild is driven to active — the gate for everything else.
Fund the treasury
Sponsor and prize money arrives over a USD ACH on-ramp and settles to USDC in your treasury.
Hold USD + USDC
One treasury, both rails. Watch a live balance and a reconciled activity feed of every movement.
Pay your players
Send a player their winnings as a USDC → USD ACH payout and watch it settle to completed.
Everything a guild
treasury needs.
Purpose-built for how esports teams actually move money — sponsor funds in, player payouts out, with compliance and provenance in the middle.
KYB-gated onboarding
A guild becomes a verified business customer. Nothing moves until KYB is active.
USD + USDC treasury
One treasury holds both. Sponsor deposits settle on-chain; the balance is always current.
One-click player payouts
Pay a player as a USDC → USD ACH transfer that settles to completed — no wallet signing.
In-line compliance gate
An amount-threshold policy runs before a payout hits the rails — flag, block, or allow.
USD ⇄ USDC rails
Receive USD over ACH, hold stablecoin, and pay out to any US bank — the rails handle the conversion.
Reconciled activity feed
Every entry is backed by a real Dakota transaction, and pending payouts self-heal to their true status.
Every transfer settles
on real rails.
KYB, deposits, and payouts all run on Dakota’s live sandbox — real business verification, real ACH settlement, real stablecoin. The balance is a ledger of genuine transactions, so what you see is what actually happened.
Compliance and
custody, by default.
Money movement is gated, keys stay server-side, and every payout passes a policy check first — the guardrails aren’t an afterthought, they’re the design.
KYB-gated access
Login and every money action require an active KYB — enforced server-side on each route.
Server-only keys
The Dakota API key lives in server env and never reaches the browser. All rails calls run server-side.
In-line compliance
An amount-threshold policy evaluates every payout before it hits the network.
Encrypted sessions
Sessions are encrypted, http-only cookies; passwords are hashed with bcrypt.
Proven end to end,
on real rails.
Onboard → KYB active → deposit settles → payout completes — verified live, not claimed. These aren’t vanity metrics; they’re what the build actually does.
Guilds clear KYB and open a treasury in seconds on the sandbox — the gate for every transfer.
Hold both in one treasury. Deposits settle USD → USDC; payouts convert USDC → USD ACH.
A unit-tested integration layer plus a live end-to-end run verified against the sandbox.
Frequently asked questions
Open your guild treasury.
Pass KYB, fund your treasury, and pay your first player — all on real rails, in minutes.