Skip to main content
On this page

DEUNA gives every industry a shared payment foundation without flattening the business context that makes an order useful. Start with your operating model, then connect the checkout, payment methods, routing, risk, intelligence, and post-transaction operations your team needs.

Choose the implementation path#

Business modelBegin withDetailed order model
Digital CommerceDigital CommerceRetail
Recurring CommerceRecurring CommerceCommon order contract plus the subscription lifecycle
MarketplacesMarketplacesCommon order contract with merchant-defined seller references
Airlines & HospitalityAirlines & HospitalityAirlines for supported first-class booking fields
Financial InstitutionsFinancial InstitutionsBanking
EntertainmentEntertainmentCinema for supported screening and seating fields
Quick Service RestaurantsQuick Service RestaurantsQSR

One order contract, supported industry depth#

Every example uses the public POST /merchants/orders contract. Common fields—amounts, currency, payer, callbacks, items, and metadata—stay consistent. Supported first-class fields add context for specific order types such as airline bookings, while merchant-owned references can carry non-sensitive context needed by the business.

Do not infer a new API field or operation from an industry example. Confirm provider, country, payment-method, payout, split, and operation support in the Provider capabilities catalog and with your DEUNA Technical Account Manager.

From order to payment#

Create the order
Send the supported business context and receive an order_token.
Open the experience
Use Checkout, Payment Link, an SDK, or your own interface.
Process the payment
Apply configured providers, routing, risk, authentication, and capture behavior.
Operate the outcome
Reconcile statuses, fulfill the order, and manage post-transaction operations.

Use the complete payload library to copy every supported example, or open Create an order to load a payload in the interactive request panel.