Private sandbox now open

Stablecoin rails for markets that actually move USD, BRL, MXN and more.

Launch compliant onramps, offramps, virtual accounts, quotes, and local payouts across ACH, PIX, SPEI, SEPA, FPS, and USDC settlement through one network that routes orders across eligible providers without exposing institutional partner credentials to client apps.

View coverage

Every tenant is isolated. Every end customer completes partner KYC.

USDC token connected to ACH, PIX, SPEI, SEPA, FPS, and COP rails — USDC settlement with local fiat rails and partner KYC controls.

USA ACH / Wire

BRA PIX / BRL

MEX SPEI / MXN

USDC Base settlement

Supported corridors

Start where customers already bank, then settle into USDC when the product needs programmable dollars.

Supported countries and payment rails for USA ACH, Brazil PIX, Mexico SPEI MXN, Eurozone SEPA, UK FPS, and Colombia COP

United States USD via ACH and wire

Bank deposits, withdrawals, and virtual account funding.

Brazil BRL via PIX

Instant local bank rails for Brazilian real corridors.

Mexico MXN via SPEI

Mexican peso movement through the local electronic transfer rail.

Eurozone EUR via SEPA

Euro account-to-account routes for SEPA markets.

United Kingdom GBP via Faster Payments

UK bank transfers through FPS-enabled payout paths.

Colombia COP local routes

Colombian peso coverage tracked as a controlled rollout.

Clear pricing before movement Show every fee before funds move.

Quote first, move second. Partner costs, the Avra base fee, and your own markup stay visible before the transfer is created.

Partner cost Pass-through

Avra base fee 0.30%

Your markup Configurable

No enterprise sandbox tax and no $5k/month minimum just to validate demand. Test rails, KYC gates, quotes, transfer signing, and fee rules before scaling volume.

Quote-first UX

Let users see the rate, rail, fees, and payout before they commit.

A web demo of the Monet bank-transfer quote flow: enter USD, choose a local payout route, and watch the received amount update with animated numbers.

From

USD

Paying with USDC wallet

Arrives Usually within 30 minutes

Total fees $12.50

Exchange cost included in the rate

Provider network

Avra aggregates eligible providers and routes for the best executable quote.

Each quote checks available institutional LPs, partner banks, and regional rail providers, then selects the strongest route after pricing, customer status, speed, limits, compliance rules, and settlement preference.

01 / Aggregate Compare provider paths before funds move

Avra normalizes rates, provider costs, network fees, and route constraints behind one quote response.

02 / Validate Only show routes the customer can actually use

KYC state, destination country, rail support, transfer size, and tenant permissions are checked before signing.

03 / Optimize Return the best net outcome, not just the lowest headline fee

The quote ranks rate, speed, provider reliability, Avra fee, tenant markup, and expected received amount together.

04 / Fail over Re-quote when a rail or provider path degrades

If a provider is unavailable, Avra can route to the next eligible path before an idempotent transfer is created.

The stack

Infrastructure your product can build on, without rebuilding the regulated layer.

01 / IDENTITY

Secure identity verification and compliance review workspace

Customer onboarding

Create individual or business customers and launch hosted KYC or KYB review. Money movement stays locked until approval is active.

Built in sandbox

02 / ACCOUNTS

Virtual bank account cards settling into USDC

Virtual accounts

Issue reusable fiat deposit details for approved customers and define where converted funds settle.

Partner-bank ready

03 / ORCHESTRATION

Quote lock and transfer orchestration across fiat and stablecoin rails

Quotes and transfers

Lock route, partner costs, Avra fees, and tenant markup in a quote before a signed, idempotent transfer is created.

Quote engine ready

04 / ROUTING

Institutional liquidity and partner bank routing network

Partner-aware routing

Keep one Avra contract while institutional LPs, partner banks, and regional rail partners evolve behind the server boundary.

Partner network expanding

A controlled flow of funds

Your users see your product. Partner banks and LPs see the correctly identified customer and full transaction context.

Create a customer

Your tenant sends only the required customer profile.

POST /v1/customers

Complete KYC

The hosted flow records consent and verifies the end customer.

POST /kyc-sessions

Price the route

Avra returns partner, Avra, tenant, and network fees explicitly.

POST /v1/quotes

Move the funds

A signed request executes once and creates a durable audit trail.

POST /v1/transfers

Designed for the real trust boundary

One partner relationship does not mean one shared identity.

Avra holds institutional partner credentials server-side. Each developer gets a scoped API key, each request is signed, and every customer remains a distinct KYC record at the underlying partner.

AUTH HMAC SHA-256 request signing Timestamp and nonce replay protection

SCOPE Tenant and permission isolation Per-key scopes with optional IP allowlists

STATE Idempotent write operations Safe retries across client and partner timeouts

AUDIT Request, fee, and ledger records Traceable operations without leaking partner credentials

Developer-side controls

Sandbox is open. Production money movement is KYB-gated.

Developers are not the end users receiving virtual accounts, but they do control API keys and transfer initiation. Avra reviews the tenant before live access and watches for obvious abuse.

Tenant KYB Business verification before production keys

Companies complete KYB and control-person checks. Individual builders complete KYC before live access.

User consent Funds move only after KYC gates and signed intent

Quotes lock route and fees, transfers are idempotent, and destination context is recorded for review.

Velocity limits Obvious bad behavior gets throttled or blocked

Risk tiers, hourly limits, IP allowlists, and scoped keys reduce blast radius for abusive tenants.

Audit trail Every API action is traceable

Request IDs, nonces, idempotency keys, fees, and ledger entries stay tied to the tenant and customer.

Avra token

Network incentives for builders who create real volume.

The supply is allocated before launch, with the public curve limited to the launch float. Approved businesses receive a wallet, settled API volume unlocks eligibility, and claims are paid from a fixed developer pool.

Burn allocation 25%

Committed for burn from the reserved supply path.

Developer rewards 25%

Pre-funded into a claim contract for volume milestones.

Team 5%

Vested allocation. No separate marketing fund.

Public float 45%

Only the launch float is routed through DBC/public liquidity.

Fee loop 50%

Avra plans to direct half of API fees to recurring market purchases under a published policy.

01 / KYB Business approved

Production rewards start only after tenant KYB and risk review are active.

02 / Wallet Privy wallet linked

Avra generates or connects a developer reward wallet and binds it to the tenant.

03 / Volume Settled flow scored

Only completed, non-reversed API volume counts toward reward eligibility.

04 / Claim Contract pays from the pool

Avra publishes epoch allocations; developers claim unlocked tokens from the distributor.

Token mechanics are subject to final legal review and launch docs. Developer rewards are designed as network participation incentives, not a promise of profit or passive yield.

Developer first

Start in the mock sandbox. Switch live partners later.

The public contract stays stable while live partner access remains gated by commercial and compliance approval.

Node.js Signed request

const response = await avra.customers.create({
  external_id: "user_1042",
  type: "individual",
  full_name: "Avery Morgan",
  email: "avery@example.com",
  country_code: "US"
})

console.log(response.customer.id)