Paiement hébergé en stablecoins pour les commerçants
Créez un paiement hébergé en stablecoins avec liens de paiement, webhooks vérifiés, rapprochement des commandes et remboursements. Comprend une liste de vérification avant lancement.
Start with the order and its completion rule
- Create a server-priced order before opening the hosted page.
- Match verified payment evidence to the order and fulfill it once.
- Keep settlement, refunds and event recovery traceable to the original payment.
Merchant implementation focus
Connect one order to its payment, delivery and finance records.
Hypothèses : Confirm provider access, supported routes and completion states before launch.
The order workflow and 120 USD example are original reference designs. Provider links document the specific product behaviors cited.
Choose between an invoice and a product checkout
A hosted stablecoin checkout lets a customer open a payment page, select a supported payment route and complete the payment from a wallet. For a merchant, the work extends from creating that page to matching the received funds with an order, delivering the purchase and reconciling any refund.
Start with the transaction your business sells. An agency collecting a project deposit needs a named client, an agreed scope and an invoice. A software business selling immediate access needs an order and a reliable entitlement update. These workflows can both use hosted pages, but they need different records and exception handling.
For client billing, Hanko is a Gizmolab product that connects proposals, agreements, hosted invoices and recurring billing. A client can choose a supported stablecoin option alongside the bank payment methods you have configured. Hanko marks a crypto invoice paid after onchain confirmation and provides an explorer-linked receipt. It is our starting point for agencies and service businesses collecting client payments.
For an embedded merchant checkout, select a payment provider that supports your entity, product and exact payment route. Stripe documents stablecoin acceptance through products including Checkout and Payment Links. Check its current account requirements before designing around that route. A custom interface still needs an agreed source of payment truth and a fulfillment process.
Create the order before generating the payment link
Give the order a stable internal identifier before calling a provider. Store the product, customer reference, amount, pricing currency and fulfillment rule in your system. Send a provider-supported reference when creating the payment session, and save the returned session identifier against that order.
Derive the amount from your own price record. A customer can change a browser field or repeat a request. The backend should validate the product and quantity, calculate the amount and decide whether an existing unpaid session can be reused. Keep a provider-supported idempotency key for session creation so an ambiguous response can be investigated against the same request.
A reusable payment link needs a way to distinguish each purchase. Determine whether the provider creates a separate session or payment object for each use. For invoice collection, use the invoice identifier. For a basket with inventory, define when the reservation expires and what an operator should do if payment arrives after the reservation is released.
| Enregistrer | Purpose | Example |
|---|---|---|
| Order ID | Connect the purchase to fulfillment | order-1042 |
| Provider account and session ID | Locate the payment in the correct account | Store the identifiers returned by the provider |
| Amount and currency | Check the payment against the agreed price | 120.00 USD invoice amount |
| Allowed payment route | Identify supported asset and network combinations | A route confirmed for this merchant account |
| Quote or session expiry | Handle a payment outside its original window | Provider expiry and your inventory deadline |
Verify payment before releasing goods or access
Use the customer return page to display status and guide the next action. A customer may close the tab or lose their connection after paying. Stripe’s fulfillment documentation requires a webhook path so successful payments can still trigger delivery when the landing page is never opened.
Your integration should match the verified provider payment to the stored order. Check the provider account, session or payment reference, amount, currency and successful payment state. Define which documented state permits fulfillment. For a direct wallet collection, also verify the exact asset, network, receiving destination and confirmation policy.
Keep payment evidence and delivery evidence separate. A paid order can still need inventory allocation, a license or a shipping task. Persist the accepted payment decision and a durable delivery task together. Make the delivery worker use an order-level fulfillment key, so concurrent notifications or a worker restart cannot grant the same entitlement twice.
Handle delayed, repeated and out-of-order webhooks
Provider events can arrive again after a timeout or a manual replay. Stripe also documents that webhook delivery order can differ from event creation order. Use the provider’s signature-verification procedure with the original request body, and retain a durable event record before acknowledging accepted work.
In an original reference design, the event record is unique by provider account and event ID. A worker resolves the corresponding payment and applies an allowed change to the order. It can retrieve current provider state when an event is incomplete or appears to conflict with records already processed. A timestamp alone is insufficient to decide whether two notifications describe the same payment.
Add a second protection at the business-operation level. Two different events may describe the same completed payment. A database transaction can enforce one accepted payment allocation and one fulfillment task per order. A queue message delivered twice should find the existing task or delivery result. If an external fulfillment service times out, reuse its idempotency mechanism or investigate the original request before sending another.
Run a scheduled reconciliation job that compares open local orders with provider payments. This gives your operator a recovery path for an event that was missed during an outage. Keep the correction auditable, including the payment evidence and the reason the order changed.
Work through a 120 USD order
Consider a synthetic digital-product order priced at 120 USD. The backend creates order-1042 and a hosted payment session for that price. The customer chooses an available stablecoin route and completes the provider’s payment flow. The browser closes before the return page loads.
The verified payment event links to order-1042. Your worker checks the amount and payment state, records payment acceptance and enqueues access delivery in one database transaction. A second delivery of the event finds the existing records. The customer can reopen the order page and see the delivery result without making another payment.
If the session expires before payment, keep an exception path for a late or uncertain receipt. Retrieve the provider’s actual result before offering a fresh session. If the payment is complete but the inventory or service is unavailable, route the case to your agreed fulfillment or refund procedure. Keep the original paid order as the reference for that decision.
| Observation | Order decision | Operator evidence |
|---|---|---|
| Customer returns without verified payment | Continue showing pending status | Order and session identifiers |
| Verified successful payment matches the order | Accept payment and schedule one delivery | Provider payment reference and validation result |
| The event is delivered again | Retain the existing allocation and delivery | Event receipt and order fulfillment key |
| Payment succeeds after an inventory deadline | Apply the late-payment procedure | Payment time, reservation expiry and operator decision |
Reconcile settlement and refunds separately
Record the original order value, customer payment evidence, provider fees, any currency conversion and the merchant settlement reference. A processor balance credit and a bank payout can occur at different times. Ask finance which milestone it needs for order reporting and which it needs for cash reporting.
For a refund, use the selected provider’s documented process. Stripe states that refunds of its stablecoin payments return as stablecoins to the customer’s original wallet. Other collection arrangements need their own verified return instructions and authorization. Preserve the original payment, each refund request, the amount already refunded and the remaining refundable amount.
If a refund request times out, retrieve its status before creating another request. Reconcile a completed refund against the order and accounting records, and make its effect on access or inventory explicit. Store a customer-visible receipt or reference so support can explain the result without relying on a screenshot.
A hosted stablecoin checkout launch checklist
Exercise the full purchase with the provider’s supported testing tools, then agree how to verify behaviors the test environment cannot reproduce. Keep a named operator and a documented recovery action for every exception.
| Test | Résultat attendu |
|---|---|
| Price is edited in the browser | The server uses the approved product price |
| Session creation response is lost | The same request can be located without opening duplicate orders |
| Webhook signature is invalid | The request cannot alter the order |
| Successful payment arrives after the browser closes | The order can still be fulfilled |
| Two workers process the payment concurrently | One payment allocation and one delivery task |
| Payment events arrive in reverse order | The order reflects verified provider state |
| Delivery service times out | The original delivery result is investigated before another attempt |
| Refund response is lost | The existing refund can be located and reconciled |
FAQ
En résumé
- • Choose invoice collection or merchant checkout around the customer transaction.
- • Verify payment and make delivery recoverable across repeated events.
- • Reconcile fees, settlement and refunds with the original order.
Solutions et produits pertinents
Lecture connexe
Besoin d'aide pour cette décision ?
Créez un paiement hébergé en stablecoins avec liens de paiement, webhooks vérifiés, rapprochement des commandes et remboursements. Comprend une liste de vérification avant lancement.