StableIn PaymentsStablecoin checkout and merchant operations software

Integration & operationsLocal workflow demo

Keep the workflow moving after payment.

Server-side quotes, signed notifications, fulfillment deduplication and refund records connect developer integration with everyday merchant operations.

Tech stack

  • Solidity
  • EVM
  • ERC-20
  • TypeScript
  • NestJS
  • MySQL
  • Foundry
Follow the workflow Talk about this idea

0xF1 · 2026-10-20 · Build notes

StableIn Payments · Website integration guide
Website integration guideDemo excerpt · Full screenshot

01 / Integration & operations

Connect the website, payment and delivery

Your server creates the quote, the browser SDK opens checkout, and signed notifications reach the merchant service. The business grants access once, including when the same event is retried.

StableIn Payments · Website integration guide
Website integration guideDemo excerpt · Full screenshot

02 / Integration & operations

Recover notifications and handle after-sales

Follow notification failures and recovery from the order, then handle partial or full refunds. Payment and fulfillment statuses remain distinct, giving support a clear explanation of progress.

StableIn Payments · Merchant order details
Merchant order detailsDemo excerpt · Full screenshot

THE BUSINESS & VALUE FLOW

One order, with revenue and fees clearly accounted for.

Merchants sell products or services and buyers pay with supported crypto assets. Order value, merchant settlement and fees are tracked separately for reconciliation and support.

  1. 01

    Create the order

    Generate a server-side quote and payment order

  2. 02

    Pay by wallet

    The buyer reviews the asset and amount

  3. 03

    Confirm and fulfill

    Signed notifications update orders and grant access

  4. 04

    Settle or refund

    Inspect merchant balances and process refunds

THE MODEL IN A DEMONSTRATION

Demo order — customer pays 100 test USDC merchant receives 99 payment fee is 1.

01

Merchant revenue

Sales of goods or services, such as downloads or account access.

02

Platform revenue

Payment fees are a configurable business parameter. Software delivery is quoted per project.

03

Costs and support

Budget for chain fees, operations and refund funding alongside sales.

The 1% test fee is not a commercial quote. Under the current refund flow, a full 100 refund is funded by the merchant; the original fee is retained.

BUILT BEHIND THE EXPERIENCE

See how the workflow is built.

01

Checkout and SDK

A browser SDK connects sites to checkout. Server-side quotes help protect payment amounts from frontend changes.

02

Confirmation and notifications

Backend workers follow confirmation state and deliver signed Webhooks, with retries for failed notifications.

03

Orders and after-sales

MySQL records connect settlements, access delivery and refunds. The demo covers deduplicated fulfillment after notification retries.

More from the product

StableIn Payments · Failed notification record
Failed notification recordDemo excerpt · Full screenshot
StableIn Payments · Notification recovery and order lookup
Notification recovery and order lookupDemo excerpt · Full screenshot
StableIn Payments · Result after staged refunds
Result after staged refundsDemo excerpt · Full screenshot

BUILT BY 0xF1 / 2026-10-20

What I’m building here

My development focus connects checkout, confirmation, signed notifications and merchant fulfillment, including recovery records when notifications fail.

  • Checkout and SDK
  • Confirmation and notifications
  • Orders and after-sales

Why not deliver immediately after payment?

Verify the notification and current order, then deduplicate by event and order. The demo recovers a failed receiver while repeated notifications still lead to one fulfillment; payment and delivery keep separate states.

What comes next

Further work includes real-wallet compatibility and business integration.

EXPLORE THE PRODUCT

Choose what matters to your business.

Questions before we talk

Do we need to rebuild our storefront?

You can retain the storefront and use an SDK button to start checkout. The merchant backend determines the amount and asset.

Where does the payment go?

The payment transaction sends the merchant net amount to the configured recipient wallet, with platform fees recorded separately.

StableIn Payments / FONE

Building something similar? Let’s talk.

Ask an engineering question, share a product idea or discuss collaboration, deployment or extending the software. A short message is enough.

Talk about this projectRequest a full demonstration