Pay: Pay Using Customer Card [PAYCPC]

Guidance for Schema Version:


Definition of Capability


This capability allows an Airline to receive customer payment card details to process payment for an existing unpaid Order or OrderItems.


This capability allows the Seller to:

  1. Pay for an existing unpaid Order or Order Items using customer card

  2. Pay for a selected Offer towards the creation of an Order

NOTE: System Providers will use the above definition that pertains to their customers for Capabilities Verification.

Links to EASD Implementation Guidance

This capability document is currently in the SOSB Ballot process. Once the capability has been approved in the voting process, the links will be updated.

Update links: Capability: Pay using Customer Card

Text from Pay using Customer Card:

▪ Seller has already performed the necessary authentication prior to requesting if required
▪ Seller and airlines implemented all the necessary processes to handle card data

  1. A payer attempts to pay for the unpaid item or items;
    a) Providing payment intent via customer card details and authentication results as needed.

  2. A payee attempts to validate and accept the payment with received card details

Post Condition
▪ Seller receives a view of the confirmed Order with payment confirmation success and document details if applicable
▪ The Order details are returned with a warning message indicating the failed payment with reason for failure
Relevant Messages
▪ OrderChangeRQ
▪ OrderCreateRQ
▪ OrderViewRS

Related Concepts, Capabilities and Worked Examples:

NOTE: Retailing Capabilities Verification Guidance will align to the published EASD Implementation Guidance at all times. From time to time when new guidance is published this will be updated and supersede any Retailing Capabilities Verification Guidance listed below.

Retailing Capabilities Verification Guidance

Airlines have the capability of capturing payments directly from customers through the Payment Card method of payment. Payment Card transactions require the passing of card details through the PaymentCard structure:


In addition to the minimum set of details needed for processing a typical payment card transaction (e.g. CardNumber, CardSecurityCode, CardHolderName, ExpirationDate), this payment method also supports 3D-Secure authentication (both v1 and v2 approaches) and the encryption of the card number and security code elements.

For PaymentCard payments, the Seller needs to indicate the use of this payment method under the TypeCode element with credit card codes defined in the online Implementation Guide.

Payment statuses need to be included in payment summaries (reference to ATSB Codeset “PAYS“): /IATA_OrderViewRS/PaymentFunctions/PaymentProcessingSummary/PaymentStatusCode


Any one of the following message pairs




Any one of the following message pairs



NOTE: For all versions prior to that listed above (generally the most recent), the verification will be based on the guidance available for that version. In the case that no guidance is available, verification will be at IATA’s discretion.