DerbySoft GDN Seller API

TABLE OF CONTENTS

Request Payload Example

Request Payload Structure
Response

This API provides the capability for sellers to confirm an unticketed order (‘HOLD’ status) by providing payment information

Version	Date	Description of Edit
Beta	2025/09/16	Initial Commit
v1.0	2025/10/22	ConfirmOrderRQ: Add gdnOrderId/gdnBookingId
v1.1	2025/11/23	Added bundleOrders node (optional) under confirmCreate to support bundle feature
v1.2	2026/04/23	OrderView: Return GST related field in contactInfos node.
V1.3	2026/07/02	Added post-booking ancillary modification history for ADD_ANCILLARY. OrderView returns servicePsgFares under orderView.serviceInfos and supports totalWeightMeasure under baggage weightAllowance.
V2.0	2026/08/15	ConfirmOrder RQ: Supported Multi-FOP payment methods. OrderViewRS: Aligned response schema with orderCreate RS

Request Details
Path	v1.0	/api/flight/connectivity/order/confirmOrder
Path	v1.1	/api/flight/connectivity/order/V1.1/confirmOrder
Path	v1.2	/api/flight/connectivity/order/V1.2/confirmOrder
Path	v1.3	/api/flight/connectivity/order/V1.3/confirmOrder
Path	v2.0	/api/flight/connectivity/order/V2.0/confirmOrder

Request Payload Example

{
   "confirmOrder": {
       "flightOrder": {
           "booking": {
               "supplierBookingId": "101522924132221190144"
           },
           "gdnOrderId": "326100900041998261"
       },
       "promotionCriteria": {
           "promotionCode": ""
       },
       "serviceOrderList": [],
       "payment": {
           "amount": "430.02",
           "paymentMethod": {
               "paymentCard": {
                   "cardSecurityCode": "333",
                   "cardBrandCode": "VI",
                   "cardHolderName": "KAREN WILLIAMS",
                   "cardType": "CENTRAL_BILL",
                   "cardNumber": "5200000000002235",
                   "expirationDate": "05/2027"
               }
           },
           "paymentCurrency": "USD",
           "payer": {
               "phone": {
                   "phoneNumber": "+351 14261256705",
                   "contactTypeText": "Passenger"
               },
               "payerName": {
                   "titleName": "Mr",
                   "surname": "Anderson",
                   "givenName": "Sarah",
                   "middleName": ""
               }
           }
       },
       "order": {
           "supplierOrderId": "101522924132221190144",
           "gdnOrderId": "326100900041998261"
       }
   }
}

Request Payload Structure

Key	Parent	Type	Mandatory/Optional	Description
confirmOrder	root	Object	M
order	confirmOrder	Object	M
supplierOrderId	order	String	M
gdnOrderId	order	String	M
flightOrder	confirmOrder	Object	O
serviceOrders	confirmOrder	Object	O
bundleOrders	confirmOrder	Array	O
payment	root	Object	M
amount	payment	String	M	Amount to be charged to this payment method
paymentCurrency	payment	String	M
paymentGateway	payment	String	O	Enumeration: Direct: pay directly to airline/suppliers DSPAY: 3rd party payment service
paymentMethod	payment	Object	O
paymentMethod	paymentMethod	String	O	[Since v2.0] This field indicates the settlement method used for the order. It enables the purchasing agent to explicitly choose between cash‑based (wallet / BSP settlement) and card‑based payment, or other alternative methods, when the transaction supports multiple payment channels. If empty, default will be WALLET. Enumeration List WALLET – Airline / supplier wallet (e.g., IATA EasyPay). Pre‑funded electronic wallet; funds are blocked at the time of ticket issuance. No card details are required. BSP_CASH – BSP cash settlement. The sale is reported as cash and settled via the BSP (Billing and Settlement Plan) according to IATA’s standard settlement timelines. No card details are required. CARD – Payment card (credit or debit). This value requires the PaymentCard sub‑object to be present with valid card details (e.g., card number, expiration date, cardholder name). VOUCHER – Payment using a voucher or travel certificate. BANK_TRANSFER – Payment via bank transfer (wire transfer). LOYALTY_REDEMPTION – Frequent flyer miles or loyalty program redemption. OTHER – Other payment methods not covered by the above values. This is an extensible placeholder for future additions.
paymentCard	paymentMethod	Object	O
cardBrandCode	paymentCard	String	M	Enumeration: VI: Visa MC: Master Card AX: American Express BC: Bank Card BL: Carte Bleu CB: Carte Blanche DN: Diners Club DS: Discover Card EC: Euro card JC: Japanese Credit Bureau Credit Card TP: Universal Air Travel Card CU: China UnionPay MA: Maestro Card
cardNumber	paymentCard	String	M	Credit card number
cardSecurityCode	paymentCard	String	M	Card CVC/CVV number
cardType	paymentCard	String	M	Enumeration: 1: CREDIT 2: DEBIT 3: CENTRAL_BILL
cardHolderName	paymentCard	String	M	Name of cardholder, as it appears on the card
expirationDate	paymentCard	String	M	Card expiration time
payer	payment	Object	O
payerName	payer	Object	O
givenName	payer	String	M
surname	payer	String	M	Family/Lastname of the Pax
middleName	payer	String	O
phone	payer	Object	O
contactTypeText	phone	String	O
phoneNumber	phone	String	O

Response

confirmOrder return the same OrderView structure that is produced by orderCreate; no new fields are introduced, so the payload layout documented for the response applies unchanged to this endpoints

ConfirmOrder

Request Payload Example

Request Payload Structure

Response