Customer onboarding
Money movement stays locked until the real end user or business is approved.
Developer sandbox now open
Add ACH deposits, hosted KYC, virtual accounts, quote locks, local payouts, and Base USDC settlement without handing provider credentials to every app you ship.
ACH deposits into USDC.
USD
USD
MXN
BRL
COP
EUR
GBP
One API, many rails
Create customers, open provider-hosted KYC, issue virtual deposit details, quote every route, attach your markup, and settle approved transfers through institutional LPs and partner banks.
Money movement stays locked until the real end user or business is approved.
Reusable bank details accept fiat deposits and route settlement to USDC or local payout rails.
Lock rate, partner cost, Universa fee, and tenant markup before the signed transfer is created.
Transparent economics
No $5k/month provider minimum just to validate demand. Test the rails, KYC gates, quotes, transfer signing, and fee model before committing to enterprise contracts.
No monthly minimum
No forced enterprise commitment
30 bps Universa base fee plus your configurable markup
ACH, wire, virtual accounts, USDC, and local payout routes
Often paid plan or sales gate
Volume thresholds unlock better rates
Provider spread plus plan pricing
Coverage depends on region and account approval
$5k/month style minimums can appear before launch
Production access tied to KYB, volume, and risk review
Custom pricing, reserve, and settlement terms
Bank rails first, stablecoin rails by approval
Create approved customers, issue deposit details, and control where converted funds settle. Use virtual account funding for repeat user deposits instead of one-off manual instructions.
Start with the corridors customers ask for first: USD, MXN, BRL, COP, EUR, GBP, and Base USDC settlement behind one quote response.
Universa takes a 30 bps base fee on swaps and transfers. You set the tenant markup above provider costs and show the full fee stack before money moves.
Risk controls
Production tenants complete KYB or individual review before live access. End users complete KYC where the rail requires it. API keys stay scoped, signed, rate-limited, and tied to an audit trail.
Coverage in motion
ACH, wire, customer onboarding, virtual account funding, and audit records.
Quote USD to Mexican pesos, collect fees, and create a signed payout request.
Support PIX-style local rails as partner access and customer approvals expand.
Route Colombian bank payouts through the same quote and transfer contract.
Universa Protocol
The Universa Protocol is a Solana-native rewards vault for approved developers that move real platform volume. Public liquidity, developer incentives, and vested team supply stay separated from day one.
View Solana contract on GitHubThe launch plan creates 10,000,000 total UNV, puts 4,500,000 into public DBC liquidity, reserves 5,000,000 for a Solana Anchor developer rewards vault, and keeps 500,000 for vested team ownership. There is no separate marketing fund.
Public liquidity is quoted in USDC so pricing, depth, and market activity are easy to follow. The launch float is separate from developer rewards and vested allocations.
The vault is a Solana program-owned SPL token account. Epochs have hard caps, each developer can claim once per epoch, and there is no generic admin withdraw path.
KYB, risk review, settled USD volume, returns, chargebacks, and fraud signals are checked server-side before Universa signs a reward release.
The public float and liquidity policy are designed for durable market access, transparent execution, and long-term alignment between developers and network users.
Anyone can inspect the program id, config PDA, vault token account, reward epoch accounts, and claim accounts. The no-withdraw story is complete only after upgrade authority is removed.
Built for builders
Universa holds institutional partner credentials server-side. Developers use tenant-scoped keys, signed requests, idempotency keys, and explicit scopes.
const quote = await universa.quotes.create({
customer_id: "cus_9Kz...",
source: { rail: "ach", currency: "USD", amount: "2500.00" },
destination: { rail: "spei", currency: "MXN" },
settlement: { network: "base", asset: "USDC" },
platform_fee_bps: 20
})
Developer console
Signed in
No live funds move until production KYB, limits, and partner approval are active.
ACH, wire, Base USDC, MXN SPEI, BRL PIX, and COP bank payout flows are available for testing.
Universa fee layer is shown in every sandbox quote before a transfer can be signed.
Switching to real rails requires tenant review, risk limits, and signed provider terms.
Create a customer, launch hosted KYC, then issue sandbox ACH or wire instructions that settle to Base USDC or a configured treasury account.
This area is wired as a sandbox console surface, so it should not imply real users, production volume, or earned revenue before live access is approved.
Browser sessions never receive partner credentials or HMAC secrets. Tenant provisioning, fee limits, and production access remain server-controlled.
Loading...
The landing page quote and this console share the same fee slider, so the developer can see Universa base fee plus tenant markup before creating a signed transfer.
Open quote tester