Crypto checkout on U.CASH: every rail, non-custodial

Checkout and embed on U.CASH

A checkout that closes sales, not tabs: crypto on 35 networks beside cards and the local bank rails, on one surface the buyer never has to leave. The embed drops into any product page; the API drives it server-side for platforms that prefer full control.

Every checkout settles non-custodial, prices per your confirmation policy, and fires a signed webhook the moment paid means paid. Custom tokens on 24 token networks are first-class: your community token is a payment method, not a support ticket.

Crypto checkout in depth

Embedded checkout is the integration tier for businesses with a site they like: the payment surface drops in as a component rather than redirecting the buyer anywhere. The customer keeps the page's context, the merchant keeps the analytics continuity, and the completion event lands server-side through webhooks exactly as the hosted tiers deliver.

The engineering surface is deliberately thin: a script tag, a configuration, and an endpoint for events. Underneath sit the decisions that make it trustworthy, signature verification on every event, retries that assume the merchant's server occasionally sleeps, and status rendering that shows the buyer the same confirmation state the merchant acts on. The embed inherits the asset list and policies from the merchant's configuration, so the integration work is done once at the platform level and every checkout instance just renders it.

How it works

From setup to settled.

Step 01

Create the checkout

Pick the rails: crypto assets, cards, bank rails. Set the confirmation policy per store.

Step 02

Embed or API

Drop the universal embed into the product page, or drive checkouts server-side through the API.

Step 03

Buyer pays their way

Wallet for crypto, card for the card crowd, local rail where the buyer lives: one surface, every rail.

Step 04

Order releases on policy

The signed webhook fires when the confirmation policy is met; the ledger, the inventory, and the buyer all agree.

What you get

Universal embed

A container and a snippet: a full checkout surface inside your page, styled to your brand.

Server-side API

Create checkouts, amounts, and policies from your backend; webhooks keep state in sync.

Custom tokens

Any token on 24 token networks becomes a payment method by wallet and contract.

Confirmation policies

Tune what counts as paid per asset and per store, from coffee-speed to car-safe.

Cards beside crypto

Stripe, Verifone, or PayPal through your own account on the same checkout as the wallets.

Signed webhooks

Cryptographically verified payment events your systems can trust without polling.

Crypto checkout: FAQ

Does the checkout work with my stack?

The embed is a snippet for any site; the API is plain HTTPS for any backend; plugins cover the major platforms. The webhook signs every event for the paranoid path.

Can I accept my own token?

Yes: custom tokens on 24 token networks are first-class payment methods, added by wallet and contract, with your confirmation policy applied.

What happens on underpayment?

The checkout detects it, shows the shortfall, and holds the order visible instead of failing silently: the buyer tops up or the order expires per your terms.

How long does the embed take to integrate?

The surface itself is a script tag and a configuration; the real work is the webhook endpoint and its verification path, which is an afternoon done properly and repays itself on the first event.

Can the embed sit on multiple pages?

Yes: order pages, product pages, and flows can each carry an instance with its own context. All instances settle through the same account and records.