NewStablecoin settlement: USDC, EURC and USDG

The U.S. banking stack, as one API.

ACH, wire, RTP, stablecoins and cards, with KYC, AML and the sponsor bank already wired in.

Business verification typically within 48 hoursSandbox included with every planHow it works

Your companyPayments
Illustrative

Payments

TodayNew paymentOpen in full Console

Volume today

$4,218,930.12

+12.4% vs. yesterday

Payments

12,482

38 in flight

Median RTP settle

1.8s

p99 4.2s

Returns today

1

R01 · 6m ago

Recent payments (illustrative data)
AmountRailCounterpartyPayment IDStatusTime
$18,400.00RTPContractor payoutpay_9Hk2vQx7LmSettlednow
$250,000.00WireTreasury sweeppay_3Rt8nWc1ZbProcessing12s
$1,204,318.55ACHPayroll batch · 1,214 itemsbat_7Fq0pJd4Ke1m
50,000.00 USDCUSDCCross-border settlementpay_6Lm2xVb9QaSettled2m
$86.40CardCard authorization · ••4821auth_2Ws5hTy8NcApproved3m
$3,120.00ACHAccount fundingpay_0Pz4cRk6UdReturned R016m
$9,775.00RTPInstant withdrawalpay_8Nj1gFs3YvSettled8m
$42,960.00ACHVendor invoice · net 30pay_4Tc9wEm2Hs11m
$1,480.00RTPDriver earningspay_1Kd7rBn5WqSettled14m

Event stream

streaming
  1. 14:02:07.412payment.settledrtp
  2. 14:02:07.398compliance.passedaml
  3. 14:02:06.951payment.submittedrtp
  4. 14:01:55.030wire.imad_assignedfed
  5. 14:01:41.772batch.acceptedach
  6. 14:01:12.604usdc.transfer.finalbase
  7. 14:00:58.219card.authorizednetwork
  8. 14:00:31.007ach.returnR01

Volume by rail

24h
  • ACH$2.61M
  • Wire$0.88M
  • RTP$0.46M
  • USDC$0.21M
  • Card$0.06M

The problem

Twelve jacks to patch before a dollar moves.

Build it yourself and every obligation is its own connection: a contract, a set of keys, a webhook format and someone on call when it drops.

All twelve, behind one API key.

Drag a plug into a jack, or click one to patch it.

OmniwireAll twelve, behind one API key.

Build it yourself

Twelve separate connections to negotiate, integrate, monitor and audit. About 18 months before the first one carries a live payment.

0 of 12 live

Plug in once

One API, all twelve behind it. About 3 weeks to live.

How a payment moves

Follow one payment down the wire.

One API call, traced from your app to a settled account. Everything on this wire is the part you don't have to build.

  1. 01 — Your app

    One call. Any rail.

    Send an amount, two accounts and rail: "fastest". The request looks the same for ACH, wire, RTP, USDC and cards.

    SDKs for Node, Python, Ruby, PHP and Java

    pay.ts
    const payment = await ow.payments.create({
      amount: 1840000,        // $18,400.00
      currency: "usd",
      from: "acct_ops_4410",
      to: "cpty_contractor_7702",
      rail: "fastest",
      idempotency_key: "inv_2291",
    });
    201 Createdpay_9Hk2vQx7Lm · 212ms
  2. 02 — Compliance

    Checked before it moves.

    KYC and KYB, sanctions screening, AML rules and limits run inline on every payment. Our compliance team runs the program; you keep the audit trail.

    SOC 2 · Built-in KYC and AML

    Pre-flight checkspay_9Hk2vQx7Lm
    • Sender KYBBusiness verified6ms
    • Recipient KYCIdentity verified5ms
    • Sanctions screenOFAC and watchlists clear11ms
    • AML rulesVelocity and pattern, 0 flags9ms
    • LimitsWithin daily limit2ms
    Cleared to move5 of 5 passed · 33ms
  3. 03 — Routing

    Routed to the fastest open rail.

    Omniwire picks RTP when the receiving bank supports it and falls back to wire or same-day ACH when it doesn't. You never write rail logic.

    • ACH
      Same-day or standardFallback 2
    • Wire
      Fedwire, same dayFallback 1
    • RTPSelected
      Seconds, 24/7/365Receiving bank supports RTP
    • USDC
      Stablecoin, 24/7When you set currency: usdc
    • Cards
      Accepted worldwideFor card spend and payouts
  4. 04 — Settlement

    Settled at an insured partner bank.

    Funds move through our FDIC-insured sponsor banks, and your ledger updates the moment they land. No bank agreement to negotiate.

    Omniwire is not a bank · FDIC-insured partner banks

    TransferRTP
    Settled in 1.8s

    $18,400.00

    FromOperating accountacct_ops_4410−$18,400.00
    ToContractor payoutcpty_contractor_7702+$18,400.00
    Created14:02:05.600Cleared14:02:05.633Settled14:02:07.412
  5. 05 — Back to you

    One webhook. Every rail, same shape.

    payment.settled arrives with the rail, timing and trace IDs attached, so reconciliation is a join, not a project.

    Same event for ACH, wire, RTP, USDC and cards

    POST/webhooks/omniwire
    200 OK
    {
      "type": "payment.settled",
      "id": "evt_2Pq8sLx4Hd",
      "data": {
        "payment": "pay_9Hk2vQx7Lm",
        "amount": 1840000,
        "rail": "rtp",
        "fallbacks_used": 0,
        "settled_in_ms": 1812,
        "trace_id": "rtp_20260929_7Qm1"
      }
    }
  6. Settled

    1.8 seconds on the wire.
    About three weeks to wire in.

    That's the whole trip. Everything between your app and the bank is ours to run, audit and keep up.

Example builds

Wired in. Then shipped.

Illustrative examples · not customer data

Three example builds and what each one takes: the rails it switches on and the path from sandbox to live.

Find your route
Example buildIllustrative

A payroll platform pays contractors the same day: RTP when the receiving bank supports it, wire or same-day ACH when it doesn’t.

Wired with SuperAPIEvery U.S. money rail on one API key.
sandbox keys to live
≈ 3 wk
rails on one API key
3
Explore SuperAPI

Illustrative example, not a customer record. About 3 weeks is typical from first sandbox call to live money, versus roughly 18 months building it in-house.

example/payroll / path_to_liveillustrative
  1. day 1Account created, business verification submittedevent: kyb.submitted
  2. day 3Business approved, plan active, sandbox keys issuedsk_test_•••• created
  3. wk 1First contractor payout in sandboxPOST /v1/payments → 201
  4. wk 3Production approved, live keys issuedsk_live_•••• created
  5. liveLive: first same-day payout on RTPstatus: live · rail=rtp · 1.8 s

Switched on

  • RTP
  • ACH
  • Wire
  • Cards (not used)
  • USDC (not used)
  • Open banking (not used)
Example buildIllustrative

A consumer brand launches its own bank: accounts, debit cards and instant transfers in its app, with KYC, AML and the sponsor bank already wired.

Wired with White-label neobankYour bank, your brand, typically live in 4–6 weeks.
kickoff to first customer
4–6 wk
rails behind your brand
3
Explore the neobank

Illustrative example, not a customer record. Launches typically take 4–6 weeks from kickoff to your first customer.

example/neobank / path_to_liveillustrative
  1. day 1Kickoff: brand, products and cards pickedstudio: theme=gold · apps=ios,android,web
  2. wk 1App and card design approvedevent: program.design_approved
  3. wk 2KYC and AML program approvedevent: kyc.program.approved
  4. wk 4Sponsor bank sign-offevent: program.bank_approved
  5. liveLive: first account opened, first card issuedstatus: live · rail=cards

Switched on

  • Cards
  • ACH
  • RTP
  • Wire (not used)
  • USDC (not used)
  • Open banking (not used)
Example buildIllustrative

A card program helps customers build credit history with the debit card they already use, reported to Experian every month.

Wired with Credit BuilderEveryday debit spend, reported to Experian.
reporting to Experian
Monthly
everyday spend, reported
Debit
Explore Credit Builder

Illustrative example, not a customer record. Results vary and no change to any credit score is promised.

example/credit-builder / path_to_liveillustrative
  1. setupCredit Builder added to the programproduct: credit_builder · on
  2. day 1Cardholder opts in, reporting notice shownevent: credit.notice_accepted
  3. mo 1Everyday debit spend on the cardrail=cards · ledger posts
  4. mo endMonth closed into one tradelineevent: tradeline.built
  5. 1stReported to Experian, every monthstatus: reported · bureau=experian

Switched on

  • Cards
  • Accounts
  • Experian reporting
  • RTP (not used)
  • Wire (not used)
  • USDC (not used)

How you go live

Verified in about 48 hours. Live when you’re ready.

Request access and verify your business with our team. Once you’re approved, subscribe to a plan: that’s when you pay, and your sandbox keys come with it. Build against every rail, then go live when production is approved. Talk to us whenever it helps.

  1. 01

    Request access

    Tell us about your business with your company email. We set up your account.

    You + Omniwire

  2. 02

    Verify your business

    Business details, documents and owners. We run KYB with our partner bank, typically within 48 hours.

    You + Omniwire + partner bank

  3. 03

    Subscribe

    Pick your plan. You pay only after your business is approved.

    You

  4. 04

    Build in the sandbox

    Sandbox keys issue once your plan is active. Test every rail with test money.

    Your team

  5. 05

    Go live

    Once production is approved, live keys issue on the same API you built against.

    Live

Find your route

What are you building?
We'll wire the rest.

Pick your product and your volume. We switch on the rails it needs and send you down the fastest path: an account today, or an engineer this week.

What are you building?
How much will you move a month? A range is fine. It only decides your route.

Switched on for a neobank

Ready when you are

Wire in once.

Verify your business once, typically within 48 hours, and every U.S. money rail is in production in about three weeks.

  • SOC 2
  • FDIC-insured partner banks