Skip to main content
All systems operationalChangelogv1
Log in
Industry solution

Digital Commerce

Connect product-rich checkout, payment orchestration, fulfillment context, and post-purchase operations for digital commerce.

On this page

Digital Commerce connects the customer checkout to the order, payment, and fulfillment lifecycle. DEUNA lets you use a hosted or embedded experience, your own interface, or a direct server integration while keeping provider routing and payment state behind consistent platform concepts.

Checkout choiceChoose a hosted, SDK, widget, plugin, or Direct API integration.Product contextCarry product, variant, promotion, shipping, and fulfillment information.Payment operationsApply supported routing, authentication, capture, refund, and fallback behavior.

Build the journey#

  1. Create the order server-side with authoritative amounts, currency, items, payer, callbacks, and fulfillment context.
  2. Present only the payment methods and installment options enabled for the account, market, currency, and customer context.
  3. Keep the same order_token and merchant order reference through customer retries and asynchronous provider states.
  4. Treat webhooks or an authoritative order retrieval as the source of truth before fulfillment when the browser result is pending or uncertain.
  5. Preserve capture, refund, cancellation, dispute, and reconciliation evidence against the original order and payment attempt.

Model catalog and fulfillment context#

Use the Retail order model when your implementation needs supported product identity, variant, promotion, delivery, and fulfillment fields. The order payload library contains copyable examples for common commerce models.

Production priorities#

  • Calculate totals and discounts in the merchant backend and make idempotent retries deterministic.
  • Validate provider, method, country, currency, capture, refund, and authentication support before exposing an option.
  • Design explicit loading, pending, decline, redirect-return, timeout, and duplicate-submission states.
  • Test inventory or price changes without creating a second financial attempt accidentally.
  • Verify webhooks, post-purchase operations, and reconciliation before go-live.

Continue with Quickstart, Retail payments and orders, and Webhooks.