Guide · Shop owners, platforms, developers

How to integrate a store

Integration depth is a dial, not a cliff. At one end, a snippet in a product page gives you the full checkout; at the other, a server-side API gives your platform complete control of amounts, policies, and state. Most merchants start at the shallow end and never need to leave.

This guide walks all three paths and the webhook that ties them together.

You needA U.CASH Pay account with a configured storeAccess to your site (for embed) or backend (for API)

Step by step

Every step, in order.

Step 01

Choose the path

Embed for the fastest path: a checkout surface inside your own page. Payment links for no-site selling: a URL that is the checkout. API for platforms: checkouts created and tracked server-side.

Step 02

Drop in the embed

Add a container and the universal snippet where the payment belongs. The embed offers every rail your store enabled, styled to your brand, and settles identically to every other path.

Step 03

Or publish links

Create reusable links for your services or one-off links per sale; QR renders from any link for counters and print. Status tracks per link: which conversation converted is one glance.

Step 04

Or build on the API

Create checkouts server-side with the amounts, assets, and policies your platform needs; the REST surface and SDKs cover every app framework.

Step 05

Wire the webhook

Register your endpoint and receive cryptographically signed events: payment seen, confirmed per policy, completed. Verify the signature, update your state, sleep well.

Step 06

Test, then live

Run test payments against your confirmation policies, check the webhook handling end to end, and flip the store live. The same rails, the same settlement, no parallel config to maintain.

The part that matters

The embed-versus-API decision is really a question of who owns state. The embed owns the payment surface and hands you webhooks: perfect for shops. The API owns nothing and lets you own everything: perfect for platforms billing on behalf of others, where amounts are dynamic, checkouts are ephemeral, and reconciliation must live in your database. Links are the surprise workhorse: for services sold in conversation, the link replaces the entire checkout page.

Go deeper

Checkout and embedPayment linksEmbed, API and SDKs

FAQ

Does the embed match my brand?
Yes: logo, colors, and optionally your own domain. The payment surface is white-label; U.CASH stays the rails underneath.
Which platforms have plugins?
The integrations directory lists the current set; the universal embed works anywhere HTML does, and the API works anywhere HTTPS does.
How do I handle refunds?
Issue them from your wallet or the console: crypto refunds are sends back to the payer's address, and card refunds run through your processor as with any card charge.

Other guides

How to accept crypto payments

Accept Bitcoin, Ethereum, stablecoins and 53 more assets at checkout in minutes: connect…

How to swap across chains

Swap any asset for any other across 34 networks: connect a wallet, pick the pair, review…

How to buy UCASH

Three ways to get UCASH, the U.CASH network token: card or bank through the partner ramp,…

Keep going

How to integrate a store, done right

Six guides, one platform, every rail non-custodial.