Skip to main content
On this page

Use these guides to map business data into DEUNA's public order and payment contracts. The order-model guides include copyable payloads, field mappings, and production checks. The payment-pattern guides cover flows that depend on configuration or merchant-owned records rather than a separate public order type.

Select the correct contract#

RequirementGuideContract guidance
Airline bookingAirlinesUse AIRLINE_ORDER and airline_information.booking_items.
Screening and assigned seatingCinemaUse the standard order with supported event, venue, seating, and item fields.
Restaurant fulfillmentQSRUse the standard order with menu, modifier, store, schedule, and shipping context.
Product and delivery fulfillmentRetailUse the standard order with catalog, discount, address, and shipping fields.
Financial-service paymentBankingUse the standard order with non-sensitive merchant-owned references.
Subscription or scheduled chargeRecurring CommerceUse the common order/payment contract plus the supported credential and subscription lifecycle.
Multi-seller commerceMarketplacesUse the common contract and confirm account-specific split, transfer, and payout support.

The order and payment request library contains complete Purchase V2 and optional create-order examples for the five supported order models. Do not infer hotel, event, seller, subscription, or payout fields from a related example when the public contract does not define them.

Shared implementation sequence#

Map the contract
Choose the supported order type and map authoritative merchant fields.
Create the order
Send deterministic totals and business references, then retain the order_token.
Process payment
Use only methods and operations enabled for the account and context.
Confirm outcome
Use the authoritative final DEUNA order state before fulfillment.

Next, open Create an order or Create payment.