TABLE OF CONTENTS

Overview

For certain airlines, a successful hold may have a very short payment validity period (e.g., several minutes). In such cases, it is critical to minimize the time between placing the hold and confirming it with payment to avoid automatic cancellation by the airline's system.


To ensure a high conversion rate and avoid unnecessarily blocking inventory (seats and fares), it is mandatory to securely collect and authorize the customer's payment details before initiating any booking request (the OrderCreate call with DerbySoft.



For airlines that return supportedIssueWay: "HOLD" and are known to have short payment timers, we strongly recommend the following sequence of actions:


  • Collect and Secure Payment: Complete the payment transaction with your customer first. Ensure the funds are successfully authorized or captured within your own payment system.
  • Execute DerbySoft Booking: Immediately after securing the funds, execute the two-step DerbySoft hold process in rapid, sequential succession:
    • Call 1: POST /api/orderCreate
      • Purpose: Create the order and place the hold with the airline
      • Do not call this endpoint until the customer's payment is secure.

    • Call 2:POST /api/confirmOrder
      • Purpose: Confirm the order and submit the payment details to DerbySoft.
      • Make this call immediately (i.e., within the same server-side process) after receiving a successful response from OrderCreate.