Pay: Pay Using Customer Card [PAYCPC]

Guidance for Schema Version:

21.3 - Please consult the ARM index Schema version 21.3 regarding validation of capabilities within the ARM index program.

Definition of Capability

Airline

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

Seller

This capability allows the Seller to:

Pay for an existing unpaid Order or Order Items using customer card
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

Capability: Pay using Customer Card: https://standards.atlassian.net/wiki/spaces/EASD/pages/574652501

Worked Examples: End to End Payment via Pre-Authenticated Card: https://standards.atlassian.net/wiki/spaces/EASD/pages/574849139

Related Concepts, Capabilities and Worked Examples:

Concepts: Payment: https://standards.atlassian.net/wiki/spaces/EASD/pages/574619671
Capabilities: Payment: https://standards.atlassian.net/wiki/spaces/EASD/pages/574717975
Worked Examples: Payment: https://standards.atlassian.net/wiki/spaces/EASD/pages/574488655

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

For all capabilities, please also consult the list of general guidelines for adherence to best practices that span across several capabilities and messages: https://standards.atlassian.net/wiki/spaces/ARMI/pages/584318980

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:

/IATA_OrderCreateRQ/Request/PaymentFunctions/PaymentProcessingDetails/PaymentMethod/PaymentCard

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.

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

Airline

Any one of the following message pairs
OrderCreateRQ/OrderViewRS
OrderChangeRQ/OrderViewRS

Seller

Any one of the following message pairs
OrderCreateRQ/OrderViewRS
OrderChangeRQ/OrderViewRS

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.