Every rail on one invoice
56 crypto assets, cards through your own processor, and 20 bank rails: the client picks, you get paid either way.
An invoice that accepts everything: crypto on 35 networks, cards, and the bank rails your clients actually pay through, on one payable invoice. Amount, reference, and due window are set by you; the payment surface, confirmations, and webhook are U.CASH.
Invoices settle non-custodial to your wallet, carry a unique payment reference for reconciliation, and mark themselves paid the moment your confirmation policy is met. Underpayments and overpayments are detected, not discovered.
Invoicing on U.CASH is settlement-agnostic by design: the invoice names the amount, the currency of record, and the reference, and any rail the merchant enables can close it. That single abstraction is what removes the usual fragmented tooling, where each payment path drags along its own invoice format and matching ritual. The reference is the load-bearing field: because every payment arrives tagged, the ledger side becomes a join, and the multi-rail question collapses into one queue.
The accounting posture matters as much as the plumbing. An invoice denominated in the operating currency with crypto legs converting at payment time keeps the books in familiar terms, while the payment records carry both the fiat figure and the chain evidence. Businesses that invoice across borders usually find the peg families do the heavy lifting: a corridor that clears in the local currency behaves identically whether the buyer pays a bank rail or the local peg, and the merchant stops caring which.
From setup to settled.
Set the amount, the currency you bill in, and the rails you accept: crypto, cards, or the bank rails.
The invoice is a link: email it, paste it in a chat, or attach it to the statement of work.
The client picks the rail: a wallet for crypto, a card, or a bank transfer with the invoice's payment reference.
Payment lands non-custodial at your wallet or account; the invoice flips to paid and the webhook fires.
56 crypto assets, cards through your own processor, and 20 bank rails: the client picks, you get paid either way.
Every invoice carries its own reference (B-XXXXXX on bank rails), so reconciliation is a match, not a guess.
Underpayments are detected and held visible; the invoice says what remains instead of silently waiting.
Crypto invoices settle straight to your wallet. U.CASH never holds the payment at any point.
The moment your confirmation policy is met, a signed webhook tells your systems the invoice is good.
Bank-rail invoices hold their reference for 30 days: late corporate payments still reconcile.
Sellers without a site, service pros, anyone billing by message.
Platforms, marketplaces, payroll, affiliates.
Online stores, SaaS, digital goods.
Every rail on one non-custodial platform, under your brand.