Industry data processing helps you adapt to evolving requirements by supporting airline and car rental payment data.
Supplying this enhanced data can help reduce fees, improve
Analyze fraud metrics across transactions, review detection patterns, and build prevention strategies to minimize losses and liability.
fraud
detection and
Respond to chargebacks with structured dispute workflows including reason code analysis, evidence collection, and representment submission.
dispute
handling, increase customer trust, and support industry compliance.
Industry data processing is available only through a specific list of supported connectors, and coverage may vary across card brands even within those connectors. To confirm whether your current setup supports these fields, contact contact us us.
Airline payments
Airline industry payments include additional data to be captured and passed through the payment
An order is a customer’s request to purchase goods or services, progressing through various states based on payment status.
lifecycle
. This enriched data, including passenger names, ticket numbers, and flight information, enables accurate verification and categorization of transactions.
Merchants operating under airline-related MCCs 3000–3350 or travel agencies MCC 4722 may choose to provide these details.
Airline data requirements
Airline-related information can be included in the
charge
API
request body under industry_data, where the type is
airline
with the following key data:
airline- carrier codes, ticket types, passenger information, and flight datesticket- unique ticket identifier, issue date, restriction status, and the address where the ticket was issuedpassenger- passenger's first and last name, date of birth, phone number, and traveler type, along with an optional code for identifying the travelerflight_legs- details about each leg of the flight, such as flight number, carrier code, class of travel, departure and arrival airports, travel dates, and additional details like departure tax and stopover eligibilityFor each transaction, the flight legs data should be saved, and up to four legs can be included per transfer.
It is crucial that the data be validated in accordance with industry standards. For example, airport codes must follow the IATA codes, and flight dates must be in the correct format.
|
|
Car rental payments
Car rental industry payments include additional data to be captured and passed through the payment
An order is a customer’s request to purchase goods or services, progressing through various states based on payment status.
lifecycle
. This enriched data, including rental agreement details, renter identity, pick-up and drop-off information, and distance terms, ensures proper verification and categorization of transactions.
Merchants operating under car-rental-related MCCs 3351-3500, 7512, 7513, and 7519 may choose to provide these details.
Car rental data requirements
Car-rental-related information can be included in the
Google Pay
API
,
Apple Pay
API
or
resign
API
requests body, or in the
Set up the Solidgate payment form with step-by-step instructions for script loading, container mounting, and payment request configuration.
Payment form
paymentIntent object, under industry_data, where the type is
car_rental
with the following key data:
car_rental- contains agreement details, renter identity, rental dates, refundability, location data, and distance limitspick_up_locationanddrop_off_location- rental addresses including state, city, country, and postaldistance_limit- limit configuration with limit, unit, and additional distance cost
It is crucial that the data is validated according to industry standards. For example, country values must use three-letter ISO format, state values should align with ISO 3166-2, and currency codes must follow ISO-4217.
|
|