Docs/buy/checkout
Reviewed 2026-07-14
Markdown
BetaBuy & sell · Task

Complete a buyer checkout

Create one order from a reviewed seller quote and keep the identifiers needed to recover it.

Start the checkout checksEstimated time5–10 minutes
Trust, applicability, and sourcesMobazha v0.3 release candidate

Before you start

  • Confirm the store identity, item, quantity, variant, fulfillment method, and return policy.
  • Use a current browser session connected to the intended store and backend.
  • Decide whether you are using account checkout or the store's optional Guest Checkout path.
  • Have the exact payment asset available, but do not send funds before the order displays an address, amount, and expiry.

Checkout steps

  1. Open /product/{slug}, confirm the seller and store context, select required options, and add the item to the cart.
  2. Open Cart and confirm every line belongs to the intended seller. A marketplace may curate discovery and record attribution, but the approved seller—not the marketplace projection—must own the checkout handoff and resulting order.
  3. Continue through /checkout; enter only the delivery and contact data required for this order, then choose a destination-valid shipping method where required.
  4. Review subtotal, shipping, discounts, taxes, network or provider costs, optional services, and final total.
  5. Select an available payment method at the payment-method step. Availability comes from the connected backend and store policy, not from a static list in this guide.
  6. If the order mode requires a moderator or other protection choice, review its scope and cost before confirmation.
  7. Confirm the order only after seller, recipient, final total, payment asset or provider, applicable policy, and any protection choice are visible.
  8. On confirmation, save the order identifier and tracking link, then use the order-bound Payment Session for address, provider payload, amount, expiry, and progress.

Pay with an external wallet

  1. Use only the payment choices still visible after the order policy is applied. A protection or settlement mode may intentionally remove a previously cached provider or rail.
  2. In the active Payment Session, match the asset or Token, network where shown, exact amount, payment address or URI, expiry, and order identifier. Do not reconstruct these values from a catalog price.
  3. Scan the active QR code or copy the active address and amount. Before approving the wallet transfer, compare the wallet's parsed recipient and amount with the Payment Session again.
  4. After broadcast, keep the transaction identifier and leave the order available for reconciliation. Read observed transfers, observed or remaining amount, observation status, and confirmations separately.
  5. If the payment instruction expires, stop using its QR code, URI, address, and amount. Refresh through the product to request the current instruction instead of sending to the expired target.

Expected result and verification

The application should display a newly created order with an authoritative state and order-bound Payment Session. Confirm that the item revision, seller, seller-owned backend, total, canonical payment asset or provider, funding target, amount, settlement mode, and expiry match the final confirmation you approved. A marketplace page or referral label is not the seller and must not silently become the order owner.

Do not treat a wallet broadcast, a screenshot, or a pending transaction as completed payment. Wait for the order page to report the required confirmations and funded state.

An order awaiting payment or payment verification should remain in the payment journey. A canceled, declined, expired, refunded, or processing-error order must not be presented as payment success. Paid or fulfillment states may continue to confirmation, but the order detail remains the recovery authority.

If something fails

  • If the quote expires, return to checkout and request a new quote; do not send the old amount.
  • If an item becomes unavailable, return to the cart and re-evaluate the order rather than repeatedly submitting it.
  • If the payment asset or destination changes unexpectedly, stop and verify the store and backend identity.
  • If you created an order but lost the page, use the saved order identifier or Guest Order tracking link.
  • If funds were sent but state does not advance, preserve the transaction ID and order ID and follow order-status troubleshooting.

Continue