Create payment

Use this merchant-backend operation to create and pay for an inline order in one request. You can also provide the token of an order that already exists. DEUNA applies the payment connections, routing, risk, and capture behavior configured for the merchant.

Send an installment selectionAsk Athia about this#

When the customer selects an option returned by List installment options, preserve both values from that same option:

{
  "payment_source": {
    "method_type": "credit_card",
    "card_info": {
      "card_id": "CARD_ID",
      "installments": 6,
      "installment": {
        "plan_option_id": "a4756a5f-7f9b-414d-8712-e3a9da2be337"
      }
    }
  }
}

The installment count and option ID must match. The option ID identifies DEUNA's resolved campaign/provider option; the count carries the selected number of installments into payment processing. See Installments for campaign eligibility and the end-to-end flow.

Send a recurring card paymentAsk Athia about this#

Recurring fields belong inside the inline order. The initial cardholder-initiated transaction establishes the recurring credential:

{
  "payer_info": {
    "email": "buyer@example.com"
  },
  "payment_source": {
    "method_type": "credit_card",
    "payment_method": "TOKENIZED_PAYMENT_METHOD"
  },
  "order_type": "DEUNA_CHECKOUT",
  "order": {
    "order_id": "subscription-1001-initial",
    "store_code": "main",
    "currency": "USD",
    "sub_total": 1000,
    "total_tax_amount": 0,
    "total_amount": 1000,
    "initiator_type": "customer",
    "recurrence": {
      "first_time_use": true,
      "scheduled": true,
      "bill_reference": "subscription-1001"
    }
  }
}

After the first successful charge, retain the returned order.recurrence.recurrence_id. Send that value with the later merchant-initiated charge:

{
  "payer_info": {
    "email": "buyer@example.com"
  },
  "payment_source": {
    "method_type": "credit_card",
    "payment_method": "STORED_PAYMENT_METHOD"
  },
  "order_type": "DEUNA_CHECKOUT",
  "order": {
    "order_id": "subscription-1001-002",
    "store_code": "main",
    "currency": "USD",
    "sub_total": 1000,
    "total_tax_amount": 0,
    "total_amount": 1000,
    "initiator_type": "merchant",
    "recurrence": {
      "first_time_use": false,
      "scheduled": true,
      "recurrence_id": "RECURRING_CREDENTIAL_ID",
      "bill_reference": "subscription-1001"
    }
  }
}

Use the exact field name recurrence_id; it is the public JSON contract used by Purchase V2. A subsequent charge without a valid identifier cannot be matched to the stored recurrence credential for the selected processor.

Choose how to provide the orderAsk Athia about this#

Start with a complete industry orderAsk Athia about this#

The order field accepts the same business context modeled by the Orders API. Each industry example opens with the recommended inline Purchase V2 request and also lets you inspect the optional create-order-first request.

ResponseAsk Athia about this#

Returns the processed order, including its order_token, order type, resulting status, payment information, and subscription information when applicable. Treat the returned state as authoritative. If it remains unresolved, retrieve the original order after DEUNA processes the asynchronous provider update.

Status codes

IdempotencyAsk Athia about this#

The Gateway applies idempotency to this purchase operation. Send a stable X-Idempotency-Key for the same business attempt and reuse the same key and body after a network timeout. Use a new key for a materially different attempt.

• Generate the key in the merchant backend, not in browser or mobile code.
• Never reuse a key with a different request body.
• Reconcile an uncertain outcome by retrieving the order before starting a new attempt.

See Idempotent requests for the 24-hour retention window, replay behavior, conflicts, and supported operations. Continue with the complete endpoint entry, Authentication, and Error codes.