Developer sandbox now open

The fast way to launch fiat-to-USDC rails

Add ACH deposits, hosted KYC, virtual accounts, quote locks, local payouts, and Solana USDC settlement without handing provider credentials to every app you ship.

Try the quote

ACH deposits into USDC.

Locked quote
You send exactly USD
Exchange cost included in the rate
Recipient gets

Arrives

Usually within 30 minutes

Total fees

$31.25

Destination

MXN SPEI bank
USA ACH Wire USDC Mexico SPEI Brazil PIX Colombia bank Solana settlement
USD MXN BRL COP EUR GBP

One API, many rails

Build the money movement layer once. Let Universa handle the regulated edges.

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.

A person showing a phone to a family member outside a neighborhood grocer
Remit

Remittance app

Let users fund in dollars, quote local currency, and send to family through compliant payout routes.

Workers reviewing payroll on a phone at a construction site
Pay

Global payroll

Pay international contractors with KYC-gated accounts, stablecoin settlement, and local bank payouts.

Creators checking a payout at an outdoor market
Creator

Creator payouts

Move marketplace earnings to creators across wallets, USD accounts, and supported local rails.

A traveler checking a wallet on a balcony while packing
Wallet

Stablecoin wallet

Add fiat deposits, virtual accounts, and USDC settlement to a consumer or business wallet.

Marketplace sellers reviewing payout details while packing orders
Market

Marketplace disbursements

Route seller payouts with signed transfers, fee controls, idempotency, and audit-ready records.

An international traveler checking an account on a phone in a transit hall
USD

USD accounts for international users

Give approved users a dollar funding route and digital-dollar balance without stitching providers together.

Customer onboarding

Money movement stays locked until the real end user or business is approved.

Virtual accounts

Reusable bank details accept fiat deposits and route settlement to USDC or local payout rails.

Quote and transfer

Lock rate, partner cost, Universa fee, and tenant markup before the signed transfer is created.

Small business operators reviewing a money movement app at a cafe
Go live corridor by corridor. Start with ACH and USDC, then expand into MXN, BRL, COP, EUR, and GBP as partners approve volume.

Transparent economics

No enterprise sandbox tax.

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.

Sandbox access Monthly minimum Volume gate Fee model Rails

Universa

$0 to test

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

API

Traditional onramp

Custom quote

Often paid plan or sales gate

Volume thresholds unlock better rates

Provider spread plus plan pricing

Coverage depends on region and account approval

PSP

Enterprise PSP

Contract first

$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

01 / accounts

ACH, wire, and virtual accounts

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.

02 / payouts

Local payout routes

Start with the corridors customers ask for first: USD, MXN, BRL, COP, EUR, GBP, and Solana USDC settlement behind one quote response.

03 / fees

Your markup, our rails

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.

Compliance operations specialists reviewing a customer verification workflow

Risk controls

Developers get keys. End users still get verified.

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.

Tenant review KYB before production keys
User gate Funds stay locked until KYC is active
Abuse controls Velocity limits, IP allowlists, scopes, and holds
Read the API model

Coverage in motion

Launch the corridors users already understand.

USD in

ACH, wire, customer onboarding, virtual account funding, and audit records.

MXN out

Quote USD to Mexican pesos, collect fees, and create a signed payout request.

BRL out

Support PIX-style local rails as partner access and customer approvals expand.

COP out

Route Colombian bank payouts through the same quote and transfer contract.

$UNV

A staking rewards layer for Universa rails.

UNV is the staking token for Universa rails. Approved developers and operators stake UNV to qualify for rewards tied to verified onboarding, account, quote, transfer, and payout volume. Rewards come from real platform usage, not passive holding.

Open contract repo
Staking wallet No wallet connected

Connect Phantom to read the Solana wallet balance used for UNV staking eligibility. Google signs you into the developer dashboard; Phantom proves the wallet side.

UNV balance -- UNV Connect Phantom to read your UNV staking balance.
02 / how it is made

Solana mint, Meteora DBC, staking reserve

The launch flow creates the UNV mint through Meteora Dynamic Bonding Curve, quotes public liquidity in USDC, migrates to DAMM v2, then separates public liquidity, the staking rewards reserve, and locked team allocation from day one.

03 / why it exists

Stake into real integration risk

Developers who stake UNV and take on bank, stablecoin, KYC, quote, and payout integration work should have an upside path tied to real settled volume, not anonymous wallet farming.

04 / staking

Stake UNV to qualify for rewards

Staking creates a commitment before rewards are earned. Eligibility can require tenant approval, active KYB/KYC, minimum stake, verified usage, and clean risk signals before a rewards period is paid.

05 / reward funding

Rewards follow real platform activity

Rewards are designed to be funded and paced around actual platform revenue, transfer volume, FX, settlement, and tenant activity. Higher usage can support larger reward periods while keeping rewards tied to productive integrations.

  • Stake first, then earn based on approved usage.
  • Reward pools are capped before each period opens.
  • Fees, stake, usage, and risk checks all affect eligibility.
06 / verification

Stake, usage, and rewards stay auditable

The rewards model is built to be inspectable: staking status, eligible usage periods, approved recipients, reward caps, and completed releases can be reconciled against platform records and Solana transactions.

01 Stake UNV Commit tokens before the usage period begins.
02 Move volume Onboard users, create accounts, quote transfers, and settle payouts.
03 Pass review KYB, risk, fraud, chargebacks, and limits are checked first.
04 Earn rewards Approved stake and verified usage determine reward eligibility.
07 / reward policy

Staking rewards are capped by stake, usage, and risk.

Staking does not create automatic yield. A developer earns only when their approved stake is matched with verified platform activity and a published reward period. Reward caps keep payout rates tied to real traction instead of passive holding.

Control Purpose Reward impact
Minimum stake Require commitment before rewards Filters passive wallets
Verified volume Count real settled rails usage Rewards productive integrations
Risk review Check KYB, fraud, returns, and abuse Blocks low-quality activity
Period cap Set max rewards before each cycle Prevents uncapped payouts

Recommendation: reward stakers for verified platform work, keep period caps explicit, and avoid presenting UNV as a passive holding product.

Built for builders

One contract for onboarding, accounts, quotes, and transfers.

Universa holds institutional partner credentials server-side. Developers use tenant-scoped keys, signed requests, idempotency keys, and explicit scopes.

Quote Transfer
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: "solana", asset: "USDC" },
  platform_fee_bps: 20
})