NewSkies Payment API

PCI-DSS Compliance

This API is designed to be PCI-DSS (Payment Card Industry Data Security Standard) compliant. PCI-DSS is a set of security standards established by major credit card companies to ensure that all companies that accept, process, store, or transmit credit card information maintain a secure environment.

The PCI-DSS compliance framework is responsible for:

• Protecting Cardholder Data: Ensuring that sensitive payment information (credit card numbers, CVV codes, etc.) is encrypted and securely transmitted
• Secure Network Infrastructure: Maintaining firewalls, secure configurations, and network segmentation to protect payment systems
• Access Control: Restricting access to cardholder data on a need-to-know basis with unique IDs and strong authentication
• Monitoring and Testing: Regularly monitoring and testing networks and systems to detect and prevent security vulnerabilities
• Security Policies: Maintaining comprehensive information security policies for all personnel handling payment data
• Vulnerability Management: Keeping systems patched and protected against known security threats

By routing payment operations through this PCI-DSS compliant proxy, we ensure that all payment transactions meet the stringent security requirements mandated by the payment card industry.

API Overview

The NewSkies Payment API provides a unified gateway for payment management across multiple integration protocols. This proxy supports three distinct payment channels:

Digital API Payments (/rest endpoints)

The Digital API provides modern RESTful payment operations for the Navitaire NewSkies booking system. All Digital API endpoints are accessible via the /rest/api/nsk/{version}/booking/payments/** path pattern.

Key Features:

• Full CRUD operations for payment management
• Support for multiple payment methods (credit cards, vouchers, credits)
• Direct Currency Conversion (DCC) and Multi-Currency Conversion (MCC)
• Three-D Secure (3DS) authentication support
• Payment refunds and reversals
• Payment fee management
• Stored payment methods

Example Endpoints:

• POST /rest/api/nsk/v5/booking/payments - Create a new payment
• GET /rest/api/nsk/v1/booking/payments - Retrieve all booking payments
• DELETE /rest/api/nsk/v1/booking/payments/{paymentKey} - Delete a payment
• POST /rest/api/nsk/v4/booking/payments/voucher - Add voucher payment
• POST /rest/api/nsk/v6/booking/payments/dcc/{dccKey} - Create DCC payment
• [....]

SOAP API Payments (/soap endpoint)

The SOAP API provides legacy SOAP-based payment integration for systems that require XML-based communication protocols.

Key Features:

• SOAP 1.1 protocol support
• XML request/response format
• Requires SOAPAction header for operation identification
• Supports AddPaymentToBooking operation

Endpoint:

• POST /soap - Add payment to booking via SOAP

Required Header:

SOAPAction: http://schemas.navitaire.com/WebServices/IBookingManager/AddPaymentToBooking

NDC Payments (/ndc endpoint) - Future Support

The NDC (New Distribution Capability) payment endpoint is reserved for future implementation of IATA's NDC standard for airline distribution.

Current Status:

• Returns 501 Not Implemented for all methods
• Placeholder for future NDC payment functionality
• Will support modern airline retailing capabilities when implemented

Endpoint:

• ANY /ndc - NDC payment operations (not yet available)

Authentication

All endpoints require API key authentication. The API key must be provided as a query parameter:

?apikey=YOUR_API_KEY

Error Handling

The API provides protocol-appropriate error responses:

• REST endpoints: JSON error responses with standard HTTP status codes
• SOAP endpoints: XML SOAP fault responses
• Unmatched routes: 404 Not Found with appropriate format (JSON or XML)
• NDC endpoints: 501 Not Implemented

Getting Started

To use this API, you will need:

1. A valid API key configured for flight-newskies-payment-api.
2. Understanding of the payment protocol you wish to use (REST, SOAP, or NDC)

For detailed endpoint documentation, please refer to the OpenAPI specification included with this proxy.

Support

For technical support or questions about the payment integration flow, please contact the API Support Team.