---
title: "Manual Sale"
method: POST
path: "/transactions/manualsale"
tags: ["Transactions"]
---

# Manual Sale

`POST /transactions/manualsale`

This function is used to request authorization and a sale in an offline scenario, which means that Shift4 will not seek processor approval. An authorization code should be included in this request if the amount being submitted in the request is greater than the authorization amount currently on file.

For Restaurant industry, review [Restaurant Authorization and Settlement Flow](/guides/core-concepts/restaurant-authorization-and-settlement-flow)

**Integration Methods:**
- Host Direct
- Locally Installed UTG
- Commerce Engine For On Premise
- Commerce Engine For Cloud

See the [Integration Methods](/guides/quickstart#integration-methods) and [URLs Section](/guides/quickstart#urls) sections of the Development Quick Start guide for details regarding each processing option.

See the [JSON Body Schemas](/guides/quickstart#json-body-schemas) for more details on the various JSON body formats.

## Headers

- `InterfaceVersion` string, required
- `InterfaceName` string, required
- `CompanyName` string, required
- `AccessToken` string, uuid, required

## Request body

- union
  - TransactionsManualsaleComengdevice
    - `dateTime` string, ISO 8601, required — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
    - `amount` AmountObjectNoSurcharge, required — Object containing information regarding the amount being requested. The `total` field within the object is required and specifies the amount being requested. All other fields are for informational purposes and must also be included in the `total` field. For example, a purchase of $100 with a $20 tip and $8 tax would be `128.00` in the `total` field, `20.00` in the `tip` field and `8.00` in the `tax` field. Note: For merchants that are configured to allow multiple currencies, the amount fields can specify up to three decimal places. However, the number of decimal places can not exceed the number allowed for the specified currency. See the [Currency Codes](/guides/appendices/currency-codes) section for details.
      - `total` number, required — The amount being charged for a particular transaction. If other amount fields are sent, they must be included in the total amount. Amount cannot be zero.
      - `tax` number, required — The amount of sales tax charged for a transaction. The tax amount is used by businesses to track tax expenses for accounting purposes. Identifying the tax amount also helps consumers understand the total amount that they were billed. This field is part of Level 2 card data.
      - `taxIndicator` 'Y' | 'N' — Value|Description -----|----------- Y | Tax is included N | Tax is not included
      - `cashback` number — Specifies the cashback amount in a transaction. When using a UTG-controlled PIN pad with the ALLOWCASHBACK API Option, this field will return the cashback amount requested by the consumer. The interface can also send the desired cashback amount in a request by adding it to the `amount.total` and including it in the `amount.cashback` field. This will bypass prompting the consumer for a cashback amount.
      - `iiasAmounts` IIASAmounts[] — **Conditional: Send in the request if processing for a health care merchant.** For Vision related charges you must send only `iiasAmounts.type = 4V` and the corresponding `iiasAmounts.amount` value. For all other charges, the first entry in the array should have an amount representing the total of all healthcare costs, and `iiasAmounts.type = 4S`. Any subsequent entries should contain the subtotal for each of the other expense types involved in this transaction.
        - `amount` number — The subtotal for this type of healthcare expenses.
        - `type` '4O' | '4S' | '4T' | '4U' | '4V' | '4W' | '4X' — This code classifies eligible healthcare expenses. Value|Description -----|----------- 4O | Cash Disbursement (Discover Only) – Amount of Cash Back Being Requested 4S | Healthcare (Visa/MC Only) – Qualified Medical Expenses or Over-the-Counter 4T | Transit (Visa Only) – Transit Fare Media (e.g., Commuter and Parking Passes, Mass Transit Vouchers, and Tickets) 4U | RX (Visa/MC Only) 4V | Vision (Visa Only) 4W | Clinical (Visa Only) 4X | Dental (Visa Only)
      - `tip` number — **Conditional: Send in the request if a tip is included.** The tip amount of the transaction.
      - `checkTotal` number — Optional field specifying the total amount of the entire bill/invoice that this transaction is part of. It can be larger than `amount.total` in scenarios where the check is being split or if a portion of the check was already paid in cash or another form of payment.
    - `clerk` Clerk, required
      - `numericId` integer, required — A number used to identify the point-of-sale (POS) or property management system (PMS) clerk or user. The value cannot be 0. An interface must be able to dynamically populate this field (not use a hardcoded value), unless the interface will be used exclusively for e-commerce.
    - `transaction` object, required
      - `invoice` string, required — 10-digit invoice number assigned by the interface to identify a transaction. An invoice number serves as a unique key that identifies a transaction within a batch in Shift4's Gateway. **Note: For US and Canadian processing: Although the invoice number is sent as a JSON string it is a numeric value. No alpha characters are allowed.** **For processing outside of the US and Canada alpha characters are allowed.**
      - `authorizationCode` string, required — The authorization code provided by the consumer’s issuing bank. It is provided in a response if an online authorization or sale request is approved. Following a referral response, it is also specified in [Manual Sale](/apis/payments-platform-rest/openapi/transactions/manualsale) requests.
      - `manualTranId` string — This is typically used in a Referral. If a ManualTranID is returned by the issuer with the Auth code, it should be sent to the processor in the ManualTranid field.
      - `notes` string — A free-form notes field that supports the use of HTML tags. This can be used for reference in [Lighthouse Transaction Manager](https://ltm.shift4test.com/) and is not sent to the authorization host. Escaped quotation marks should not be sent in the Notes field.
      - `businessDate` string, ISO 8601 — Desired business date of a transaction. Include when overriding the existing business date of a transaction. The overriding date may be earlier or later than the existing date. (yyyy-mm-dd)
      - `amex` TransactionAmex
        - `propertyCode` string — The code that contains a Merchant-assigned store or location number (or name) that uniquely identifies where the transaction took place.
      - `auto` AutoCheckOut — **Conditional: Utilize this object for Auto Rental transactions**
        - `distanceDriven` integer — The amount of distance the cardholder drove the vehicle.
        - `distanceUnit` 'M' | 'K' — The unit of measure that corresponds to the `distanceDriven` field. Value|Description -----|----------- M | Miles K | Kilometers
        - `lateAdjustment` number — A dollar amount for late adjustment fees for an auto rental, including refueling charges, a surcharge, or charges for damage incurred during use.
        - `noShowIndicator` 'Y' | 'N' — Indicates whether or not the cardholder picked up a reserved rental car. Value|Description -----|----------- Y | customer did not pick up the rental car N | customer did pick up the rental car
        - `additionalCharges` AutoAdditionalCharges — The codes used to provide a reason for additional charges in an auto rental sale. Multiple codes can be specified for the same transaction.
          - `gasoline` 'Y' | 'N'
          - `lateReturn` 'Y' | 'N'
          - `mileage` 'Y' | 'N'
          - `oneWayServiceFee` 'Y' | 'N'
          - `violationFee` 'Y' | 'N'
        - `driver` AutoDriver
          - `license` string — The cardholder's driver's license number.
          - `name` string — In a sale/authorization request for an auto rental, the customer’s name exactly as it appears on their driver’s license.
          - `taxNumber` string — This field contains the driver’s Tax Identification Number.
        - `rental` AutoRental — Information relating to where the rental card was picked up.
          - `agreement` string — Contract number for an auto rental agreement.
          - `city` string — City where rental car was picked up.
          - `countryCode` string — Country where rental card was picked up.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was picked up in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was picked up in U.S. postal abbreviation format.
        - `return` AutoReturn — Information relating to where the rental car was returned
          - `city` string — City where rental car was returned.
          - `countryCode` string — Country where rental card was returned.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was returned in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was returned in U.S. postal abbreviation format.
      - `airline` AirlineRequest — **Conditional: Utilize this object for Airline transactions in Authorization/Sale requests when possible. If unable to provide this data at Authorization, this object must be sent in subsequent Capture requests for the transaction.**
        - `carrierCode` string, required — The code of the airline carrier issuing the ticket.
        - `carrierName` string, required — The name of the airline carrier issuing the ticket.
        - `conjunctionTicketIndicator` 'Y' | 'N', required — Indicates whether the itinerary contains more than four segments of travel. Value | Description -------|------------------- Y | Yes N | No
        - `documentType` '01' | '02' | '03' | '04' | '05' | '06' | '07' | '08' | '09' | '10' | '11' | '12' | '13' | '14' | '15' | '16' | '17' | '18' | '19' | '20' | '21' | '22' | '23' | '24' | '25' | '26' | '27' | '28' | '29' | '30' | '31' | '32' | '33' | '34' | '35' | '36' | '37' | '38' | '39' | '41' | '42' | '43' | '44' | '45' | '46' | '47' | '48' | '49' | '50' | '51' | '52' | '60' | '64' | '65' | '66' | '67' | '68' | '69' | '70' | '71' | '72' | '73' | '74' | '75' | '76' | '77' | '78' | '79' | '80' | '81' | '82' | '83' | '84' | '85' | '86' | '87' | '88' | '89' | '90' | '91' | '92' | '93', required — This field contains the airline Document Type code, which indicates the purpose of this transaction. This information may appear on the descriptive bill on the Cardmember's statement, or be used to resolve billing inquiries and disputes. The codes entered in the Transaction Type and Document Type fields are used together to describe the purpose of this transaction. Value | Description ------|--------------- 01 | Passenger Ticket 02 | Additional Collection 03 | Excess Baggage 04 | Misc. Charge Order (MCO) / Prepaid Ticket Auth 05 | Special Service Ticket 06 | Supported Refund 07 | Unsupported Refund 08 | Lost Ticket Application 09 | Tour Order Voucher 10 | Ticket by Mail 11 | Undercharge Adjustment 12 | Group Ticket 13 | Exchange Adjustment 14 | SPD/Air Freight 15 | In-flight Adjustment 16 | Agency Passenger Ticket 17 | Agency Tour Order/Voucher 18 | Agency Misc. Charge Order (MCO) 19 | Agency Exchange Order 20 | Agency Group Ticket 21 | Debit Adjustment Duplicate Refund/Use 22 | In-flight Merchandise Ordered 23 | Catalogue Merchandise Ordered 24 | In-flight Phone Charges 25 | Frequent Flyer Fee/Purchase 26 | Kennel Charge 27 | Animal Transportation Charge 28 | Firearms Case 29 | Upgrade Charge 30 | Credit Unused Transportation 31 | Credit Class of Service Adjustment 32 | Credit Denied Boarding 33 | Credit Misc. Refund 34 | Credit Lost Ticket Refund 35 | Credit Exchange Refund 36 | Credit Overcharge Adjustment 37 | Credit Multiple Unused Tickets 38 | Exchange Order 39 | Self-Service Ticket(s) 41 | In-flight Duty Free Purchase 42 | Senior Citizen Discount Booklets 43 | Club Membership Fee 44 | Coupon Book 45 | In-flight Charges 46 | Tour Deposit 47 | Frequent Flyer Overnight Delivery Charge 48 | Frequent Flyer Fulfillment 49 | Small Package Delivery 50 | Vendor Sale 51 | Miscellaneous Tax(es) Fee(s) 52 | Travel Agency Fee 60 | Vendor Refund Credit 64 | Duty Free Sale 65 | Preferred Seat Upgrade 66 | Cabin Upgrade 67 | Lounge/Club Access or Day Pass 68 | Agent Assisted Reservation. Ticketing Fee 69 | Ticket Change or Cancel Fee 70 | Trip Insurance 71 | Unaccompanied Minor 72 | Standby Fee 73 | Curbside Baggage 74 | Inflight Medical Equipment 75 | Ticket or Pass Print Fee 76 | Checked Sporting/Special Equipment 77 | Dry Ice Fee 78 | Mail/Postage Fee 79 | Club Membership Fee - Temporary/Trial 80 | Frequent Flyer Activation/Reinstatement 81 | Gift Certificate 82 | Onboard/Inflight Prepaid Voucher 83 | Optional Services Fee 84 | Advanced Purchase - Excess Baggage 85 | Advanced Purchase - Preferred Seat Upgrade 86 | Advanced Purchase - Cabin Upgrade 87 | Advanced Purchase - Optional Services 88 | WiFi 89 | Packages 90 | Inflight Entertainment/Internet Access 91 | Overweight Bag Fee 92 | Sleep Sets 93 | Special Purchase Fee
        - `electronicTicketIndicator` 'Y' | 'N', required — Indicates if an electronic ticket was issued. Value | Description -------|------------------- Y | Yes N | No
        - `internetIndicator` 'Y' | 'N', required — Indicates if this is an internet transaction. Value | Description -------|------------------- Y | Yes N | No
        - `issueDate` string, ISO 8601, required — The date the ticket was issued to the customer. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `numberOfCities` number, required — The number of airports or cities for each leg on the ticket (including origination and destination cities).
        - `numberOfCarriers` number, required — This field contains the number of airline carriers.
        - `numberOfPassengers` number, required — The number of passengers in the transaction.
        - `passengerArrivalDate` string, ISO 8601, required — Date that the ticket holder is scheduled to arrive at their destination at the time of issuance of the original ticket. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerDepartureDate` string, ISO 8601, required — Date that the ticket holder is scheduled to depart at the time of issuance of the original ticket. The date may be a future one. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerNameRecord` string, required — A passenger name record (PNR) is a record in the database of a computer reservation system (CRS) that contains the itinerary for a passenger or a group of passengers travelling together
        - `restrictedTicketIndicator` '0' | '1', required — Indicates whether this ticket is non-refundable. Value | Description -------|------------------- 0 | No restriction 1 | Restricted (non-refundable) ticket
        - `ticketChangeIndicator` 'C' | 'N', required — Indicates why a ticket was changed. This field should contain spaces or one of the below codes. Value | Description -------|--------------- C | Change to existing ticket N | New ticket
        - `ticketTranType` 'TKT' | 'REF' | 'EXC' | 'MSC', required — This field contains the ticket transaction type code assigned to this transaction. Value | Description -------|--------------- TKT | Ticket Purchase REF | Refund EXC | Exchange Ticket MSC | Miscellaneous (non-Ticket Purchase- and non-Exchange Ticket-related transactions only)
        - `typeIndicator` 'R' | 'O' | 'M', required — Indicates if this ticket is a round trip, multi-city, or one-way ticket. Value | Description -------|--------------- R | Round-Trip O | One Way M | Multi-City
        - `tickets` AirlineTickets[], required — Array of ticket number and passenger name. Note: At least one instance of ticket number and passenger name info should be provided.
          - `passengerName` string, required — Name of the passenger to whom the ticket was issued. This field contains the Passenger Name in format: `SURNAME FIRSTNAME MIDDLEINITIAL TITLE` Example: "Doe Jane M Mrs"
          - `ticketNumber` string, required — The ticket number provided by the Carrier for the passenger.
          - `ticketFare` number, required — Ticket fare is the total amount for each ticket, including service fee or any other fee for each ticket.
        - `flightLegs` AirlineFlightLegs[], required — Array of flight trip leg info. Maximun 4 legs to a trip allowed. Note: At least one instance of flight trip leg info should be provided.
          - `carrierCode` string, required — Code indicating name of carrier (United Airlines, Jet Blue, etc.) for the leg.
          - `couponNumber` number — Number of coupons in the ticket for the leg.
          - `destAirportCode` string, required — Indicates destination city's airport code for the leg.
          - `fare` number, required — This field contains the total Fare for this trip segment. This is not the total amount billed to the customer.
          - `fareBasis` string, required — This field contains primary and secondary discount codes that indicate the class of service and fare level associated with the ticket for the leg. Truncate at 24 bytes, if necessary.
          - `flightNumber` string, required — Number of the airline flight to be taken on Leg of the trip.
          - `legArrivalDateTime` string, ISO 8601, required — The date and time the flight is scheduled to arrive for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `legDepartureDateTime` string, ISO 8601, required — The date and time the flight is scheduled to depart for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `originAirportCode` string, required — Indicates origination city's airport code for the leg.
          - `serviceClass` string, required — Indicates service class for leg. Value | Description -------|--------------- FC | First Class BC | Business Class EC | Economy/Coach Class
          - `stopOverCode` string, required — Indicates whether a stopover is allowed on this ticket for leg. The entry must be a D, O, or X. Value | Description -------|--------------- O | Stopover allowed X | Stopover not allowed D | Destination point
          - `tripLegInfo` string, required — Description of leg or stage of trip.
        - `ancillaryServices` AirlineAncillaryServices[] — Array of ancillary service code and fees. **Conditional: Send if any ancillary services were charged.**
          - `serviceCode` 'BF' | 'BG' | 'CF' | 'CG' | 'CO' | 'FF' | 'GF' | 'GT' | 'IE' | 'LG' | 'MD' | 'ML' | 'OT' | 'PA' | 'PT' | 'SA' | 'SB' | 'SF' | 'ST' | 'TS' | 'UN' | 'UP' | 'WI', required — This field describes the type of service that has been provided. Value | Description ------|--------------- BF | Bundled Service BG | Baggage Fee CF | Change Fee CG | Cargo CO | Carbon Offset FF | Frequent Flyer GF | Gift Card GT | Ground Transport IE | In-Flight Entertainment LG | Lounge MD | Medical ML | Meal/Beverage OT | Other PA | Passenger Assist Fee PT | Pets SA | Seat Fees SB | Standby SF | Service Fee ST | Store TS | Travel Service UN | Unaccompanied Travel UP | Upgrades WI | Wi-Fi
          - `serviceFee` number, required — This field contains the amount associated with the value provided in ancillary Service Code.
        - `travelAgencyCode` string — Code identifying travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `travelAgencyName` string — Name of travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `exchangeTicketNumber` string — The original ticket number that was replaced by a new ticket number.
      - `cardOnFile` CardOnFile — **Conditional: Send this object when the transaction being performed is using a card on file or when the request will result in storing a card on file.** See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for more information.
        - `type` 'S01' | 'S02' | 'U01' | 'U02' | 'U03' | 'U04' | 'U05' | 'U06' | 'U07' | 'U08' | 'U09' — This field specifies the type of the card-on-file transaction. Below is a table showing the valid values for use cases where the cardholder is entering their card data to store on file. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | S01 | Cardholder | No | Yes | Used when the initial transaction/card verification request is not for a recurring payment. | | S02 | Cardholder | Yes | Yes | Used when the initial transaction/card verification request is for a recurring payment. Requires sending `cardOnFile.recurringFrequency` and `cardOnFile.recurringExpiry` | Below is a table showing the valid values for uses cases where you already have a card on file and are using that existing card to process a transaction. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | U01 | Cardholder | No | Yes | Unscheduled transaction using the card on file initiated by the cardholder | | U02 | Merchant | No | No | Unscheduled transaction using the card on file initiated by the merchant | | U03 | Merchant | Yes | No | Merchant initiated recurring payment using the card on file | | U04 | Merchant | No | No | Identifies a transaction as a Reauthorization COF transaction. | | U05 | Merchant | No | No | Identifies a transaction as a Resubmission COF transaction. Only certain merchant categories are able to send a resubmission, and it can only be done if the original authorization attempt was declined due to insufficient funds. | | U06 | Merchant | No | No | Identifies a transaction as an Estimated Authorization COF transaction. | | U07 | Merchant | No | No | Identifies a transaction as a Delayed Charges COF transaction. For example, a hotel might charge a customer for room damages after the guest has already checked out. | | U08 | Merchant | No | No | Identifies a transaction as an Incremental COF transaction. For example, a hotel which authorized a customer’s card for one night at check-in might increase the authorization amount to cover two nights when the customer decides to extend their stay. Shift4 automatically detects this scenario and sends the appropriate value to the processor. | | U09 | Merchant | No | No | Identifies a transaction as a No Show COF transaction. For example, a hotel might charge a customer who does not show up for a booked stay. | See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for additional details.
        - `recurringExpiry` string — Date after which no further authorizations shall be performed. This field is limited to 8 characters, and the accepted format is YYYYMMDD. **Conditional: This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `recurringFrequency` string — Indicates the minimum number of days between authorizations. **Conditional: 'This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `transactionId` string — This field is returned in the initial COF response, and ties subsequent COF transactions to the original authorization. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
        - `transactionLinkId` string — A unique identifier assigned to each transaction to link related events throughout the transaction lifecycle. This field is supported for Mastercard brand only. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionLinkId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionLinkId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
      - `hotel` HotelCheckOut — **Conditional: Utilize this object for Hotel transactions**
        - `arrivalDateTime` string — Arrival date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the arrival date needs to be one day before the sale date.
        - `departureDateTime` string — Departure date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the departure date needs to be the day of the sale.
        - `primaryChargeType` 1 | 2 | 3 — Guest’s transaction type at a hotel. Value|Description -----|----------- 1 | Lodging 2 | Restaurant 3 | Gift Shop
        - `specialCode` 1 | 2 | 3 | 4 | 5 | 6 — This field is used to provide additional detail for lodging transactions. If a lodging charge does not match one of the listed descriptions, the default value of ‘1’ should be sent in the request. When a value of ‘4’ is sent, the `additionalCharges` field needs to be sent as well. Value|Description -----|----------- 1 | No Special Code 2 | Assured Reservation/No Show 3 | Advance Deposit 4 | Delayed Charge 5 | Express Check-Out Service 6 | Assured Reservation/Normal
        - `additionalCharges` HotelAdditionalCharges — Reason codes for additional charges in a lodging sale request at the time a consumer checks out.
          - `giftShop` 'Y' | 'N'
          - `laundry` 'Y' | 'N'
          - `miniBar` 'Y' | 'N'
          - `other` 'Y' | 'N'
          - `restaurant` 'Y' | 'N'
          - `telephone` 'Y' | 'N'
        - `roomRates` HotelRoomRates[] — Room rates broken down by rate and number of nights.
          - `nights` integer — The number of nights being charged at this rate.
          - `rate` number — The per night room rate.
      - `purchaseCard` PurchaseCard, required
        - `customerReference` string, required — A unique value used to identify the consumer or transaction. If a merchant has a significant amount of revenue from purchasing card customers, the interface would use this field to collect the consumer’s purchase order or employee identification number. In lodging transactions, this may be unique transaction details, such as a reservation code or third-party booking source. This field is part of Level 2 card data.
        - `destinationPostalCode` string, required — When items are shipped, the ZIP/postal code to which merchandise will be shipped; otherwise, the ZIP/postal code where the goods or services are rendered. This field is part of Level 2 card data.
        - `productDescriptors` string[], required — A text description of the items purchased or services sold. This can be a generic text description of what the merchant sells (such as “Groceries”) or specific transaction data (such as the name of the item sold). At least one product descriptor field is required in a sale or authorization request. Note: The productDescriptors array is limited to 4 elements. Each element can contain a maximum of 40 characters.
      - `vendorReference` string — Optional field for information that can be searched in the merchant portal.
    - `device` object
      - `terminalId` string — This field is optional and is for backwards compatibility with existing vendors that are used to processing via UTG controlled devices. Since Commerce Engine is running directly on the payment device it does not require a `device.terminalId` to be specified.
    - `card` object
      - `present` 'Y' | 'N' — **Conditional: Send in the initial authorization/sale request** Indicates whether a card was present (‘Y’) or not (‘N’) at the time a transaction took place. This should be set appropriately in the initial authorization/sale request. In subsequent requests, this field should be left blank or should not be sent. **Note:** Subsequent request here does not apply to the secondary request for card on file type transactions or reuse of the same card. An example of a subsequent request would be a capture after an authorization. You would not include `card.present` in the capture, which is the subsequent request. Another example is when performing an incremental authorization where you perform an authorization, followed by an incremental authorization then a capture. The second authorization (incremental) and the capture are the subsequent requests where you would not include `card.present`.
      - `type` 'CC' | 'DB' | 'GC' | 'HF' | 'PL' | 'YC' — An abbreviation used to specify the type of card that will be used when processing a transaction. If an interface sends a value that is not listed here, that value will be ignored. Value| Description -----|------------ CC | When using a UTG-controlled device, this value will force a card to process as credit. DB | When using a UTG-controlled device, this value will force a card to process as debit. When using a non-UTG-controlled PIN pad, this value must be sent when processing a debit transaction. GC | Gift Card HF | HSA/FSA Card PL | Private Label YC | IT’S YOUR CARD
    - `customer` Customer
      - `addressLine1` string — Cardholder’s street address exactly as it appears on their billing statement. This field is used in AVS.
      - `firstName` string — Specifies a consumer’s first name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `middleName` string — Specifies a consumer’s middle name.
      - `lastName` string — Specifies a consumer’s last name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `postalCode` string — Cardholder’s ZIP/postal code from their billing statement. This field is used in AVS. Do not include special characters. **Note: This field only allows alphanumeric characters (a-z, A-Z, 0-9). Special characters including - are not allowed. If you are sending in zip+4 you must not include the dash so 89134-1234 would be sent as 891341234**
      - `emailAddress` string — Customer email address.
      - `ipAddress` string — Public source IP Address where the request originates, not the IP Address of the web server.
    - `receiptColumns` integer — Send this field if you want Shift4 to format the receipt text instead of returning individual fields. The value sent will correlate to the column width of the formatted receipt that we return. (This also allows the receipt text to wrap to fit the paper size of the printed receipt.) See the [Printing Receipts](/guides/core-concepts/printing-receipts) section of this document for more information on formatted receipts.
    - `currencyCode` string, ISO 4217 3 Character Alphabetic Code — Transaction currency code. See the [Currency Codes](/guides/appendices/currency-codes) section for details. **Note: This is currently supported when processing for a merchant outside of the US and Canada. If processing for a US or Canadian merchant then this field will be ignored and the transaction will process in the merchant's configured currency.**
    - `apiOptions` string[] — API Options modify the request being made. See the [API Options](/guides/appendices/api-options.md) section for more information.
    - `statementSuffix` string — Custom description that will be appended to the merchant name on the customer's statement. For most card brands, the merchant DBA name can be a maximum of 25 characters. Sending this value will cause the merchant name to be truncated to 9 characters. Shift4 will add an asterisk between the merchant name and the `statementSuffix` value. For example, for a merchant named `Joe's Warehouse Emporium` that processes a transaction with `statementSuffix` value of `KDNYZUHQ1`, the merchant statement will show as `Joe's War*KDNYZUHQ1`. **Note: The value that displays on customer statements from card issuers is beyond Shift4's control. We will submit the transaction data as described above, however issuers may modify or truncate that data as they see fit. To best accommodate different issuer limitations, we will truncate the merchant name to the minimum possible value (9 characters) in order to attempt to leave the most room for the statementSuffix to populate on issuer statements.**
    - `ui` object
      - `language` string — ISO 639-1 2-letter language code specifying the UI display language for the transaction (e.g. "en", "fr", "de"). When provided, overrides the device's configured default language for the duration of the session. Value persists across transactions until a new value is passed. Send default to reset the device back to its default language.
      - `mode` 'light' | 'dark' — Set the UI to light mode by sending `light` or dark mode by sending `dark`
      - `suppressFinalResult` boolean — When `true`, the terminal suppresses the final transaction result screen.
  - TransactionsManualsaleComengcloud
    - `dateTime` string, ISO 8601, required — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
    - `amount` AmountObjectNoSurcharge, required — Object containing information regarding the amount being requested. The `total` field within the object is required and specifies the amount being requested. All other fields are for informational purposes and must also be included in the `total` field. For example, a purchase of $100 with a $20 tip and $8 tax would be `128.00` in the `total` field, `20.00` in the `tip` field and `8.00` in the `tax` field. Note: For merchants that are configured to allow multiple currencies, the amount fields can specify up to three decimal places. However, the number of decimal places can not exceed the number allowed for the specified currency. See the [Currency Codes](/guides/appendices/currency-codes) section for details.
      - `total` number, required — The amount being charged for a particular transaction. If other amount fields are sent, they must be included in the total amount. Amount cannot be zero.
      - `tax` number, required — The amount of sales tax charged for a transaction. The tax amount is used by businesses to track tax expenses for accounting purposes. Identifying the tax amount also helps consumers understand the total amount that they were billed. This field is part of Level 2 card data.
      - `taxIndicator` 'Y' | 'N' — Value|Description -----|----------- Y | Tax is included N | Tax is not included
      - `cashback` number — Specifies the cashback amount in a transaction. When using a UTG-controlled PIN pad with the ALLOWCASHBACK API Option, this field will return the cashback amount requested by the consumer. The interface can also send the desired cashback amount in a request by adding it to the `amount.total` and including it in the `amount.cashback` field. This will bypass prompting the consumer for a cashback amount.
      - `iiasAmounts` IIASAmounts[] — **Conditional: Send in the request if processing for a health care merchant.** For Vision related charges you must send only `iiasAmounts.type = 4V` and the corresponding `iiasAmounts.amount` value. For all other charges, the first entry in the array should have an amount representing the total of all healthcare costs, and `iiasAmounts.type = 4S`. Any subsequent entries should contain the subtotal for each of the other expense types involved in this transaction.
        - `amount` number — The subtotal for this type of healthcare expenses.
        - `type` '4O' | '4S' | '4T' | '4U' | '4V' | '4W' | '4X' — This code classifies eligible healthcare expenses. Value|Description -----|----------- 4O | Cash Disbursement (Discover Only) – Amount of Cash Back Being Requested 4S | Healthcare (Visa/MC Only) – Qualified Medical Expenses or Over-the-Counter 4T | Transit (Visa Only) – Transit Fare Media (e.g., Commuter and Parking Passes, Mass Transit Vouchers, and Tickets) 4U | RX (Visa/MC Only) 4V | Vision (Visa Only) 4W | Clinical (Visa Only) 4X | Dental (Visa Only)
      - `tip` number — **Conditional: Send in the request if a tip is included.** The tip amount of the transaction.
      - `checkTotal` number — Optional field specifying the total amount of the entire bill/invoice that this transaction is part of. It can be larger than `amount.total` in scenarios where the check is being split or if a portion of the check was already paid in cash or another form of payment.
    - `clerk` Clerk, required
      - `numericId` integer, required — A number used to identify the point-of-sale (POS) or property management system (PMS) clerk or user. The value cannot be 0. An interface must be able to dynamically populate this field (not use a hardcoded value), unless the interface will be used exclusively for e-commerce.
    - `transaction` object, required
      - `invoice` string, required — 10-digit invoice number assigned by the interface to identify a transaction. An invoice number serves as a unique key that identifies a transaction within a batch in Shift4's Gateway. **Note: For US and Canadian processing: Although the invoice number is sent as a JSON string it is a numeric value. No alpha characters are allowed.** **For processing outside of the US and Canada alpha characters are allowed.**
      - `authorizationCode` string, required — The authorization code provided by the consumer’s issuing bank. It is provided in a response if an online authorization or sale request is approved. Following a referral response, it is also specified in [Manual Sale](/apis/payments-platform-rest/openapi/transactions/manualsale) requests.
      - `manualTranId` string — This is typically used in a Referral. If a ManualTranID is returned by the issuer with the Auth code, it should be sent to the processor in the ManualTranid field.
      - `notes` string — A free-form notes field that supports the use of HTML tags. This can be used for reference in [Lighthouse Transaction Manager](https://ltm.shift4test.com/) and is not sent to the authorization host. Escaped quotation marks should not be sent in the Notes field.
      - `businessDate` string, ISO 8601 — Desired business date of a transaction. Include when overriding the existing business date of a transaction. The overriding date may be earlier or later than the existing date. (yyyy-mm-dd)
      - `amex` TransactionAmex
        - `propertyCode` string — The code that contains a Merchant-assigned store or location number (or name) that uniquely identifies where the transaction took place.
      - `auto` AutoCheckOut — **Conditional: Utilize this object for Auto Rental transactions**
        - `distanceDriven` integer — The amount of distance the cardholder drove the vehicle.
        - `distanceUnit` 'M' | 'K' — The unit of measure that corresponds to the `distanceDriven` field. Value|Description -----|----------- M | Miles K | Kilometers
        - `lateAdjustment` number — A dollar amount for late adjustment fees for an auto rental, including refueling charges, a surcharge, or charges for damage incurred during use.
        - `noShowIndicator` 'Y' | 'N' — Indicates whether or not the cardholder picked up a reserved rental car. Value|Description -----|----------- Y | customer did not pick up the rental car N | customer did pick up the rental car
        - `additionalCharges` AutoAdditionalCharges — The codes used to provide a reason for additional charges in an auto rental sale. Multiple codes can be specified for the same transaction.
          - `gasoline` 'Y' | 'N'
          - `lateReturn` 'Y' | 'N'
          - `mileage` 'Y' | 'N'
          - `oneWayServiceFee` 'Y' | 'N'
          - `violationFee` 'Y' | 'N'
        - `driver` AutoDriver
          - `license` string — The cardholder's driver's license number.
          - `name` string — In a sale/authorization request for an auto rental, the customer’s name exactly as it appears on their driver’s license.
          - `taxNumber` string — This field contains the driver’s Tax Identification Number.
        - `rental` AutoRental — Information relating to where the rental card was picked up.
          - `agreement` string — Contract number for an auto rental agreement.
          - `city` string — City where rental car was picked up.
          - `countryCode` string — Country where rental card was picked up.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was picked up in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was picked up in U.S. postal abbreviation format.
        - `return` AutoReturn — Information relating to where the rental car was returned
          - `city` string — City where rental car was returned.
          - `countryCode` string — Country where rental card was returned.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was returned in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was returned in U.S. postal abbreviation format.
      - `airline` AirlineRequest — **Conditional: Utilize this object for Airline transactions in Authorization/Sale requests when possible. If unable to provide this data at Authorization, this object must be sent in subsequent Capture requests for the transaction.**
        - `carrierCode` string, required — The code of the airline carrier issuing the ticket.
        - `carrierName` string, required — The name of the airline carrier issuing the ticket.
        - `conjunctionTicketIndicator` 'Y' | 'N', required — Indicates whether the itinerary contains more than four segments of travel. Value | Description -------|------------------- Y | Yes N | No
        - `documentType` '01' | '02' | '03' | '04' | '05' | '06' | '07' | '08' | '09' | '10' | '11' | '12' | '13' | '14' | '15' | '16' | '17' | '18' | '19' | '20' | '21' | '22' | '23' | '24' | '25' | '26' | '27' | '28' | '29' | '30' | '31' | '32' | '33' | '34' | '35' | '36' | '37' | '38' | '39' | '41' | '42' | '43' | '44' | '45' | '46' | '47' | '48' | '49' | '50' | '51' | '52' | '60' | '64' | '65' | '66' | '67' | '68' | '69' | '70' | '71' | '72' | '73' | '74' | '75' | '76' | '77' | '78' | '79' | '80' | '81' | '82' | '83' | '84' | '85' | '86' | '87' | '88' | '89' | '90' | '91' | '92' | '93', required — This field contains the airline Document Type code, which indicates the purpose of this transaction. This information may appear on the descriptive bill on the Cardmember's statement, or be used to resolve billing inquiries and disputes. The codes entered in the Transaction Type and Document Type fields are used together to describe the purpose of this transaction. Value | Description ------|--------------- 01 | Passenger Ticket 02 | Additional Collection 03 | Excess Baggage 04 | Misc. Charge Order (MCO) / Prepaid Ticket Auth 05 | Special Service Ticket 06 | Supported Refund 07 | Unsupported Refund 08 | Lost Ticket Application 09 | Tour Order Voucher 10 | Ticket by Mail 11 | Undercharge Adjustment 12 | Group Ticket 13 | Exchange Adjustment 14 | SPD/Air Freight 15 | In-flight Adjustment 16 | Agency Passenger Ticket 17 | Agency Tour Order/Voucher 18 | Agency Misc. Charge Order (MCO) 19 | Agency Exchange Order 20 | Agency Group Ticket 21 | Debit Adjustment Duplicate Refund/Use 22 | In-flight Merchandise Ordered 23 | Catalogue Merchandise Ordered 24 | In-flight Phone Charges 25 | Frequent Flyer Fee/Purchase 26 | Kennel Charge 27 | Animal Transportation Charge 28 | Firearms Case 29 | Upgrade Charge 30 | Credit Unused Transportation 31 | Credit Class of Service Adjustment 32 | Credit Denied Boarding 33 | Credit Misc. Refund 34 | Credit Lost Ticket Refund 35 | Credit Exchange Refund 36 | Credit Overcharge Adjustment 37 | Credit Multiple Unused Tickets 38 | Exchange Order 39 | Self-Service Ticket(s) 41 | In-flight Duty Free Purchase 42 | Senior Citizen Discount Booklets 43 | Club Membership Fee 44 | Coupon Book 45 | In-flight Charges 46 | Tour Deposit 47 | Frequent Flyer Overnight Delivery Charge 48 | Frequent Flyer Fulfillment 49 | Small Package Delivery 50 | Vendor Sale 51 | Miscellaneous Tax(es) Fee(s) 52 | Travel Agency Fee 60 | Vendor Refund Credit 64 | Duty Free Sale 65 | Preferred Seat Upgrade 66 | Cabin Upgrade 67 | Lounge/Club Access or Day Pass 68 | Agent Assisted Reservation. Ticketing Fee 69 | Ticket Change or Cancel Fee 70 | Trip Insurance 71 | Unaccompanied Minor 72 | Standby Fee 73 | Curbside Baggage 74 | Inflight Medical Equipment 75 | Ticket or Pass Print Fee 76 | Checked Sporting/Special Equipment 77 | Dry Ice Fee 78 | Mail/Postage Fee 79 | Club Membership Fee - Temporary/Trial 80 | Frequent Flyer Activation/Reinstatement 81 | Gift Certificate 82 | Onboard/Inflight Prepaid Voucher 83 | Optional Services Fee 84 | Advanced Purchase - Excess Baggage 85 | Advanced Purchase - Preferred Seat Upgrade 86 | Advanced Purchase - Cabin Upgrade 87 | Advanced Purchase - Optional Services 88 | WiFi 89 | Packages 90 | Inflight Entertainment/Internet Access 91 | Overweight Bag Fee 92 | Sleep Sets 93 | Special Purchase Fee
        - `electronicTicketIndicator` 'Y' | 'N', required — Indicates if an electronic ticket was issued. Value | Description -------|------------------- Y | Yes N | No
        - `internetIndicator` 'Y' | 'N', required — Indicates if this is an internet transaction. Value | Description -------|------------------- Y | Yes N | No
        - `issueDate` string, ISO 8601, required — The date the ticket was issued to the customer. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `numberOfCities` number, required — The number of airports or cities for each leg on the ticket (including origination and destination cities).
        - `numberOfCarriers` number, required — This field contains the number of airline carriers.
        - `numberOfPassengers` number, required — The number of passengers in the transaction.
        - `passengerArrivalDate` string, ISO 8601, required — Date that the ticket holder is scheduled to arrive at their destination at the time of issuance of the original ticket. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerDepartureDate` string, ISO 8601, required — Date that the ticket holder is scheduled to depart at the time of issuance of the original ticket. The date may be a future one. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerNameRecord` string, required — A passenger name record (PNR) is a record in the database of a computer reservation system (CRS) that contains the itinerary for a passenger or a group of passengers travelling together
        - `restrictedTicketIndicator` '0' | '1', required — Indicates whether this ticket is non-refundable. Value | Description -------|------------------- 0 | No restriction 1 | Restricted (non-refundable) ticket
        - `ticketChangeIndicator` 'C' | 'N', required — Indicates why a ticket was changed. This field should contain spaces or one of the below codes. Value | Description -------|--------------- C | Change to existing ticket N | New ticket
        - `ticketTranType` 'TKT' | 'REF' | 'EXC' | 'MSC', required — This field contains the ticket transaction type code assigned to this transaction. Value | Description -------|--------------- TKT | Ticket Purchase REF | Refund EXC | Exchange Ticket MSC | Miscellaneous (non-Ticket Purchase- and non-Exchange Ticket-related transactions only)
        - `typeIndicator` 'R' | 'O' | 'M', required — Indicates if this ticket is a round trip, multi-city, or one-way ticket. Value | Description -------|--------------- R | Round-Trip O | One Way M | Multi-City
        - `tickets` AirlineTickets[], required — Array of ticket number and passenger name. Note: At least one instance of ticket number and passenger name info should be provided.
          - `passengerName` string, required — Name of the passenger to whom the ticket was issued. This field contains the Passenger Name in format: `SURNAME FIRSTNAME MIDDLEINITIAL TITLE` Example: "Doe Jane M Mrs"
          - `ticketNumber` string, required — The ticket number provided by the Carrier for the passenger.
          - `ticketFare` number, required — Ticket fare is the total amount for each ticket, including service fee or any other fee for each ticket.
        - `flightLegs` AirlineFlightLegs[], required — Array of flight trip leg info. Maximun 4 legs to a trip allowed. Note: At least one instance of flight trip leg info should be provided.
          - `carrierCode` string, required — Code indicating name of carrier (United Airlines, Jet Blue, etc.) for the leg.
          - `couponNumber` number — Number of coupons in the ticket for the leg.
          - `destAirportCode` string, required — Indicates destination city's airport code for the leg.
          - `fare` number, required — This field contains the total Fare for this trip segment. This is not the total amount billed to the customer.
          - `fareBasis` string, required — This field contains primary and secondary discount codes that indicate the class of service and fare level associated with the ticket for the leg. Truncate at 24 bytes, if necessary.
          - `flightNumber` string, required — Number of the airline flight to be taken on Leg of the trip.
          - `legArrivalDateTime` string, ISO 8601, required — The date and time the flight is scheduled to arrive for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `legDepartureDateTime` string, ISO 8601, required — The date and time the flight is scheduled to depart for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `originAirportCode` string, required — Indicates origination city's airport code for the leg.
          - `serviceClass` string, required — Indicates service class for leg. Value | Description -------|--------------- FC | First Class BC | Business Class EC | Economy/Coach Class
          - `stopOverCode` string, required — Indicates whether a stopover is allowed on this ticket for leg. The entry must be a D, O, or X. Value | Description -------|--------------- O | Stopover allowed X | Stopover not allowed D | Destination point
          - `tripLegInfo` string, required — Description of leg or stage of trip.
        - `ancillaryServices` AirlineAncillaryServices[] — Array of ancillary service code and fees. **Conditional: Send if any ancillary services were charged.**
          - `serviceCode` 'BF' | 'BG' | 'CF' | 'CG' | 'CO' | 'FF' | 'GF' | 'GT' | 'IE' | 'LG' | 'MD' | 'ML' | 'OT' | 'PA' | 'PT' | 'SA' | 'SB' | 'SF' | 'ST' | 'TS' | 'UN' | 'UP' | 'WI', required — This field describes the type of service that has been provided. Value | Description ------|--------------- BF | Bundled Service BG | Baggage Fee CF | Change Fee CG | Cargo CO | Carbon Offset FF | Frequent Flyer GF | Gift Card GT | Ground Transport IE | In-Flight Entertainment LG | Lounge MD | Medical ML | Meal/Beverage OT | Other PA | Passenger Assist Fee PT | Pets SA | Seat Fees SB | Standby SF | Service Fee ST | Store TS | Travel Service UN | Unaccompanied Travel UP | Upgrades WI | Wi-Fi
          - `serviceFee` number, required — This field contains the amount associated with the value provided in ancillary Service Code.
        - `travelAgencyCode` string — Code identifying travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `travelAgencyName` string — Name of travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `exchangeTicketNumber` string — The original ticket number that was replaced by a new ticket number.
      - `cardOnFile` CardOnFile — **Conditional: Send this object when the transaction being performed is using a card on file or when the request will result in storing a card on file.** See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for more information.
        - `type` 'S01' | 'S02' | 'U01' | 'U02' | 'U03' | 'U04' | 'U05' | 'U06' | 'U07' | 'U08' | 'U09' — This field specifies the type of the card-on-file transaction. Below is a table showing the valid values for use cases where the cardholder is entering their card data to store on file. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | S01 | Cardholder | No | Yes | Used when the initial transaction/card verification request is not for a recurring payment. | | S02 | Cardholder | Yes | Yes | Used when the initial transaction/card verification request is for a recurring payment. Requires sending `cardOnFile.recurringFrequency` and `cardOnFile.recurringExpiry` | Below is a table showing the valid values for uses cases where you already have a card on file and are using that existing card to process a transaction. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | U01 | Cardholder | No | Yes | Unscheduled transaction using the card on file initiated by the cardholder | | U02 | Merchant | No | No | Unscheduled transaction using the card on file initiated by the merchant | | U03 | Merchant | Yes | No | Merchant initiated recurring payment using the card on file | | U04 | Merchant | No | No | Identifies a transaction as a Reauthorization COF transaction. | | U05 | Merchant | No | No | Identifies a transaction as a Resubmission COF transaction. Only certain merchant categories are able to send a resubmission, and it can only be done if the original authorization attempt was declined due to insufficient funds. | | U06 | Merchant | No | No | Identifies a transaction as an Estimated Authorization COF transaction. | | U07 | Merchant | No | No | Identifies a transaction as a Delayed Charges COF transaction. For example, a hotel might charge a customer for room damages after the guest has already checked out. | | U08 | Merchant | No | No | Identifies a transaction as an Incremental COF transaction. For example, a hotel which authorized a customer’s card for one night at check-in might increase the authorization amount to cover two nights when the customer decides to extend their stay. Shift4 automatically detects this scenario and sends the appropriate value to the processor. | | U09 | Merchant | No | No | Identifies a transaction as a No Show COF transaction. For example, a hotel might charge a customer who does not show up for a booked stay. | See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for additional details.
        - `recurringExpiry` string — Date after which no further authorizations shall be performed. This field is limited to 8 characters, and the accepted format is YYYYMMDD. **Conditional: This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `recurringFrequency` string — Indicates the minimum number of days between authorizations. **Conditional: 'This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `transactionId` string — This field is returned in the initial COF response, and ties subsequent COF transactions to the original authorization. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
        - `transactionLinkId` string — A unique identifier assigned to each transaction to link related events throughout the transaction lifecycle. This field is supported for Mastercard brand only. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionLinkId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionLinkId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
      - `hotel` HotelCheckOut — **Conditional: Utilize this object for Hotel transactions**
        - `arrivalDateTime` string — Arrival date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the arrival date needs to be one day before the sale date.
        - `departureDateTime` string — Departure date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the departure date needs to be the day of the sale.
        - `primaryChargeType` 1 | 2 | 3 — Guest’s transaction type at a hotel. Value|Description -----|----------- 1 | Lodging 2 | Restaurant 3 | Gift Shop
        - `specialCode` 1 | 2 | 3 | 4 | 5 | 6 — This field is used to provide additional detail for lodging transactions. If a lodging charge does not match one of the listed descriptions, the default value of ‘1’ should be sent in the request. When a value of ‘4’ is sent, the `additionalCharges` field needs to be sent as well. Value|Description -----|----------- 1 | No Special Code 2 | Assured Reservation/No Show 3 | Advance Deposit 4 | Delayed Charge 5 | Express Check-Out Service 6 | Assured Reservation/Normal
        - `additionalCharges` HotelAdditionalCharges — Reason codes for additional charges in a lodging sale request at the time a consumer checks out.
          - `giftShop` 'Y' | 'N'
          - `laundry` 'Y' | 'N'
          - `miniBar` 'Y' | 'N'
          - `other` 'Y' | 'N'
          - `restaurant` 'Y' | 'N'
          - `telephone` 'Y' | 'N'
        - `roomRates` HotelRoomRates[] — Room rates broken down by rate and number of nights.
          - `nights` integer — The number of nights being charged at this rate.
          - `rate` number — The per night room rate.
      - `purchaseCard` PurchaseCard, required
        - `customerReference` string, required — A unique value used to identify the consumer or transaction. If a merchant has a significant amount of revenue from purchasing card customers, the interface would use this field to collect the consumer’s purchase order or employee identification number. In lodging transactions, this may be unique transaction details, such as a reservation code or third-party booking source. This field is part of Level 2 card data.
        - `destinationPostalCode` string, required — When items are shipped, the ZIP/postal code to which merchandise will be shipped; otherwise, the ZIP/postal code where the goods or services are rendered. This field is part of Level 2 card data.
        - `productDescriptors` string[], required — A text description of the items purchased or services sold. This can be a generic text description of what the merchant sells (such as “Groceries”) or specific transaction data (such as the name of the item sold). At least one product descriptor field is required in a sale or authorization request. Note: The productDescriptors array is limited to 4 elements. Each element can contain a maximum of 40 characters.
      - `vendorReference` string — Optional field for information that can be searched in the merchant portal.
    - `device` DeviceCommerceEngineCloud, required
      - `cloud` boolean, required — Indicates the transaction will be processed via the Commerce Engine solution for cloud based POS/PMS systems. Value must be sent as `true` in order to route the request to the payment device at the merchant location.
      - `manufacturer` 'Ingenico' | 'Innowi' | 'PAX' | 'Verifone' | 'Castles' | 'Miura', required — Specifies the company which manufactured the device.
      - `serialNumber` string, required — Specifies the serial number of the device.
    - `card` object
      - `present` 'Y' | 'N' — **Conditional: Send in the initial authorization/sale request** Indicates whether a card was present (‘Y’) or not (‘N’) at the time a transaction took place. This should be set appropriately in the initial authorization/sale request. In subsequent requests, this field should be left blank or should not be sent. **Note:** Subsequent request here does not apply to the secondary request for card on file type transactions or reuse of the same card. An example of a subsequent request would be a capture after an authorization. You would not include `card.present` in the capture, which is the subsequent request. Another example is when performing an incremental authorization where you perform an authorization, followed by an incremental authorization then a capture. The second authorization (incremental) and the capture are the subsequent requests where you would not include `card.present`.
      - `type` 'CC' | 'DB' | 'GC' | 'HF' | 'PL' | 'YC' — An abbreviation used to specify the type of card that will be used when processing a transaction. If an interface sends a value that is not listed here, that value will be ignored. Value| Description -----|------------ CC | When using a UTG-controlled device, this value will force a card to process as credit. DB | When using a UTG-controlled device, this value will force a card to process as debit. When using a non-UTG-controlled PIN pad, this value must be sent when processing a debit transaction. GC | Gift Card HF | HSA/FSA Card PL | Private Label YC | IT’S YOUR CARD
    - `customer` Customer
      - `addressLine1` string — Cardholder’s street address exactly as it appears on their billing statement. This field is used in AVS.
      - `firstName` string — Specifies a consumer’s first name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `middleName` string — Specifies a consumer’s middle name.
      - `lastName` string — Specifies a consumer’s last name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `postalCode` string — Cardholder’s ZIP/postal code from their billing statement. This field is used in AVS. Do not include special characters. **Note: This field only allows alphanumeric characters (a-z, A-Z, 0-9). Special characters including - are not allowed. If you are sending in zip+4 you must not include the dash so 89134-1234 would be sent as 891341234**
      - `emailAddress` string — Customer email address.
      - `ipAddress` string — Public source IP Address where the request originates, not the IP Address of the web server.
    - `receiptColumns` integer — Send this field if you want Shift4 to format the receipt text instead of returning individual fields. The value sent will correlate to the column width of the formatted receipt that we return. (This also allows the receipt text to wrap to fit the paper size of the printed receipt.) See the [Printing Receipts](/guides/core-concepts/printing-receipts) section of this document for more information on formatted receipts.
    - `currencyCode` string, ISO 4217 3 Character Alphabetic Code — Transaction currency code. See the [Currency Codes](/guides/appendices/currency-codes) section for details. **Note: This is currently supported when processing for a merchant outside of the US and Canada. If processing for a US or Canadian merchant then this field will be ignored and the transaction will process in the merchant's configured currency.**
    - `apiOptions` string[] — API Options modify the request being made. See the [API Options](/guides/appendices/api-options.md) section for more information.
    - `statementSuffix` string — Custom description that will be appended to the merchant name on the customer's statement. For most card brands, the merchant DBA name can be a maximum of 25 characters. Sending this value will cause the merchant name to be truncated to 9 characters. Shift4 will add an asterisk between the merchant name and the `statementSuffix` value. For example, for a merchant named `Joe's Warehouse Emporium` that processes a transaction with `statementSuffix` value of `KDNYZUHQ1`, the merchant statement will show as `Joe's War*KDNYZUHQ1`. **Note: The value that displays on customer statements from card issuers is beyond Shift4's control. We will submit the transaction data as described above, however issuers may modify or truncate that data as they see fit. To best accommodate different issuer limitations, we will truncate the merchant name to the minimum possible value (9 characters) in order to attempt to leave the most room for the statementSuffix to populate on issuer statements.**
    - `ui` object
      - `language` string — ISO 639-1 2-letter language code specifying the UI display language for the transaction (e.g. "en", "fr", "de"). When provided, overrides the device's configured default language for the duration of the session. Value persists across transactions until a new value is passed. Send default to reset the device back to its default language.
      - `mode` 'light' | 'dark' — Set the UI to light mode by sending `light` or dark mode by sending `dark`
      - `suppressFinalResult` boolean — When `true`, the terminal suppresses the final transaction result screen.
  - TransactionsManualsaleUtgdevice
    - `dateTime` string, ISO 8601, required — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
    - `amount` AmountObjectNoSurcharge, required — Object containing information regarding the amount being requested. The `total` field within the object is required and specifies the amount being requested. All other fields are for informational purposes and must also be included in the `total` field. For example, a purchase of $100 with a $20 tip and $8 tax would be `128.00` in the `total` field, `20.00` in the `tip` field and `8.00` in the `tax` field. Note: For merchants that are configured to allow multiple currencies, the amount fields can specify up to three decimal places. However, the number of decimal places can not exceed the number allowed for the specified currency. See the [Currency Codes](/guides/appendices/currency-codes) section for details.
      - `total` number, required — The amount being charged for a particular transaction. If other amount fields are sent, they must be included in the total amount. Amount cannot be zero.
      - `tax` number, required — The amount of sales tax charged for a transaction. The tax amount is used by businesses to track tax expenses for accounting purposes. Identifying the tax amount also helps consumers understand the total amount that they were billed. This field is part of Level 2 card data.
      - `taxIndicator` 'Y' | 'N' — Value|Description -----|----------- Y | Tax is included N | Tax is not included
      - `cashback` number — Specifies the cashback amount in a transaction. When using a UTG-controlled PIN pad with the ALLOWCASHBACK API Option, this field will return the cashback amount requested by the consumer. The interface can also send the desired cashback amount in a request by adding it to the `amount.total` and including it in the `amount.cashback` field. This will bypass prompting the consumer for a cashback amount.
      - `iiasAmounts` IIASAmounts[] — **Conditional: Send in the request if processing for a health care merchant.** For Vision related charges you must send only `iiasAmounts.type = 4V` and the corresponding `iiasAmounts.amount` value. For all other charges, the first entry in the array should have an amount representing the total of all healthcare costs, and `iiasAmounts.type = 4S`. Any subsequent entries should contain the subtotal for each of the other expense types involved in this transaction.
        - `amount` number — The subtotal for this type of healthcare expenses.
        - `type` '4O' | '4S' | '4T' | '4U' | '4V' | '4W' | '4X' — This code classifies eligible healthcare expenses. Value|Description -----|----------- 4O | Cash Disbursement (Discover Only) – Amount of Cash Back Being Requested 4S | Healthcare (Visa/MC Only) – Qualified Medical Expenses or Over-the-Counter 4T | Transit (Visa Only) – Transit Fare Media (e.g., Commuter and Parking Passes, Mass Transit Vouchers, and Tickets) 4U | RX (Visa/MC Only) 4V | Vision (Visa Only) 4W | Clinical (Visa Only) 4X | Dental (Visa Only)
      - `tip` number — **Conditional: Send in the request if a tip is included.** The tip amount of the transaction.
      - `checkTotal` number — Optional field specifying the total amount of the entire bill/invoice that this transaction is part of. It can be larger than `amount.total` in scenarios where the check is being split or if a portion of the check was already paid in cash or another form of payment.
    - `clerk` Clerk, required
      - `numericId` integer, required — A number used to identify the point-of-sale (POS) or property management system (PMS) clerk or user. The value cannot be 0. An interface must be able to dynamically populate this field (not use a hardcoded value), unless the interface will be used exclusively for e-commerce.
    - `transaction` object, required
      - `invoice` string, required — 10-digit invoice number assigned by the interface to identify a transaction. An invoice number serves as a unique key that identifies a transaction within a batch in Shift4's Gateway. **Note: For US and Canadian processing: Although the invoice number is sent as a JSON string it is a numeric value. No alpha characters are allowed.** **For processing outside of the US and Canada alpha characters are allowed.**
      - `authorizationCode` string, required — The authorization code provided by the consumer’s issuing bank. It is provided in a response if an online authorization or sale request is approved. Following a referral response, it is also specified in [Manual Sale](/apis/payments-platform-rest/openapi/transactions/manualsale) requests.
      - `manualTranId` string — This is typically used in a Referral. If a ManualTranID is returned by the issuer with the Auth code, it should be sent to the processor in the ManualTranid field.
      - `notes` string — A free-form notes field that supports the use of HTML tags. This can be used for reference in [Lighthouse Transaction Manager](https://ltm.shift4test.com/) and is not sent to the authorization host. Escaped quotation marks should not be sent in the Notes field.
      - `businessDate` string, ISO 8601 — Desired business date of a transaction. Include when overriding the existing business date of a transaction. The overriding date may be earlier or later than the existing date. (yyyy-mm-dd)
      - `amex` TransactionAmex
        - `propertyCode` string — The code that contains a Merchant-assigned store or location number (or name) that uniquely identifies where the transaction took place.
      - `auto` AutoCheckOut — **Conditional: Utilize this object for Auto Rental transactions**
        - `distanceDriven` integer — The amount of distance the cardholder drove the vehicle.
        - `distanceUnit` 'M' | 'K' — The unit of measure that corresponds to the `distanceDriven` field. Value|Description -----|----------- M | Miles K | Kilometers
        - `lateAdjustment` number — A dollar amount for late adjustment fees for an auto rental, including refueling charges, a surcharge, or charges for damage incurred during use.
        - `noShowIndicator` 'Y' | 'N' — Indicates whether or not the cardholder picked up a reserved rental car. Value|Description -----|----------- Y | customer did not pick up the rental car N | customer did pick up the rental car
        - `additionalCharges` AutoAdditionalCharges — The codes used to provide a reason for additional charges in an auto rental sale. Multiple codes can be specified for the same transaction.
          - `gasoline` 'Y' | 'N'
          - `lateReturn` 'Y' | 'N'
          - `mileage` 'Y' | 'N'
          - `oneWayServiceFee` 'Y' | 'N'
          - `violationFee` 'Y' | 'N'
        - `driver` AutoDriver
          - `license` string — The cardholder's driver's license number.
          - `name` string — In a sale/authorization request for an auto rental, the customer’s name exactly as it appears on their driver’s license.
          - `taxNumber` string — This field contains the driver’s Tax Identification Number.
        - `rental` AutoRental — Information relating to where the rental card was picked up.
          - `agreement` string — Contract number for an auto rental agreement.
          - `city` string — City where rental car was picked up.
          - `countryCode` string — Country where rental card was picked up.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was picked up in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was picked up in U.S. postal abbreviation format.
        - `return` AutoReturn — Information relating to where the rental car was returned
          - `city` string — City where rental car was returned.
          - `countryCode` string — Country where rental card was returned.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was returned in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was returned in U.S. postal abbreviation format.
      - `airline` AirlineRequest — **Conditional: Utilize this object for Airline transactions in Authorization/Sale requests when possible. If unable to provide this data at Authorization, this object must be sent in subsequent Capture requests for the transaction.**
        - `carrierCode` string, required — The code of the airline carrier issuing the ticket.
        - `carrierName` string, required — The name of the airline carrier issuing the ticket.
        - `conjunctionTicketIndicator` 'Y' | 'N', required — Indicates whether the itinerary contains more than four segments of travel. Value | Description -------|------------------- Y | Yes N | No
        - `documentType` '01' | '02' | '03' | '04' | '05' | '06' | '07' | '08' | '09' | '10' | '11' | '12' | '13' | '14' | '15' | '16' | '17' | '18' | '19' | '20' | '21' | '22' | '23' | '24' | '25' | '26' | '27' | '28' | '29' | '30' | '31' | '32' | '33' | '34' | '35' | '36' | '37' | '38' | '39' | '41' | '42' | '43' | '44' | '45' | '46' | '47' | '48' | '49' | '50' | '51' | '52' | '60' | '64' | '65' | '66' | '67' | '68' | '69' | '70' | '71' | '72' | '73' | '74' | '75' | '76' | '77' | '78' | '79' | '80' | '81' | '82' | '83' | '84' | '85' | '86' | '87' | '88' | '89' | '90' | '91' | '92' | '93', required — This field contains the airline Document Type code, which indicates the purpose of this transaction. This information may appear on the descriptive bill on the Cardmember's statement, or be used to resolve billing inquiries and disputes. The codes entered in the Transaction Type and Document Type fields are used together to describe the purpose of this transaction. Value | Description ------|--------------- 01 | Passenger Ticket 02 | Additional Collection 03 | Excess Baggage 04 | Misc. Charge Order (MCO) / Prepaid Ticket Auth 05 | Special Service Ticket 06 | Supported Refund 07 | Unsupported Refund 08 | Lost Ticket Application 09 | Tour Order Voucher 10 | Ticket by Mail 11 | Undercharge Adjustment 12 | Group Ticket 13 | Exchange Adjustment 14 | SPD/Air Freight 15 | In-flight Adjustment 16 | Agency Passenger Ticket 17 | Agency Tour Order/Voucher 18 | Agency Misc. Charge Order (MCO) 19 | Agency Exchange Order 20 | Agency Group Ticket 21 | Debit Adjustment Duplicate Refund/Use 22 | In-flight Merchandise Ordered 23 | Catalogue Merchandise Ordered 24 | In-flight Phone Charges 25 | Frequent Flyer Fee/Purchase 26 | Kennel Charge 27 | Animal Transportation Charge 28 | Firearms Case 29 | Upgrade Charge 30 | Credit Unused Transportation 31 | Credit Class of Service Adjustment 32 | Credit Denied Boarding 33 | Credit Misc. Refund 34 | Credit Lost Ticket Refund 35 | Credit Exchange Refund 36 | Credit Overcharge Adjustment 37 | Credit Multiple Unused Tickets 38 | Exchange Order 39 | Self-Service Ticket(s) 41 | In-flight Duty Free Purchase 42 | Senior Citizen Discount Booklets 43 | Club Membership Fee 44 | Coupon Book 45 | In-flight Charges 46 | Tour Deposit 47 | Frequent Flyer Overnight Delivery Charge 48 | Frequent Flyer Fulfillment 49 | Small Package Delivery 50 | Vendor Sale 51 | Miscellaneous Tax(es) Fee(s) 52 | Travel Agency Fee 60 | Vendor Refund Credit 64 | Duty Free Sale 65 | Preferred Seat Upgrade 66 | Cabin Upgrade 67 | Lounge/Club Access or Day Pass 68 | Agent Assisted Reservation. Ticketing Fee 69 | Ticket Change or Cancel Fee 70 | Trip Insurance 71 | Unaccompanied Minor 72 | Standby Fee 73 | Curbside Baggage 74 | Inflight Medical Equipment 75 | Ticket or Pass Print Fee 76 | Checked Sporting/Special Equipment 77 | Dry Ice Fee 78 | Mail/Postage Fee 79 | Club Membership Fee - Temporary/Trial 80 | Frequent Flyer Activation/Reinstatement 81 | Gift Certificate 82 | Onboard/Inflight Prepaid Voucher 83 | Optional Services Fee 84 | Advanced Purchase - Excess Baggage 85 | Advanced Purchase - Preferred Seat Upgrade 86 | Advanced Purchase - Cabin Upgrade 87 | Advanced Purchase - Optional Services 88 | WiFi 89 | Packages 90 | Inflight Entertainment/Internet Access 91 | Overweight Bag Fee 92 | Sleep Sets 93 | Special Purchase Fee
        - `electronicTicketIndicator` 'Y' | 'N', required — Indicates if an electronic ticket was issued. Value | Description -------|------------------- Y | Yes N | No
        - `internetIndicator` 'Y' | 'N', required — Indicates if this is an internet transaction. Value | Description -------|------------------- Y | Yes N | No
        - `issueDate` string, ISO 8601, required — The date the ticket was issued to the customer. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `numberOfCities` number, required — The number of airports or cities for each leg on the ticket (including origination and destination cities).
        - `numberOfCarriers` number, required — This field contains the number of airline carriers.
        - `numberOfPassengers` number, required — The number of passengers in the transaction.
        - `passengerArrivalDate` string, ISO 8601, required — Date that the ticket holder is scheduled to arrive at their destination at the time of issuance of the original ticket. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerDepartureDate` string, ISO 8601, required — Date that the ticket holder is scheduled to depart at the time of issuance of the original ticket. The date may be a future one. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerNameRecord` string, required — A passenger name record (PNR) is a record in the database of a computer reservation system (CRS) that contains the itinerary for a passenger or a group of passengers travelling together
        - `restrictedTicketIndicator` '0' | '1', required — Indicates whether this ticket is non-refundable. Value | Description -------|------------------- 0 | No restriction 1 | Restricted (non-refundable) ticket
        - `ticketChangeIndicator` 'C' | 'N', required — Indicates why a ticket was changed. This field should contain spaces or one of the below codes. Value | Description -------|--------------- C | Change to existing ticket N | New ticket
        - `ticketTranType` 'TKT' | 'REF' | 'EXC' | 'MSC', required — This field contains the ticket transaction type code assigned to this transaction. Value | Description -------|--------------- TKT | Ticket Purchase REF | Refund EXC | Exchange Ticket MSC | Miscellaneous (non-Ticket Purchase- and non-Exchange Ticket-related transactions only)
        - `typeIndicator` 'R' | 'O' | 'M', required — Indicates if this ticket is a round trip, multi-city, or one-way ticket. Value | Description -------|--------------- R | Round-Trip O | One Way M | Multi-City
        - `tickets` AirlineTickets[], required — Array of ticket number and passenger name. Note: At least one instance of ticket number and passenger name info should be provided.
          - `passengerName` string, required — Name of the passenger to whom the ticket was issued. This field contains the Passenger Name in format: `SURNAME FIRSTNAME MIDDLEINITIAL TITLE` Example: "Doe Jane M Mrs"
          - `ticketNumber` string, required — The ticket number provided by the Carrier for the passenger.
          - `ticketFare` number, required — Ticket fare is the total amount for each ticket, including service fee or any other fee for each ticket.
        - `flightLegs` AirlineFlightLegs[], required — Array of flight trip leg info. Maximun 4 legs to a trip allowed. Note: At least one instance of flight trip leg info should be provided.
          - `carrierCode` string, required — Code indicating name of carrier (United Airlines, Jet Blue, etc.) for the leg.
          - `couponNumber` number — Number of coupons in the ticket for the leg.
          - `destAirportCode` string, required — Indicates destination city's airport code for the leg.
          - `fare` number, required — This field contains the total Fare for this trip segment. This is not the total amount billed to the customer.
          - `fareBasis` string, required — This field contains primary and secondary discount codes that indicate the class of service and fare level associated with the ticket for the leg. Truncate at 24 bytes, if necessary.
          - `flightNumber` string, required — Number of the airline flight to be taken on Leg of the trip.
          - `legArrivalDateTime` string, ISO 8601, required — The date and time the flight is scheduled to arrive for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `legDepartureDateTime` string, ISO 8601, required — The date and time the flight is scheduled to depart for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `originAirportCode` string, required — Indicates origination city's airport code for the leg.
          - `serviceClass` string, required — Indicates service class for leg. Value | Description -------|--------------- FC | First Class BC | Business Class EC | Economy/Coach Class
          - `stopOverCode` string, required — Indicates whether a stopover is allowed on this ticket for leg. The entry must be a D, O, or X. Value | Description -------|--------------- O | Stopover allowed X | Stopover not allowed D | Destination point
          - `tripLegInfo` string, required — Description of leg or stage of trip.
        - `ancillaryServices` AirlineAncillaryServices[] — Array of ancillary service code and fees. **Conditional: Send if any ancillary services were charged.**
          - `serviceCode` 'BF' | 'BG' | 'CF' | 'CG' | 'CO' | 'FF' | 'GF' | 'GT' | 'IE' | 'LG' | 'MD' | 'ML' | 'OT' | 'PA' | 'PT' | 'SA' | 'SB' | 'SF' | 'ST' | 'TS' | 'UN' | 'UP' | 'WI', required — This field describes the type of service that has been provided. Value | Description ------|--------------- BF | Bundled Service BG | Baggage Fee CF | Change Fee CG | Cargo CO | Carbon Offset FF | Frequent Flyer GF | Gift Card GT | Ground Transport IE | In-Flight Entertainment LG | Lounge MD | Medical ML | Meal/Beverage OT | Other PA | Passenger Assist Fee PT | Pets SA | Seat Fees SB | Standby SF | Service Fee ST | Store TS | Travel Service UN | Unaccompanied Travel UP | Upgrades WI | Wi-Fi
          - `serviceFee` number, required — This field contains the amount associated with the value provided in ancillary Service Code.
        - `travelAgencyCode` string — Code identifying travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `travelAgencyName` string — Name of travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `exchangeTicketNumber` string — The original ticket number that was replaced by a new ticket number.
      - `cardOnFile` CardOnFile — **Conditional: Send this object when the transaction being performed is using a card on file or when the request will result in storing a card on file.** See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for more information.
        - `type` 'S01' | 'S02' | 'U01' | 'U02' | 'U03' | 'U04' | 'U05' | 'U06' | 'U07' | 'U08' | 'U09' — This field specifies the type of the card-on-file transaction. Below is a table showing the valid values for use cases where the cardholder is entering their card data to store on file. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | S01 | Cardholder | No | Yes | Used when the initial transaction/card verification request is not for a recurring payment. | | S02 | Cardholder | Yes | Yes | Used when the initial transaction/card verification request is for a recurring payment. Requires sending `cardOnFile.recurringFrequency` and `cardOnFile.recurringExpiry` | Below is a table showing the valid values for uses cases where you already have a card on file and are using that existing card to process a transaction. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | U01 | Cardholder | No | Yes | Unscheduled transaction using the card on file initiated by the cardholder | | U02 | Merchant | No | No | Unscheduled transaction using the card on file initiated by the merchant | | U03 | Merchant | Yes | No | Merchant initiated recurring payment using the card on file | | U04 | Merchant | No | No | Identifies a transaction as a Reauthorization COF transaction. | | U05 | Merchant | No | No | Identifies a transaction as a Resubmission COF transaction. Only certain merchant categories are able to send a resubmission, and it can only be done if the original authorization attempt was declined due to insufficient funds. | | U06 | Merchant | No | No | Identifies a transaction as an Estimated Authorization COF transaction. | | U07 | Merchant | No | No | Identifies a transaction as a Delayed Charges COF transaction. For example, a hotel might charge a customer for room damages after the guest has already checked out. | | U08 | Merchant | No | No | Identifies a transaction as an Incremental COF transaction. For example, a hotel which authorized a customer’s card for one night at check-in might increase the authorization amount to cover two nights when the customer decides to extend their stay. Shift4 automatically detects this scenario and sends the appropriate value to the processor. | | U09 | Merchant | No | No | Identifies a transaction as a No Show COF transaction. For example, a hotel might charge a customer who does not show up for a booked stay. | See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for additional details.
        - `recurringExpiry` string — Date after which no further authorizations shall be performed. This field is limited to 8 characters, and the accepted format is YYYYMMDD. **Conditional: This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `recurringFrequency` string — Indicates the minimum number of days between authorizations. **Conditional: 'This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `transactionId` string — This field is returned in the initial COF response, and ties subsequent COF transactions to the original authorization. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
        - `transactionLinkId` string — A unique identifier assigned to each transaction to link related events throughout the transaction lifecycle. This field is supported for Mastercard brand only. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionLinkId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionLinkId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
      - `hotel` HotelCheckOut — **Conditional: Utilize this object for Hotel transactions**
        - `arrivalDateTime` string — Arrival date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the arrival date needs to be one day before the sale date.
        - `departureDateTime` string — Departure date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the departure date needs to be the day of the sale.
        - `primaryChargeType` 1 | 2 | 3 — Guest’s transaction type at a hotel. Value|Description -----|----------- 1 | Lodging 2 | Restaurant 3 | Gift Shop
        - `specialCode` 1 | 2 | 3 | 4 | 5 | 6 — This field is used to provide additional detail for lodging transactions. If a lodging charge does not match one of the listed descriptions, the default value of ‘1’ should be sent in the request. When a value of ‘4’ is sent, the `additionalCharges` field needs to be sent as well. Value|Description -----|----------- 1 | No Special Code 2 | Assured Reservation/No Show 3 | Advance Deposit 4 | Delayed Charge 5 | Express Check-Out Service 6 | Assured Reservation/Normal
        - `additionalCharges` HotelAdditionalCharges — Reason codes for additional charges in a lodging sale request at the time a consumer checks out.
          - `giftShop` 'Y' | 'N'
          - `laundry` 'Y' | 'N'
          - `miniBar` 'Y' | 'N'
          - `other` 'Y' | 'N'
          - `restaurant` 'Y' | 'N'
          - `telephone` 'Y' | 'N'
        - `roomRates` HotelRoomRates[] — Room rates broken down by rate and number of nights.
          - `nights` integer — The number of nights being charged at this rate.
          - `rate` number — The per night room rate.
      - `purchaseCard` PurchaseCard, required
        - `customerReference` string, required — A unique value used to identify the consumer or transaction. If a merchant has a significant amount of revenue from purchasing card customers, the interface would use this field to collect the consumer’s purchase order or employee identification number. In lodging transactions, this may be unique transaction details, such as a reservation code or third-party booking source. This field is part of Level 2 card data.
        - `destinationPostalCode` string, required — When items are shipped, the ZIP/postal code to which merchandise will be shipped; otherwise, the ZIP/postal code where the goods or services are rendered. This field is part of Level 2 card data.
        - `productDescriptors` string[], required — A text description of the items purchased or services sold. This can be a generic text description of what the merchant sells (such as “Groceries”) or specific transaction data (such as the name of the item sold). At least one product descriptor field is required in a sale or authorization request. Note: The productDescriptors array is limited to 4 elements. Each element can contain a maximum of 40 characters.
      - `vendorReference` string — Optional field for information that can be searched in the merchant portal.
    - `device` object, required
      - `terminalId` string, required — To prompt a specific UTG-controlled PIN pad in a request, the API Terminal ID configured in UTG TuneUp must be specified in this field.
      - `promptPostalCode` 'Y' | 'N' — When using a UTG-controlled PIN pad: Value|Description -----|----------- Y | Force the PIN pad to prompt the consumer for a ZIP/Postal Code. N | Do not force the PIN pad to prompt the consumer for a ZIP/Postal Code. **Note: Use only when you want to override MCE (Manual Card Entry) settings in UTG.**
      - `promptCardSecurityCode` 'Y' | 'N' — When using a UTG-controlled PIN pad: Value|Description -----|----------- Y | Force the PIN pad to prompt the consumer for a CSC. N | Do not force the PIN pad to prompt the consumer for a CSC. **Note: Use only when you want to override MCE (Manual Card Entry) settings in UTG.**
      - `promptStreetNumber` 'Y' | 'N' — When using a UTG-controlled PIN pad: Value|Description -----|----------- Y | Force the PIN pad to prompt the consumer for the street number of their billing address. N | Do not force the PIN pad to prompt the consumer for the street number of their billing address. **Note: Use only when you want to override MCE (Manual Card Entry) settings in UTG.**
    - `card` object
      - `present` 'Y' | 'N' — **Conditional: Send in the initial authorization/sale request** Indicates whether a card was present (‘Y’) or not (‘N’) at the time a transaction took place. This should be set appropriately in the initial authorization/sale request. In subsequent requests, this field should be left blank or should not be sent. **Note:** Subsequent request here does not apply to the secondary request for card on file type transactions or reuse of the same card. An example of a subsequent request would be a capture after an authorization. You would not include `card.present` in the capture, which is the subsequent request. Another example is when performing an incremental authorization where you perform an authorization, followed by an incremental authorization then a capture. The second authorization (incremental) and the capture are the subsequent requests where you would not include `card.present`.
      - `type` 'CC' | 'DB' | 'GC' | 'HF' | 'PL' | 'YC' — An abbreviation used to specify the type of card that will be used when processing a transaction. If an interface sends a value that is not listed here, that value will be ignored. Value| Description -----|------------ CC | When using a UTG-controlled device, this value will force a card to process as credit. DB | When using a UTG-controlled device, this value will force a card to process as debit. When using a non-UTG-controlled PIN pad, this value must be sent when processing a debit transaction. GC | Gift Card HF | HSA/FSA Card PL | Private Label YC | IT’S YOUR CARD
    - `customer` Customer
      - `addressLine1` string — Cardholder’s street address exactly as it appears on their billing statement. This field is used in AVS.
      - `firstName` string — Specifies a consumer’s first name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `middleName` string — Specifies a consumer’s middle name.
      - `lastName` string — Specifies a consumer’s last name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `postalCode` string — Cardholder’s ZIP/postal code from their billing statement. This field is used in AVS. Do not include special characters. **Note: This field only allows alphanumeric characters (a-z, A-Z, 0-9). Special characters including - are not allowed. If you are sending in zip+4 you must not include the dash so 89134-1234 would be sent as 891341234**
      - `emailAddress` string — Customer email address.
      - `ipAddress` string — Public source IP Address where the request originates, not the IP Address of the web server.
    - `receiptColumns` integer — Send this field if you want Shift4 to format the receipt text instead of returning individual fields. The value sent will correlate to the column width of the formatted receipt that we return. (This also allows the receipt text to wrap to fit the paper size of the printed receipt.) See the [Printing Receipts](/guides/core-concepts/printing-receipts) section of this document for more information on formatted receipts.
    - `currencyCode` string, ISO 4217 3 Character Alphabetic Code — Transaction currency code. See the [Currency Codes](/guides/appendices/currency-codes) section for details. **Note: This is currently supported when processing for a merchant outside of the US and Canada. If processing for a US or Canadian merchant then this field will be ignored and the transaction will process in the merchant's configured currency.**
    - `apiOptions` string[] — API Options modify the request being made. See the [API Options](/guides/appendices/api-options.md) section for more information.
    - `statementSuffix` string — Custom description that will be appended to the merchant name on the customer's statement. For most card brands, the merchant DBA name can be a maximum of 25 characters. Sending this value will cause the merchant name to be truncated to 9 characters. Shift4 will add an asterisk between the merchant name and the `statementSuffix` value. For example, for a merchant named `Joe's Warehouse Emporium` that processes a transaction with `statementSuffix` value of `KDNYZUHQ1`, the merchant statement will show as `Joe's War*KDNYZUHQ1`. **Note: The value that displays on customer statements from card issuers is beyond Shift4's control. We will submit the transaction data as described above, however issuers may modify or truncate that data as they see fit. To best accommodate different issuer limitations, we will truncate the merchant name to the minimum possible value (9 characters) in order to attempt to leave the most room for the statementSuffix to populate on issuer statements.**
  - TransactionsManualsaleTokenGtv
    - `dateTime` string, ISO 8601, required — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
    - `amount` AmountObjectNoSurcharge, required — Object containing information regarding the amount being requested. The `total` field within the object is required and specifies the amount being requested. All other fields are for informational purposes and must also be included in the `total` field. For example, a purchase of $100 with a $20 tip and $8 tax would be `128.00` in the `total` field, `20.00` in the `tip` field and `8.00` in the `tax` field. Note: For merchants that are configured to allow multiple currencies, the amount fields can specify up to three decimal places. However, the number of decimal places can not exceed the number allowed for the specified currency. See the [Currency Codes](/guides/appendices/currency-codes) section for details.
      - `total` number, required — The amount being charged for a particular transaction. If other amount fields are sent, they must be included in the total amount. Amount cannot be zero.
      - `tax` number, required — The amount of sales tax charged for a transaction. The tax amount is used by businesses to track tax expenses for accounting purposes. Identifying the tax amount also helps consumers understand the total amount that they were billed. This field is part of Level 2 card data.
      - `taxIndicator` 'Y' | 'N' — Value|Description -----|----------- Y | Tax is included N | Tax is not included
      - `cashback` number — Specifies the cashback amount in a transaction. When using a UTG-controlled PIN pad with the ALLOWCASHBACK API Option, this field will return the cashback amount requested by the consumer. The interface can also send the desired cashback amount in a request by adding it to the `amount.total` and including it in the `amount.cashback` field. This will bypass prompting the consumer for a cashback amount.
      - `iiasAmounts` IIASAmounts[] — **Conditional: Send in the request if processing for a health care merchant.** For Vision related charges you must send only `iiasAmounts.type = 4V` and the corresponding `iiasAmounts.amount` value. For all other charges, the first entry in the array should have an amount representing the total of all healthcare costs, and `iiasAmounts.type = 4S`. Any subsequent entries should contain the subtotal for each of the other expense types involved in this transaction.
        - `amount` number — The subtotal for this type of healthcare expenses.
        - `type` '4O' | '4S' | '4T' | '4U' | '4V' | '4W' | '4X' — This code classifies eligible healthcare expenses. Value|Description -----|----------- 4O | Cash Disbursement (Discover Only) – Amount of Cash Back Being Requested 4S | Healthcare (Visa/MC Only) – Qualified Medical Expenses or Over-the-Counter 4T | Transit (Visa Only) – Transit Fare Media (e.g., Commuter and Parking Passes, Mass Transit Vouchers, and Tickets) 4U | RX (Visa/MC Only) 4V | Vision (Visa Only) 4W | Clinical (Visa Only) 4X | Dental (Visa Only)
      - `tip` number — **Conditional: Send in the request if a tip is included.** The tip amount of the transaction.
      - `checkTotal` number — Optional field specifying the total amount of the entire bill/invoice that this transaction is part of. It can be larger than `amount.total` in scenarios where the check is being split or if a portion of the check was already paid in cash or another form of payment.
    - `clerk` Clerk, required
      - `numericId` integer, required — A number used to identify the point-of-sale (POS) or property management system (PMS) clerk or user. The value cannot be 0. An interface must be able to dynamically populate this field (not use a hardcoded value), unless the interface will be used exclusively for e-commerce.
    - `transaction` object, required
      - `invoice` string, required — 10-digit invoice number assigned by the interface to identify a transaction. An invoice number serves as a unique key that identifies a transaction within a batch in Shift4's Gateway. **Note: For US and Canadian processing: Although the invoice number is sent as a JSON string it is a numeric value. No alpha characters are allowed.** **For processing outside of the US and Canada alpha characters are allowed.**
      - `authorizationCode` string, required — The authorization code provided by the consumer’s issuing bank. It is provided in a response if an online authorization or sale request is approved. Following a referral response, it is also specified in [Manual Sale](/apis/payments-platform-rest/openapi/transactions/manualsale) requests.
      - `manualTranId` string — This is typically used in a Referral. If a ManualTranID is returned by the issuer with the Auth code, it should be sent to the processor in the ManualTranid field.
      - `notes` string — A free-form notes field that supports the use of HTML tags. This can be used for reference in [Lighthouse Transaction Manager](https://ltm.shift4test.com/) and is not sent to the authorization host. Escaped quotation marks should not be sent in the Notes field.
      - `businessDate` string, ISO 8601 — Desired business date of a transaction. Include when overriding the existing business date of a transaction. The overriding date may be earlier or later than the existing date. (yyyy-mm-dd)
      - `amex` TransactionAmex
        - `propertyCode` string — The code that contains a Merchant-assigned store or location number (or name) that uniquely identifies where the transaction took place.
      - `auto` AutoCheckOut — **Conditional: Utilize this object for Auto Rental transactions**
        - `distanceDriven` integer — The amount of distance the cardholder drove the vehicle.
        - `distanceUnit` 'M' | 'K' — The unit of measure that corresponds to the `distanceDriven` field. Value|Description -----|----------- M | Miles K | Kilometers
        - `lateAdjustment` number — A dollar amount for late adjustment fees for an auto rental, including refueling charges, a surcharge, or charges for damage incurred during use.
        - `noShowIndicator` 'Y' | 'N' — Indicates whether or not the cardholder picked up a reserved rental car. Value|Description -----|----------- Y | customer did not pick up the rental car N | customer did pick up the rental car
        - `additionalCharges` AutoAdditionalCharges — The codes used to provide a reason for additional charges in an auto rental sale. Multiple codes can be specified for the same transaction.
          - `gasoline` 'Y' | 'N'
          - `lateReturn` 'Y' | 'N'
          - `mileage` 'Y' | 'N'
          - `oneWayServiceFee` 'Y' | 'N'
          - `violationFee` 'Y' | 'N'
        - `driver` AutoDriver
          - `license` string — The cardholder's driver's license number.
          - `name` string — In a sale/authorization request for an auto rental, the customer’s name exactly as it appears on their driver’s license.
          - `taxNumber` string — This field contains the driver’s Tax Identification Number.
        - `rental` AutoRental — Information relating to where the rental card was picked up.
          - `agreement` string — Contract number for an auto rental agreement.
          - `city` string — City where rental car was picked up.
          - `countryCode` string — Country where rental card was picked up.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was picked up in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was picked up in U.S. postal abbreviation format.
        - `return` AutoReturn — Information relating to where the rental car was returned
          - `city` string — City where rental car was returned.
          - `countryCode` string — Country where rental card was returned.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was returned in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was returned in U.S. postal abbreviation format.
      - `airline` AirlineRequest — **Conditional: Utilize this object for Airline transactions in Authorization/Sale requests when possible. If unable to provide this data at Authorization, this object must be sent in subsequent Capture requests for the transaction.**
        - `carrierCode` string, required — The code of the airline carrier issuing the ticket.
        - `carrierName` string, required — The name of the airline carrier issuing the ticket.
        - `conjunctionTicketIndicator` 'Y' | 'N', required — Indicates whether the itinerary contains more than four segments of travel. Value | Description -------|------------------- Y | Yes N | No
        - `documentType` '01' | '02' | '03' | '04' | '05' | '06' | '07' | '08' | '09' | '10' | '11' | '12' | '13' | '14' | '15' | '16' | '17' | '18' | '19' | '20' | '21' | '22' | '23' | '24' | '25' | '26' | '27' | '28' | '29' | '30' | '31' | '32' | '33' | '34' | '35' | '36' | '37' | '38' | '39' | '41' | '42' | '43' | '44' | '45' | '46' | '47' | '48' | '49' | '50' | '51' | '52' | '60' | '64' | '65' | '66' | '67' | '68' | '69' | '70' | '71' | '72' | '73' | '74' | '75' | '76' | '77' | '78' | '79' | '80' | '81' | '82' | '83' | '84' | '85' | '86' | '87' | '88' | '89' | '90' | '91' | '92' | '93', required — This field contains the airline Document Type code, which indicates the purpose of this transaction. This information may appear on the descriptive bill on the Cardmember's statement, or be used to resolve billing inquiries and disputes. The codes entered in the Transaction Type and Document Type fields are used together to describe the purpose of this transaction. Value | Description ------|--------------- 01 | Passenger Ticket 02 | Additional Collection 03 | Excess Baggage 04 | Misc. Charge Order (MCO) / Prepaid Ticket Auth 05 | Special Service Ticket 06 | Supported Refund 07 | Unsupported Refund 08 | Lost Ticket Application 09 | Tour Order Voucher 10 | Ticket by Mail 11 | Undercharge Adjustment 12 | Group Ticket 13 | Exchange Adjustment 14 | SPD/Air Freight 15 | In-flight Adjustment 16 | Agency Passenger Ticket 17 | Agency Tour Order/Voucher 18 | Agency Misc. Charge Order (MCO) 19 | Agency Exchange Order 20 | Agency Group Ticket 21 | Debit Adjustment Duplicate Refund/Use 22 | In-flight Merchandise Ordered 23 | Catalogue Merchandise Ordered 24 | In-flight Phone Charges 25 | Frequent Flyer Fee/Purchase 26 | Kennel Charge 27 | Animal Transportation Charge 28 | Firearms Case 29 | Upgrade Charge 30 | Credit Unused Transportation 31 | Credit Class of Service Adjustment 32 | Credit Denied Boarding 33 | Credit Misc. Refund 34 | Credit Lost Ticket Refund 35 | Credit Exchange Refund 36 | Credit Overcharge Adjustment 37 | Credit Multiple Unused Tickets 38 | Exchange Order 39 | Self-Service Ticket(s) 41 | In-flight Duty Free Purchase 42 | Senior Citizen Discount Booklets 43 | Club Membership Fee 44 | Coupon Book 45 | In-flight Charges 46 | Tour Deposit 47 | Frequent Flyer Overnight Delivery Charge 48 | Frequent Flyer Fulfillment 49 | Small Package Delivery 50 | Vendor Sale 51 | Miscellaneous Tax(es) Fee(s) 52 | Travel Agency Fee 60 | Vendor Refund Credit 64 | Duty Free Sale 65 | Preferred Seat Upgrade 66 | Cabin Upgrade 67 | Lounge/Club Access or Day Pass 68 | Agent Assisted Reservation. Ticketing Fee 69 | Ticket Change or Cancel Fee 70 | Trip Insurance 71 | Unaccompanied Minor 72 | Standby Fee 73 | Curbside Baggage 74 | Inflight Medical Equipment 75 | Ticket or Pass Print Fee 76 | Checked Sporting/Special Equipment 77 | Dry Ice Fee 78 | Mail/Postage Fee 79 | Club Membership Fee - Temporary/Trial 80 | Frequent Flyer Activation/Reinstatement 81 | Gift Certificate 82 | Onboard/Inflight Prepaid Voucher 83 | Optional Services Fee 84 | Advanced Purchase - Excess Baggage 85 | Advanced Purchase - Preferred Seat Upgrade 86 | Advanced Purchase - Cabin Upgrade 87 | Advanced Purchase - Optional Services 88 | WiFi 89 | Packages 90 | Inflight Entertainment/Internet Access 91 | Overweight Bag Fee 92 | Sleep Sets 93 | Special Purchase Fee
        - `electronicTicketIndicator` 'Y' | 'N', required — Indicates if an electronic ticket was issued. Value | Description -------|------------------- Y | Yes N | No
        - `internetIndicator` 'Y' | 'N', required — Indicates if this is an internet transaction. Value | Description -------|------------------- Y | Yes N | No
        - `issueDate` string, ISO 8601, required — The date the ticket was issued to the customer. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `numberOfCities` number, required — The number of airports or cities for each leg on the ticket (including origination and destination cities).
        - `numberOfCarriers` number, required — This field contains the number of airline carriers.
        - `numberOfPassengers` number, required — The number of passengers in the transaction.
        - `passengerArrivalDate` string, ISO 8601, required — Date that the ticket holder is scheduled to arrive at their destination at the time of issuance of the original ticket. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerDepartureDate` string, ISO 8601, required — Date that the ticket holder is scheduled to depart at the time of issuance of the original ticket. The date may be a future one. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerNameRecord` string, required — A passenger name record (PNR) is a record in the database of a computer reservation system (CRS) that contains the itinerary for a passenger or a group of passengers travelling together
        - `restrictedTicketIndicator` '0' | '1', required — Indicates whether this ticket is non-refundable. Value | Description -------|------------------- 0 | No restriction 1 | Restricted (non-refundable) ticket
        - `ticketChangeIndicator` 'C' | 'N', required — Indicates why a ticket was changed. This field should contain spaces or one of the below codes. Value | Description -------|--------------- C | Change to existing ticket N | New ticket
        - `ticketTranType` 'TKT' | 'REF' | 'EXC' | 'MSC', required — This field contains the ticket transaction type code assigned to this transaction. Value | Description -------|--------------- TKT | Ticket Purchase REF | Refund EXC | Exchange Ticket MSC | Miscellaneous (non-Ticket Purchase- and non-Exchange Ticket-related transactions only)
        - `typeIndicator` 'R' | 'O' | 'M', required — Indicates if this ticket is a round trip, multi-city, or one-way ticket. Value | Description -------|--------------- R | Round-Trip O | One Way M | Multi-City
        - `tickets` AirlineTickets[], required — Array of ticket number and passenger name. Note: At least one instance of ticket number and passenger name info should be provided.
          - `passengerName` string, required — Name of the passenger to whom the ticket was issued. This field contains the Passenger Name in format: `SURNAME FIRSTNAME MIDDLEINITIAL TITLE` Example: "Doe Jane M Mrs"
          - `ticketNumber` string, required — The ticket number provided by the Carrier for the passenger.
          - `ticketFare` number, required — Ticket fare is the total amount for each ticket, including service fee or any other fee for each ticket.
        - `flightLegs` AirlineFlightLegs[], required — Array of flight trip leg info. Maximun 4 legs to a trip allowed. Note: At least one instance of flight trip leg info should be provided.
          - `carrierCode` string, required — Code indicating name of carrier (United Airlines, Jet Blue, etc.) for the leg.
          - `couponNumber` number — Number of coupons in the ticket for the leg.
          - `destAirportCode` string, required — Indicates destination city's airport code for the leg.
          - `fare` number, required — This field contains the total Fare for this trip segment. This is not the total amount billed to the customer.
          - `fareBasis` string, required — This field contains primary and secondary discount codes that indicate the class of service and fare level associated with the ticket for the leg. Truncate at 24 bytes, if necessary.
          - `flightNumber` string, required — Number of the airline flight to be taken on Leg of the trip.
          - `legArrivalDateTime` string, ISO 8601, required — The date and time the flight is scheduled to arrive for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `legDepartureDateTime` string, ISO 8601, required — The date and time the flight is scheduled to depart for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `originAirportCode` string, required — Indicates origination city's airport code for the leg.
          - `serviceClass` string, required — Indicates service class for leg. Value | Description -------|--------------- FC | First Class BC | Business Class EC | Economy/Coach Class
          - `stopOverCode` string, required — Indicates whether a stopover is allowed on this ticket for leg. The entry must be a D, O, or X. Value | Description -------|--------------- O | Stopover allowed X | Stopover not allowed D | Destination point
          - `tripLegInfo` string, required — Description of leg or stage of trip.
        - `ancillaryServices` AirlineAncillaryServices[] — Array of ancillary service code and fees. **Conditional: Send if any ancillary services were charged.**
          - `serviceCode` 'BF' | 'BG' | 'CF' | 'CG' | 'CO' | 'FF' | 'GF' | 'GT' | 'IE' | 'LG' | 'MD' | 'ML' | 'OT' | 'PA' | 'PT' | 'SA' | 'SB' | 'SF' | 'ST' | 'TS' | 'UN' | 'UP' | 'WI', required — This field describes the type of service that has been provided. Value | Description ------|--------------- BF | Bundled Service BG | Baggage Fee CF | Change Fee CG | Cargo CO | Carbon Offset FF | Frequent Flyer GF | Gift Card GT | Ground Transport IE | In-Flight Entertainment LG | Lounge MD | Medical ML | Meal/Beverage OT | Other PA | Passenger Assist Fee PT | Pets SA | Seat Fees SB | Standby SF | Service Fee ST | Store TS | Travel Service UN | Unaccompanied Travel UP | Upgrades WI | Wi-Fi
          - `serviceFee` number, required — This field contains the amount associated with the value provided in ancillary Service Code.
        - `travelAgencyCode` string — Code identifying travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `travelAgencyName` string — Name of travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `exchangeTicketNumber` string — The original ticket number that was replaced by a new ticket number.
      - `cardOnFile` CardOnFile — **Conditional: Send this object when the transaction being performed is using a card on file or when the request will result in storing a card on file.** See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for more information.
        - `type` 'S01' | 'S02' | 'U01' | 'U02' | 'U03' | 'U04' | 'U05' | 'U06' | 'U07' | 'U08' | 'U09' — This field specifies the type of the card-on-file transaction. Below is a table showing the valid values for use cases where the cardholder is entering their card data to store on file. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | S01 | Cardholder | No | Yes | Used when the initial transaction/card verification request is not for a recurring payment. | | S02 | Cardholder | Yes | Yes | Used when the initial transaction/card verification request is for a recurring payment. Requires sending `cardOnFile.recurringFrequency` and `cardOnFile.recurringExpiry` | Below is a table showing the valid values for uses cases where you already have a card on file and are using that existing card to process a transaction. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | U01 | Cardholder | No | Yes | Unscheduled transaction using the card on file initiated by the cardholder | | U02 | Merchant | No | No | Unscheduled transaction using the card on file initiated by the merchant | | U03 | Merchant | Yes | No | Merchant initiated recurring payment using the card on file | | U04 | Merchant | No | No | Identifies a transaction as a Reauthorization COF transaction. | | U05 | Merchant | No | No | Identifies a transaction as a Resubmission COF transaction. Only certain merchant categories are able to send a resubmission, and it can only be done if the original authorization attempt was declined due to insufficient funds. | | U06 | Merchant | No | No | Identifies a transaction as an Estimated Authorization COF transaction. | | U07 | Merchant | No | No | Identifies a transaction as a Delayed Charges COF transaction. For example, a hotel might charge a customer for room damages after the guest has already checked out. | | U08 | Merchant | No | No | Identifies a transaction as an Incremental COF transaction. For example, a hotel which authorized a customer’s card for one night at check-in might increase the authorization amount to cover two nights when the customer decides to extend their stay. Shift4 automatically detects this scenario and sends the appropriate value to the processor. | | U09 | Merchant | No | No | Identifies a transaction as a No Show COF transaction. For example, a hotel might charge a customer who does not show up for a booked stay. | See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for additional details.
        - `recurringExpiry` string — Date after which no further authorizations shall be performed. This field is limited to 8 characters, and the accepted format is YYYYMMDD. **Conditional: This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `recurringFrequency` string — Indicates the minimum number of days between authorizations. **Conditional: 'This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `transactionId` string — This field is returned in the initial COF response, and ties subsequent COF transactions to the original authorization. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
        - `transactionLinkId` string — A unique identifier assigned to each transaction to link related events throughout the transaction lifecycle. This field is supported for Mastercard brand only. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionLinkId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionLinkId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
      - `hotel` HotelCheckOut — **Conditional: Utilize this object for Hotel transactions**
        - `arrivalDateTime` string — Arrival date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the arrival date needs to be one day before the sale date.
        - `departureDateTime` string — Departure date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the departure date needs to be the day of the sale.
        - `primaryChargeType` 1 | 2 | 3 — Guest’s transaction type at a hotel. Value|Description -----|----------- 1 | Lodging 2 | Restaurant 3 | Gift Shop
        - `specialCode` 1 | 2 | 3 | 4 | 5 | 6 — This field is used to provide additional detail for lodging transactions. If a lodging charge does not match one of the listed descriptions, the default value of ‘1’ should be sent in the request. When a value of ‘4’ is sent, the `additionalCharges` field needs to be sent as well. Value|Description -----|----------- 1 | No Special Code 2 | Assured Reservation/No Show 3 | Advance Deposit 4 | Delayed Charge 5 | Express Check-Out Service 6 | Assured Reservation/Normal
        - `additionalCharges` HotelAdditionalCharges — Reason codes for additional charges in a lodging sale request at the time a consumer checks out.
          - `giftShop` 'Y' | 'N'
          - `laundry` 'Y' | 'N'
          - `miniBar` 'Y' | 'N'
          - `other` 'Y' | 'N'
          - `restaurant` 'Y' | 'N'
          - `telephone` 'Y' | 'N'
        - `roomRates` HotelRoomRates[] — Room rates broken down by rate and number of nights.
          - `nights` integer — The number of nights being charged at this rate.
          - `rate` number — The per night room rate.
      - `purchaseCard` PurchaseCard, required
        - `customerReference` string, required — A unique value used to identify the consumer or transaction. If a merchant has a significant amount of revenue from purchasing card customers, the interface would use this field to collect the consumer’s purchase order or employee identification number. In lodging transactions, this may be unique transaction details, such as a reservation code or third-party booking source. This field is part of Level 2 card data.
        - `destinationPostalCode` string, required — When items are shipped, the ZIP/postal code to which merchandise will be shipped; otherwise, the ZIP/postal code where the goods or services are rendered. This field is part of Level 2 card data.
        - `productDescriptors` string[], required — A text description of the items purchased or services sold. This can be a generic text description of what the merchant sells (such as “Groceries”) or specific transaction data (such as the name of the item sold). At least one product descriptor field is required in a sale or authorization request. Note: The productDescriptors array is limited to 4 elements. Each element can contain a maximum of 40 characters.
      - `vendorReference` string — Optional field for information that can be searched in the merchant portal.
    - `card` object, required
      - `expirationDate` integer — **Conditional: Send only when card data is manually entered or when using a token. This field should not be specified when using an encrypted device.** Card expiration date in MMYY format. This value should only be populated in the initial sale/authorization request.
      - `present` 'Y' | 'N' — **Conditional: Send in the initial authorization/sale request** Indicates whether a card was present (‘Y’) or not (‘N’) at the time a transaction took place. This should be set appropriately in the initial authorization/sale request. In subsequent requests, this field should be left blank or should not be sent. **Note:** Subsequent request here does not apply to the secondary request for card on file type transactions or reuse of the same card. An example of a subsequent request would be a capture after an authorization. You would not include `card.present` in the capture, which is the subsequent request. Another example is when performing an incremental authorization where you perform an authorization, followed by an incremental authorization then a capture. The second authorization (incremental) and the capture are the subsequent requests where you would not include `card.present`.
      - `token` CardTokenRequired, required
        - `value` string, required — This field is used to specify a card token. Whenever CHD is sent in a request, a card token will be returned in this field. Your interface should be designed to store this card token for future use. The latest card token received should be used in any subsequent request that references the same card data.
      - `securityCode` CardSecurityCode — **Conditional: Send only when card data is manually entered. This object should not be specified when using an encrypted device. This object should be sent for initial card on file request but is not required for subsequent merchant initiated charges.**
        - `indicator` '0' | '1' | '2' | '9', required — This field indicates the presence of a CSC. Value|Description -----|----------- 0 | CSC not provided by user. 1 | CSC provided. 2 | CSC illegible. 9 | CSC not on card, or card did not have a CSC.
        - `result` 'M' | 'N' | 'P' | 'S' | 'U' | 'Y' | '1' | '2' | '3' — **Conditional: Returned if `card.securityCode.indicator` and `card.securityCode.value` are sent in the request.** The result of a CSC check. This field will be used by Shift4 to determine the value sent in the `card.securityCode.valid` field (based on the merchant’s list of accepted verification results as configured with Shift4). Value|Description -----|------------ M | CSC matched. N | CSC did not match. P | CSC not processed. S | CSC should have been present. U | Issuer unable to process. Y | CVC1 incorrect. 1 | CSC Unavailable - processor / card type does not support this parameter. 2 | An unrecognised result code was returned by the processor. 3 | No result code was returned by the processor.
        - `valid` string — **Conditional: Returned if `card.securityCode.indicator` and `card.securityCode.value` are sent in the request.** A simplified CSC check result based on the value in the `card.securityCode.result` field and the merchant’s accepted verification results as configured with Shift4. The value returned will be ‘Y’ if CSC verification passed or ‘N’ if CSC verification did not pass.
        - `value` string, required — The three- or four-digit Card Security Code found on a payment card. This value should only be sent in an initial sale/authorization request. It should not be stored by the interface. When sending `card.securityCode.value`, `card.securityCode.indicator` must also be sent.
    - `customer` Customer
      - `addressLine1` string — Cardholder’s street address exactly as it appears on their billing statement. This field is used in AVS.
      - `firstName` string — Specifies a consumer’s first name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `middleName` string — Specifies a consumer’s middle name.
      - `lastName` string — Specifies a consumer’s last name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `postalCode` string — Cardholder’s ZIP/postal code from their billing statement. This field is used in AVS. Do not include special characters. **Note: This field only allows alphanumeric characters (a-z, A-Z, 0-9). Special characters including - are not allowed. If you are sending in zip+4 you must not include the dash so 89134-1234 would be sent as 891341234**
      - `emailAddress` string — Customer email address.
      - `ipAddress` string — Public source IP Address where the request originates, not the IP Address of the web server.
    - `receiptColumns` integer — Send this field if you want Shift4 to format the receipt text instead of returning individual fields. The value sent will correlate to the column width of the formatted receipt that we return. (This also allows the receipt text to wrap to fit the paper size of the printed receipt.) See the [Printing Receipts](/guides/core-concepts/printing-receipts) section of this document for more information on formatted receipts.
    - `currencyCode` string, ISO 4217 3 Character Alphabetic Code — Transaction currency code. See the [Currency Codes](/guides/appendices/currency-codes) section for details. **Note: This is currently supported when processing for a merchant outside of the US and Canada. If processing for a US or Canadian merchant then this field will be ignored and the transaction will process in the merchant's configured currency.**
    - `apiOptions` string[] — API Options modify the request being made. See the [API Options](/guides/appendices/api-options.md) section for more information.
    - `reportingData` ReportingData — Used to send non-payment related data for reporting purposes.
      - `customerInfo` ReportingDataCustomerInfo[] — Array of customer information objects. The maximum number of customer information objects that can be sent is 10.
        - `firstName` string — Customer's first name
        - `lastName` string — Customer's last name
        - `dateOfBirth` string — Customer's date of birth in MMDDYYYY format
        - `gender` string — Customer's gender
        - `baggage` string — Description for the customer's baggage
        - `seats` string — Customer's assigned seat
        - `boardingPriority` string — Customer's boarding priority
      - `pspData` ReportingDataPspData — Payment service provider (PSP) metadata for third-party processed transactions.
        - `pspId` string — PSP identifier / label
        - `pspMid` string — PSP merchant identifier (MID).
        - `pspTid` string — PSP terminal identifier (TID).
        - `pspTxnTraceNo` string — PSP transaction trace number.
        - `pspTxnDate` string, date — PSP transaction date (YYYYMMDD).
        - `pspTxnTime` string, 24-hour time — PSP transaction time (hhmmss)
        - `pspResponseCode` string — PSP host response code.
        - `pspResponseText` string — PSP host response description/text.
    - `statementSuffix` string — Custom description that will be appended to the merchant name on the customer's statement. For most card brands, the merchant DBA name can be a maximum of 25 characters. Sending this value will cause the merchant name to be truncated to 9 characters. Shift4 will add an asterisk between the merchant name and the `statementSuffix` value. For example, for a merchant named `Joe's Warehouse Emporium` that processes a transaction with `statementSuffix` value of `KDNYZUHQ1`, the merchant statement will show as `Joe's War*KDNYZUHQ1`. **Note: The value that displays on customer statements from card issuers is beyond Shift4's control. We will submit the transaction data as described above, however issuers may modify or truncate that data as they see fit. To best accommodate different issuer limitations, we will truncate the merchant name to the minimum possible value (9 characters) in order to attempt to leave the most room for the statementSuffix to populate on issuer statements.**
  - TransactionsManualsaleTokenLegacy
    - `dateTime` string, ISO 8601, required — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
    - `amount` AmountObjectNoSurcharge, required — Object containing information regarding the amount being requested. The `total` field within the object is required and specifies the amount being requested. All other fields are for informational purposes and must also be included in the `total` field. For example, a purchase of $100 with a $20 tip and $8 tax would be `128.00` in the `total` field, `20.00` in the `tip` field and `8.00` in the `tax` field. Note: For merchants that are configured to allow multiple currencies, the amount fields can specify up to three decimal places. However, the number of decimal places can not exceed the number allowed for the specified currency. See the [Currency Codes](/guides/appendices/currency-codes) section for details.
      - `total` number, required — The amount being charged for a particular transaction. If other amount fields are sent, they must be included in the total amount. Amount cannot be zero.
      - `tax` number, required — The amount of sales tax charged for a transaction. The tax amount is used by businesses to track tax expenses for accounting purposes. Identifying the tax amount also helps consumers understand the total amount that they were billed. This field is part of Level 2 card data.
      - `taxIndicator` 'Y' | 'N' — Value|Description -----|----------- Y | Tax is included N | Tax is not included
      - `cashback` number — Specifies the cashback amount in a transaction. When using a UTG-controlled PIN pad with the ALLOWCASHBACK API Option, this field will return the cashback amount requested by the consumer. The interface can also send the desired cashback amount in a request by adding it to the `amount.total` and including it in the `amount.cashback` field. This will bypass prompting the consumer for a cashback amount.
      - `iiasAmounts` IIASAmounts[] — **Conditional: Send in the request if processing for a health care merchant.** For Vision related charges you must send only `iiasAmounts.type = 4V` and the corresponding `iiasAmounts.amount` value. For all other charges, the first entry in the array should have an amount representing the total of all healthcare costs, and `iiasAmounts.type = 4S`. Any subsequent entries should contain the subtotal for each of the other expense types involved in this transaction.
        - `amount` number — The subtotal for this type of healthcare expenses.
        - `type` '4O' | '4S' | '4T' | '4U' | '4V' | '4W' | '4X' — This code classifies eligible healthcare expenses. Value|Description -----|----------- 4O | Cash Disbursement (Discover Only) – Amount of Cash Back Being Requested 4S | Healthcare (Visa/MC Only) – Qualified Medical Expenses or Over-the-Counter 4T | Transit (Visa Only) – Transit Fare Media (e.g., Commuter and Parking Passes, Mass Transit Vouchers, and Tickets) 4U | RX (Visa/MC Only) 4V | Vision (Visa Only) 4W | Clinical (Visa Only) 4X | Dental (Visa Only)
      - `tip` number — **Conditional: Send in the request if a tip is included.** The tip amount of the transaction.
      - `checkTotal` number — Optional field specifying the total amount of the entire bill/invoice that this transaction is part of. It can be larger than `amount.total` in scenarios where the check is being split or if a portion of the check was already paid in cash or another form of payment.
    - `clerk` Clerk, required
      - `numericId` integer, required — A number used to identify the point-of-sale (POS) or property management system (PMS) clerk or user. The value cannot be 0. An interface must be able to dynamically populate this field (not use a hardcoded value), unless the interface will be used exclusively for e-commerce.
    - `transaction` object, required
      - `invoice` string, required — 10-digit invoice number assigned by the interface to identify a transaction. An invoice number serves as a unique key that identifies a transaction within a batch in Shift4's Gateway. **Note: For US and Canadian processing: Although the invoice number is sent as a JSON string it is a numeric value. No alpha characters are allowed.** **For processing outside of the US and Canada alpha characters are allowed.**
      - `authorizationCode` string, required — The authorization code provided by the consumer’s issuing bank. It is provided in a response if an online authorization or sale request is approved. Following a referral response, it is also specified in [Manual Sale](/apis/payments-platform-rest/openapi/transactions/manualsale) requests.
      - `manualTranId` string — This is typically used in a Referral. If a ManualTranID is returned by the issuer with the Auth code, it should be sent to the processor in the ManualTranid field.
      - `notes` string — A free-form notes field that supports the use of HTML tags. This can be used for reference in [Lighthouse Transaction Manager](https://ltm.shift4test.com/) and is not sent to the authorization host. Escaped quotation marks should not be sent in the Notes field.
      - `businessDate` string, ISO 8601 — Desired business date of a transaction. Include when overriding the existing business date of a transaction. The overriding date may be earlier or later than the existing date. (yyyy-mm-dd)
      - `amex` TransactionAmex
        - `propertyCode` string — The code that contains a Merchant-assigned store or location number (or name) that uniquely identifies where the transaction took place.
      - `auto` AutoCheckOut — **Conditional: Utilize this object for Auto Rental transactions**
        - `distanceDriven` integer — The amount of distance the cardholder drove the vehicle.
        - `distanceUnit` 'M' | 'K' — The unit of measure that corresponds to the `distanceDriven` field. Value|Description -----|----------- M | Miles K | Kilometers
        - `lateAdjustment` number — A dollar amount for late adjustment fees for an auto rental, including refueling charges, a surcharge, or charges for damage incurred during use.
        - `noShowIndicator` 'Y' | 'N' — Indicates whether or not the cardholder picked up a reserved rental car. Value|Description -----|----------- Y | customer did not pick up the rental car N | customer did pick up the rental car
        - `additionalCharges` AutoAdditionalCharges — The codes used to provide a reason for additional charges in an auto rental sale. Multiple codes can be specified for the same transaction.
          - `gasoline` 'Y' | 'N'
          - `lateReturn` 'Y' | 'N'
          - `mileage` 'Y' | 'N'
          - `oneWayServiceFee` 'Y' | 'N'
          - `violationFee` 'Y' | 'N'
        - `driver` AutoDriver
          - `license` string — The cardholder's driver's license number.
          - `name` string — In a sale/authorization request for an auto rental, the customer’s name exactly as it appears on their driver’s license.
          - `taxNumber` string — This field contains the driver’s Tax Identification Number.
        - `rental` AutoRental — Information relating to where the rental card was picked up.
          - `agreement` string — Contract number for an auto rental agreement.
          - `city` string — City where rental car was picked up.
          - `countryCode` string — Country where rental card was picked up.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was picked up in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was picked up in U.S. postal abbreviation format.
        - `return` AutoReturn — Information relating to where the rental car was returned
          - `city` string — City where rental car was returned.
          - `countryCode` string — Country where rental card was returned.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was returned in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was returned in U.S. postal abbreviation format.
      - `airline` AirlineRequest — **Conditional: Utilize this object for Airline transactions in Authorization/Sale requests when possible. If unable to provide this data at Authorization, this object must be sent in subsequent Capture requests for the transaction.**
        - `carrierCode` string, required — The code of the airline carrier issuing the ticket.
        - `carrierName` string, required — The name of the airline carrier issuing the ticket.
        - `conjunctionTicketIndicator` 'Y' | 'N', required — Indicates whether the itinerary contains more than four segments of travel. Value | Description -------|------------------- Y | Yes N | No
        - `documentType` '01' | '02' | '03' | '04' | '05' | '06' | '07' | '08' | '09' | '10' | '11' | '12' | '13' | '14' | '15' | '16' | '17' | '18' | '19' | '20' | '21' | '22' | '23' | '24' | '25' | '26' | '27' | '28' | '29' | '30' | '31' | '32' | '33' | '34' | '35' | '36' | '37' | '38' | '39' | '41' | '42' | '43' | '44' | '45' | '46' | '47' | '48' | '49' | '50' | '51' | '52' | '60' | '64' | '65' | '66' | '67' | '68' | '69' | '70' | '71' | '72' | '73' | '74' | '75' | '76' | '77' | '78' | '79' | '80' | '81' | '82' | '83' | '84' | '85' | '86' | '87' | '88' | '89' | '90' | '91' | '92' | '93', required — This field contains the airline Document Type code, which indicates the purpose of this transaction. This information may appear on the descriptive bill on the Cardmember's statement, or be used to resolve billing inquiries and disputes. The codes entered in the Transaction Type and Document Type fields are used together to describe the purpose of this transaction. Value | Description ------|--------------- 01 | Passenger Ticket 02 | Additional Collection 03 | Excess Baggage 04 | Misc. Charge Order (MCO) / Prepaid Ticket Auth 05 | Special Service Ticket 06 | Supported Refund 07 | Unsupported Refund 08 | Lost Ticket Application 09 | Tour Order Voucher 10 | Ticket by Mail 11 | Undercharge Adjustment 12 | Group Ticket 13 | Exchange Adjustment 14 | SPD/Air Freight 15 | In-flight Adjustment 16 | Agency Passenger Ticket 17 | Agency Tour Order/Voucher 18 | Agency Misc. Charge Order (MCO) 19 | Agency Exchange Order 20 | Agency Group Ticket 21 | Debit Adjustment Duplicate Refund/Use 22 | In-flight Merchandise Ordered 23 | Catalogue Merchandise Ordered 24 | In-flight Phone Charges 25 | Frequent Flyer Fee/Purchase 26 | Kennel Charge 27 | Animal Transportation Charge 28 | Firearms Case 29 | Upgrade Charge 30 | Credit Unused Transportation 31 | Credit Class of Service Adjustment 32 | Credit Denied Boarding 33 | Credit Misc. Refund 34 | Credit Lost Ticket Refund 35 | Credit Exchange Refund 36 | Credit Overcharge Adjustment 37 | Credit Multiple Unused Tickets 38 | Exchange Order 39 | Self-Service Ticket(s) 41 | In-flight Duty Free Purchase 42 | Senior Citizen Discount Booklets 43 | Club Membership Fee 44 | Coupon Book 45 | In-flight Charges 46 | Tour Deposit 47 | Frequent Flyer Overnight Delivery Charge 48 | Frequent Flyer Fulfillment 49 | Small Package Delivery 50 | Vendor Sale 51 | Miscellaneous Tax(es) Fee(s) 52 | Travel Agency Fee 60 | Vendor Refund Credit 64 | Duty Free Sale 65 | Preferred Seat Upgrade 66 | Cabin Upgrade 67 | Lounge/Club Access or Day Pass 68 | Agent Assisted Reservation. Ticketing Fee 69 | Ticket Change or Cancel Fee 70 | Trip Insurance 71 | Unaccompanied Minor 72 | Standby Fee 73 | Curbside Baggage 74 | Inflight Medical Equipment 75 | Ticket or Pass Print Fee 76 | Checked Sporting/Special Equipment 77 | Dry Ice Fee 78 | Mail/Postage Fee 79 | Club Membership Fee - Temporary/Trial 80 | Frequent Flyer Activation/Reinstatement 81 | Gift Certificate 82 | Onboard/Inflight Prepaid Voucher 83 | Optional Services Fee 84 | Advanced Purchase - Excess Baggage 85 | Advanced Purchase - Preferred Seat Upgrade 86 | Advanced Purchase - Cabin Upgrade 87 | Advanced Purchase - Optional Services 88 | WiFi 89 | Packages 90 | Inflight Entertainment/Internet Access 91 | Overweight Bag Fee 92 | Sleep Sets 93 | Special Purchase Fee
        - `electronicTicketIndicator` 'Y' | 'N', required — Indicates if an electronic ticket was issued. Value | Description -------|------------------- Y | Yes N | No
        - `internetIndicator` 'Y' | 'N', required — Indicates if this is an internet transaction. Value | Description -------|------------------- Y | Yes N | No
        - `issueDate` string, ISO 8601, required — The date the ticket was issued to the customer. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `numberOfCities` number, required — The number of airports or cities for each leg on the ticket (including origination and destination cities).
        - `numberOfCarriers` number, required — This field contains the number of airline carriers.
        - `numberOfPassengers` number, required — The number of passengers in the transaction.
        - `passengerArrivalDate` string, ISO 8601, required — Date that the ticket holder is scheduled to arrive at their destination at the time of issuance of the original ticket. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerDepartureDate` string, ISO 8601, required — Date that the ticket holder is scheduled to depart at the time of issuance of the original ticket. The date may be a future one. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerNameRecord` string, required — A passenger name record (PNR) is a record in the database of a computer reservation system (CRS) that contains the itinerary for a passenger or a group of passengers travelling together
        - `restrictedTicketIndicator` '0' | '1', required — Indicates whether this ticket is non-refundable. Value | Description -------|------------------- 0 | No restriction 1 | Restricted (non-refundable) ticket
        - `ticketChangeIndicator` 'C' | 'N', required — Indicates why a ticket was changed. This field should contain spaces or one of the below codes. Value | Description -------|--------------- C | Change to existing ticket N | New ticket
        - `ticketTranType` 'TKT' | 'REF' | 'EXC' | 'MSC', required — This field contains the ticket transaction type code assigned to this transaction. Value | Description -------|--------------- TKT | Ticket Purchase REF | Refund EXC | Exchange Ticket MSC | Miscellaneous (non-Ticket Purchase- and non-Exchange Ticket-related transactions only)
        - `typeIndicator` 'R' | 'O' | 'M', required — Indicates if this ticket is a round trip, multi-city, or one-way ticket. Value | Description -------|--------------- R | Round-Trip O | One Way M | Multi-City
        - `tickets` AirlineTickets[], required — Array of ticket number and passenger name. Note: At least one instance of ticket number and passenger name info should be provided.
          - `passengerName` string, required — Name of the passenger to whom the ticket was issued. This field contains the Passenger Name in format: `SURNAME FIRSTNAME MIDDLEINITIAL TITLE` Example: "Doe Jane M Mrs"
          - `ticketNumber` string, required — The ticket number provided by the Carrier for the passenger.
          - `ticketFare` number, required — Ticket fare is the total amount for each ticket, including service fee or any other fee for each ticket.
        - `flightLegs` AirlineFlightLegs[], required — Array of flight trip leg info. Maximun 4 legs to a trip allowed. Note: At least one instance of flight trip leg info should be provided.
          - `carrierCode` string, required — Code indicating name of carrier (United Airlines, Jet Blue, etc.) for the leg.
          - `couponNumber` number — Number of coupons in the ticket for the leg.
          - `destAirportCode` string, required — Indicates destination city's airport code for the leg.
          - `fare` number, required — This field contains the total Fare for this trip segment. This is not the total amount billed to the customer.
          - `fareBasis` string, required — This field contains primary and secondary discount codes that indicate the class of service and fare level associated with the ticket for the leg. Truncate at 24 bytes, if necessary.
          - `flightNumber` string, required — Number of the airline flight to be taken on Leg of the trip.
          - `legArrivalDateTime` string, ISO 8601, required — The date and time the flight is scheduled to arrive for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `legDepartureDateTime` string, ISO 8601, required — The date and time the flight is scheduled to depart for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `originAirportCode` string, required — Indicates origination city's airport code for the leg.
          - `serviceClass` string, required — Indicates service class for leg. Value | Description -------|--------------- FC | First Class BC | Business Class EC | Economy/Coach Class
          - `stopOverCode` string, required — Indicates whether a stopover is allowed on this ticket for leg. The entry must be a D, O, or X. Value | Description -------|--------------- O | Stopover allowed X | Stopover not allowed D | Destination point
          - `tripLegInfo` string, required — Description of leg or stage of trip.
        - `ancillaryServices` AirlineAncillaryServices[] — Array of ancillary service code and fees. **Conditional: Send if any ancillary services were charged.**
          - `serviceCode` 'BF' | 'BG' | 'CF' | 'CG' | 'CO' | 'FF' | 'GF' | 'GT' | 'IE' | 'LG' | 'MD' | 'ML' | 'OT' | 'PA' | 'PT' | 'SA' | 'SB' | 'SF' | 'ST' | 'TS' | 'UN' | 'UP' | 'WI', required — This field describes the type of service that has been provided. Value | Description ------|--------------- BF | Bundled Service BG | Baggage Fee CF | Change Fee CG | Cargo CO | Carbon Offset FF | Frequent Flyer GF | Gift Card GT | Ground Transport IE | In-Flight Entertainment LG | Lounge MD | Medical ML | Meal/Beverage OT | Other PA | Passenger Assist Fee PT | Pets SA | Seat Fees SB | Standby SF | Service Fee ST | Store TS | Travel Service UN | Unaccompanied Travel UP | Upgrades WI | Wi-Fi
          - `serviceFee` number, required — This field contains the amount associated with the value provided in ancillary Service Code.
        - `travelAgencyCode` string — Code identifying travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `travelAgencyName` string — Name of travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `exchangeTicketNumber` string — The original ticket number that was replaced by a new ticket number.
      - `cardOnFile` CardOnFile — **Conditional: Send this object when the transaction being performed is using a card on file or when the request will result in storing a card on file.** See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for more information.
        - `type` 'S01' | 'S02' | 'U01' | 'U02' | 'U03' | 'U04' | 'U05' | 'U06' | 'U07' | 'U08' | 'U09' — This field specifies the type of the card-on-file transaction. Below is a table showing the valid values for use cases where the cardholder is entering their card data to store on file. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | S01 | Cardholder | No | Yes | Used when the initial transaction/card verification request is not for a recurring payment. | | S02 | Cardholder | Yes | Yes | Used when the initial transaction/card verification request is for a recurring payment. Requires sending `cardOnFile.recurringFrequency` and `cardOnFile.recurringExpiry` | Below is a table showing the valid values for uses cases where you already have a card on file and are using that existing card to process a transaction. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | U01 | Cardholder | No | Yes | Unscheduled transaction using the card on file initiated by the cardholder | | U02 | Merchant | No | No | Unscheduled transaction using the card on file initiated by the merchant | | U03 | Merchant | Yes | No | Merchant initiated recurring payment using the card on file | | U04 | Merchant | No | No | Identifies a transaction as a Reauthorization COF transaction. | | U05 | Merchant | No | No | Identifies a transaction as a Resubmission COF transaction. Only certain merchant categories are able to send a resubmission, and it can only be done if the original authorization attempt was declined due to insufficient funds. | | U06 | Merchant | No | No | Identifies a transaction as an Estimated Authorization COF transaction. | | U07 | Merchant | No | No | Identifies a transaction as a Delayed Charges COF transaction. For example, a hotel might charge a customer for room damages after the guest has already checked out. | | U08 | Merchant | No | No | Identifies a transaction as an Incremental COF transaction. For example, a hotel which authorized a customer’s card for one night at check-in might increase the authorization amount to cover two nights when the customer decides to extend their stay. Shift4 automatically detects this scenario and sends the appropriate value to the processor. | | U09 | Merchant | No | No | Identifies a transaction as a No Show COF transaction. For example, a hotel might charge a customer who does not show up for a booked stay. | See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for additional details.
        - `recurringExpiry` string — Date after which no further authorizations shall be performed. This field is limited to 8 characters, and the accepted format is YYYYMMDD. **Conditional: This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `recurringFrequency` string — Indicates the minimum number of days between authorizations. **Conditional: 'This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `transactionId` string — This field is returned in the initial COF response, and ties subsequent COF transactions to the original authorization. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
        - `transactionLinkId` string — A unique identifier assigned to each transaction to link related events throughout the transaction lifecycle. This field is supported for Mastercard brand only. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionLinkId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionLinkId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
      - `hotel` HotelCheckOut — **Conditional: Utilize this object for Hotel transactions**
        - `arrivalDateTime` string — Arrival date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the arrival date needs to be one day before the sale date.
        - `departureDateTime` string — Departure date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the departure date needs to be the day of the sale.
        - `primaryChargeType` 1 | 2 | 3 — Guest’s transaction type at a hotel. Value|Description -----|----------- 1 | Lodging 2 | Restaurant 3 | Gift Shop
        - `specialCode` 1 | 2 | 3 | 4 | 5 | 6 — This field is used to provide additional detail for lodging transactions. If a lodging charge does not match one of the listed descriptions, the default value of ‘1’ should be sent in the request. When a value of ‘4’ is sent, the `additionalCharges` field needs to be sent as well. Value|Description -----|----------- 1 | No Special Code 2 | Assured Reservation/No Show 3 | Advance Deposit 4 | Delayed Charge 5 | Express Check-Out Service 6 | Assured Reservation/Normal
        - `additionalCharges` HotelAdditionalCharges — Reason codes for additional charges in a lodging sale request at the time a consumer checks out.
          - `giftShop` 'Y' | 'N'
          - `laundry` 'Y' | 'N'
          - `miniBar` 'Y' | 'N'
          - `other` 'Y' | 'N'
          - `restaurant` 'Y' | 'N'
          - `telephone` 'Y' | 'N'
        - `roomRates` HotelRoomRates[] — Room rates broken down by rate and number of nights.
          - `nights` integer — The number of nights being charged at this rate.
          - `rate` number — The per night room rate.
      - `purchaseCard` PurchaseCard, required
        - `customerReference` string, required — A unique value used to identify the consumer or transaction. If a merchant has a significant amount of revenue from purchasing card customers, the interface would use this field to collect the consumer’s purchase order or employee identification number. In lodging transactions, this may be unique transaction details, such as a reservation code or third-party booking source. This field is part of Level 2 card data.
        - `destinationPostalCode` string, required — When items are shipped, the ZIP/postal code to which merchandise will be shipped; otherwise, the ZIP/postal code where the goods or services are rendered. This field is part of Level 2 card data.
        - `productDescriptors` string[], required — A text description of the items purchased or services sold. This can be a generic text description of what the merchant sells (such as “Groceries”) or specific transaction data (such as the name of the item sold). At least one product descriptor field is required in a sale or authorization request. Note: The productDescriptors array is limited to 4 elements. Each element can contain a maximum of 40 characters.
      - `vendorReference` string — Optional field for information that can be searched in the merchant portal.
    - `card` object, required
      - `expirationDate` integer — **Conditional: Send only when card data is manually entered or when using a token. This field should not be specified when using an encrypted device.** Card expiration date in MMYY format. This value should only be populated in the initial sale/authorization request.
      - `present` 'Y' | 'N' — **Conditional: Send in the initial authorization/sale request** Indicates whether a card was present (‘Y’) or not (‘N’) at the time a transaction took place. This should be set appropriately in the initial authorization/sale request. In subsequent requests, this field should be left blank or should not be sent. **Note:** Subsequent request here does not apply to the secondary request for card on file type transactions or reuse of the same card. An example of a subsequent request would be a capture after an authorization. You would not include `card.present` in the capture, which is the subsequent request. Another example is when performing an incremental authorization where you perform an authorization, followed by an incremental authorization then a capture. The second authorization (incremental) and the capture are the subsequent requests where you would not include `card.present`.
      - `token` CardTokenRequiredLegacy, required
        - `value` string, required — This field is used to specify a card token. Whenever CHD is sent in a request, a card token will be returned in this field. Your interface should be designed to store this card token for future use. The latest card token received should be used in any subsequent request that references the same card data.
        - `serialNumber` string — In requests that require the use of a shared card token that is held by another merchant account, such as in a TokenStore or TokenShare®, this field is used to specify the serial number for the account where the card token is stored.
      - `securityCode` CardSecurityCode — **Conditional: Send only when card data is manually entered. This object should not be specified when using an encrypted device. This object should be sent for initial card on file request but is not required for subsequent merchant initiated charges.**
        - `indicator` '0' | '1' | '2' | '9', required — This field indicates the presence of a CSC. Value|Description -----|----------- 0 | CSC not provided by user. 1 | CSC provided. 2 | CSC illegible. 9 | CSC not on card, or card did not have a CSC.
        - `result` 'M' | 'N' | 'P' | 'S' | 'U' | 'Y' | '1' | '2' | '3' — **Conditional: Returned if `card.securityCode.indicator` and `card.securityCode.value` are sent in the request.** The result of a CSC check. This field will be used by Shift4 to determine the value sent in the `card.securityCode.valid` field (based on the merchant’s list of accepted verification results as configured with Shift4). Value|Description -----|------------ M | CSC matched. N | CSC did not match. P | CSC not processed. S | CSC should have been present. U | Issuer unable to process. Y | CVC1 incorrect. 1 | CSC Unavailable - processor / card type does not support this parameter. 2 | An unrecognised result code was returned by the processor. 3 | No result code was returned by the processor.
        - `valid` string — **Conditional: Returned if `card.securityCode.indicator` and `card.securityCode.value` are sent in the request.** A simplified CSC check result based on the value in the `card.securityCode.result` field and the merchant’s accepted verification results as configured with Shift4. The value returned will be ‘Y’ if CSC verification passed or ‘N’ if CSC verification did not pass.
        - `value` string, required — The three- or four-digit Card Security Code found on a payment card. This value should only be sent in an initial sale/authorization request. It should not be stored by the interface. When sending `card.securityCode.value`, `card.securityCode.indicator` must also be sent.
    - `customer` Customer
      - `addressLine1` string — Cardholder’s street address exactly as it appears on their billing statement. This field is used in AVS.
      - `firstName` string — Specifies a consumer’s first name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `middleName` string — Specifies a consumer’s middle name.
      - `lastName` string — Specifies a consumer’s last name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `postalCode` string — Cardholder’s ZIP/postal code from their billing statement. This field is used in AVS. Do not include special characters. **Note: This field only allows alphanumeric characters (a-z, A-Z, 0-9). Special characters including - are not allowed. If you are sending in zip+4 you must not include the dash so 89134-1234 would be sent as 891341234**
      - `emailAddress` string — Customer email address.
      - `ipAddress` string — Public source IP Address where the request originates, not the IP Address of the web server.
    - `receiptColumns` integer — Send this field if you want Shift4 to format the receipt text instead of returning individual fields. The value sent will correlate to the column width of the formatted receipt that we return. (This also allows the receipt text to wrap to fit the paper size of the printed receipt.) See the [Printing Receipts](/guides/core-concepts/printing-receipts) section of this document for more information on formatted receipts.
    - `currencyCode` string, ISO 4217 3 Character Alphabetic Code — Transaction currency code. See the [Currency Codes](/guides/appendices/currency-codes) section for details. **Note: This is currently supported when processing for a merchant outside of the US and Canada. If processing for a US or Canadian merchant then this field will be ignored and the transaction will process in the merchant's configured currency.**
    - `apiOptions` string[] — API Options modify the request being made. See the [API Options](/guides/appendices/api-options.md) section for more information.
    - `reportingData` ReportingData — Used to send non-payment related data for reporting purposes.
      - `customerInfo` ReportingDataCustomerInfo[] — Array of customer information objects. The maximum number of customer information objects that can be sent is 10.
        - `firstName` string — Customer's first name
        - `lastName` string — Customer's last name
        - `dateOfBirth` string — Customer's date of birth in MMDDYYYY format
        - `gender` string — Customer's gender
        - `baggage` string — Description for the customer's baggage
        - `seats` string — Customer's assigned seat
        - `boardingPriority` string — Customer's boarding priority
      - `pspData` ReportingDataPspData — Payment service provider (PSP) metadata for third-party processed transactions.
        - `pspId` string — PSP identifier / label
        - `pspMid` string — PSP merchant identifier (MID).
        - `pspTid` string — PSP terminal identifier (TID).
        - `pspTxnTraceNo` string — PSP transaction trace number.
        - `pspTxnDate` string, date — PSP transaction date (YYYYMMDD).
        - `pspTxnTime` string, 24-hour time — PSP transaction time (hhmmss)
        - `pspResponseCode` string — PSP host response code.
        - `pspResponseText` string — PSP host response description/text.
    - `statementSuffix` string — Custom description that will be appended to the merchant name on the customer's statement. For most card brands, the merchant DBA name can be a maximum of 25 characters. Sending this value will cause the merchant name to be truncated to 9 characters. Shift4 will add an asterisk between the merchant name and the `statementSuffix` value. For example, for a merchant named `Joe's Warehouse Emporium` that processes a transaction with `statementSuffix` value of `KDNYZUHQ1`, the merchant statement will show as `Joe's War*KDNYZUHQ1`. **Note: The value that displays on customer statements from card issuers is beyond Shift4's control. We will submit the transaction data as described above, however issuers may modify or truncate that data as they see fit. To best accommodate different issuer limitations, we will truncate the merchant name to the minimum possible value (9 characters) in order to attempt to leave the most room for the statementSuffix to populate on issuer statements.**
  - TransactionsManualsaleP2peIdtech
    - `dateTime` string, ISO 8601, required — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
    - `amount` AmountObjectNoSurcharge, required — Object containing information regarding the amount being requested. The `total` field within the object is required and specifies the amount being requested. All other fields are for informational purposes and must also be included in the `total` field. For example, a purchase of $100 with a $20 tip and $8 tax would be `128.00` in the `total` field, `20.00` in the `tip` field and `8.00` in the `tax` field. Note: For merchants that are configured to allow multiple currencies, the amount fields can specify up to three decimal places. However, the number of decimal places can not exceed the number allowed for the specified currency. See the [Currency Codes](/guides/appendices/currency-codes) section for details.
      - `total` number, required — The amount being charged for a particular transaction. If other amount fields are sent, they must be included in the total amount. Amount cannot be zero.
      - `tax` number, required — The amount of sales tax charged for a transaction. The tax amount is used by businesses to track tax expenses for accounting purposes. Identifying the tax amount also helps consumers understand the total amount that they were billed. This field is part of Level 2 card data.
      - `taxIndicator` 'Y' | 'N' — Value|Description -----|----------- Y | Tax is included N | Tax is not included
      - `cashback` number — Specifies the cashback amount in a transaction. When using a UTG-controlled PIN pad with the ALLOWCASHBACK API Option, this field will return the cashback amount requested by the consumer. The interface can also send the desired cashback amount in a request by adding it to the `amount.total` and including it in the `amount.cashback` field. This will bypass prompting the consumer for a cashback amount.
      - `iiasAmounts` IIASAmounts[] — **Conditional: Send in the request if processing for a health care merchant.** For Vision related charges you must send only `iiasAmounts.type = 4V` and the corresponding `iiasAmounts.amount` value. For all other charges, the first entry in the array should have an amount representing the total of all healthcare costs, and `iiasAmounts.type = 4S`. Any subsequent entries should contain the subtotal for each of the other expense types involved in this transaction.
        - `amount` number — The subtotal for this type of healthcare expenses.
        - `type` '4O' | '4S' | '4T' | '4U' | '4V' | '4W' | '4X' — This code classifies eligible healthcare expenses. Value|Description -----|----------- 4O | Cash Disbursement (Discover Only) – Amount of Cash Back Being Requested 4S | Healthcare (Visa/MC Only) – Qualified Medical Expenses or Over-the-Counter 4T | Transit (Visa Only) – Transit Fare Media (e.g., Commuter and Parking Passes, Mass Transit Vouchers, and Tickets) 4U | RX (Visa/MC Only) 4V | Vision (Visa Only) 4W | Clinical (Visa Only) 4X | Dental (Visa Only)
      - `tip` number — **Conditional: Send in the request if a tip is included.** The tip amount of the transaction.
      - `checkTotal` number — Optional field specifying the total amount of the entire bill/invoice that this transaction is part of. It can be larger than `amount.total` in scenarios where the check is being split or if a portion of the check was already paid in cash or another form of payment.
    - `clerk` Clerk, required
      - `numericId` integer, required — A number used to identify the point-of-sale (POS) or property management system (PMS) clerk or user. The value cannot be 0. An interface must be able to dynamically populate this field (not use a hardcoded value), unless the interface will be used exclusively for e-commerce.
    - `transaction` object, required
      - `invoice` string, required — 10-digit invoice number assigned by the interface to identify a transaction. An invoice number serves as a unique key that identifies a transaction within a batch in Shift4's Gateway. **Note: For US and Canadian processing: Although the invoice number is sent as a JSON string it is a numeric value. No alpha characters are allowed.** **For processing outside of the US and Canada alpha characters are allowed.**
      - `authorizationCode` string, required — The authorization code provided by the consumer’s issuing bank. It is provided in a response if an online authorization or sale request is approved. Following a referral response, it is also specified in [Manual Sale](/apis/payments-platform-rest/openapi/transactions/manualsale) requests.
      - `manualTranId` string — This is typically used in a Referral. If a ManualTranID is returned by the issuer with the Auth code, it should be sent to the processor in the ManualTranid field.
      - `notes` string — A free-form notes field that supports the use of HTML tags. This can be used for reference in [Lighthouse Transaction Manager](https://ltm.shift4test.com/) and is not sent to the authorization host. Escaped quotation marks should not be sent in the Notes field.
      - `businessDate` string, ISO 8601 — Desired business date of a transaction. Include when overriding the existing business date of a transaction. The overriding date may be earlier or later than the existing date. (yyyy-mm-dd)
      - `amex` TransactionAmex
        - `propertyCode` string — The code that contains a Merchant-assigned store or location number (or name) that uniquely identifies where the transaction took place.
      - `auto` AutoCheckOut — **Conditional: Utilize this object for Auto Rental transactions**
        - `distanceDriven` integer — The amount of distance the cardholder drove the vehicle.
        - `distanceUnit` 'M' | 'K' — The unit of measure that corresponds to the `distanceDriven` field. Value|Description -----|----------- M | Miles K | Kilometers
        - `lateAdjustment` number — A dollar amount for late adjustment fees for an auto rental, including refueling charges, a surcharge, or charges for damage incurred during use.
        - `noShowIndicator` 'Y' | 'N' — Indicates whether or not the cardholder picked up a reserved rental car. Value|Description -----|----------- Y | customer did not pick up the rental car N | customer did pick up the rental car
        - `additionalCharges` AutoAdditionalCharges — The codes used to provide a reason for additional charges in an auto rental sale. Multiple codes can be specified for the same transaction.
          - `gasoline` 'Y' | 'N'
          - `lateReturn` 'Y' | 'N'
          - `mileage` 'Y' | 'N'
          - `oneWayServiceFee` 'Y' | 'N'
          - `violationFee` 'Y' | 'N'
        - `driver` AutoDriver
          - `license` string — The cardholder's driver's license number.
          - `name` string — In a sale/authorization request for an auto rental, the customer’s name exactly as it appears on their driver’s license.
          - `taxNumber` string — This field contains the driver’s Tax Identification Number.
        - `rental` AutoRental — Information relating to where the rental card was picked up.
          - `agreement` string — Contract number for an auto rental agreement.
          - `city` string — City where rental car was picked up.
          - `countryCode` string — Country where rental card was picked up.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was picked up in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was picked up in U.S. postal abbreviation format.
        - `return` AutoReturn — Information relating to where the rental car was returned
          - `city` string — City where rental car was returned.
          - `countryCode` string — Country where rental card was returned.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was returned in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was returned in U.S. postal abbreviation format.
      - `airline` AirlineRequest — **Conditional: Utilize this object for Airline transactions in Authorization/Sale requests when possible. If unable to provide this data at Authorization, this object must be sent in subsequent Capture requests for the transaction.**
        - `carrierCode` string, required — The code of the airline carrier issuing the ticket.
        - `carrierName` string, required — The name of the airline carrier issuing the ticket.
        - `conjunctionTicketIndicator` 'Y' | 'N', required — Indicates whether the itinerary contains more than four segments of travel. Value | Description -------|------------------- Y | Yes N | No
        - `documentType` '01' | '02' | '03' | '04' | '05' | '06' | '07' | '08' | '09' | '10' | '11' | '12' | '13' | '14' | '15' | '16' | '17' | '18' | '19' | '20' | '21' | '22' | '23' | '24' | '25' | '26' | '27' | '28' | '29' | '30' | '31' | '32' | '33' | '34' | '35' | '36' | '37' | '38' | '39' | '41' | '42' | '43' | '44' | '45' | '46' | '47' | '48' | '49' | '50' | '51' | '52' | '60' | '64' | '65' | '66' | '67' | '68' | '69' | '70' | '71' | '72' | '73' | '74' | '75' | '76' | '77' | '78' | '79' | '80' | '81' | '82' | '83' | '84' | '85' | '86' | '87' | '88' | '89' | '90' | '91' | '92' | '93', required — This field contains the airline Document Type code, which indicates the purpose of this transaction. This information may appear on the descriptive bill on the Cardmember's statement, or be used to resolve billing inquiries and disputes. The codes entered in the Transaction Type and Document Type fields are used together to describe the purpose of this transaction. Value | Description ------|--------------- 01 | Passenger Ticket 02 | Additional Collection 03 | Excess Baggage 04 | Misc. Charge Order (MCO) / Prepaid Ticket Auth 05 | Special Service Ticket 06 | Supported Refund 07 | Unsupported Refund 08 | Lost Ticket Application 09 | Tour Order Voucher 10 | Ticket by Mail 11 | Undercharge Adjustment 12 | Group Ticket 13 | Exchange Adjustment 14 | SPD/Air Freight 15 | In-flight Adjustment 16 | Agency Passenger Ticket 17 | Agency Tour Order/Voucher 18 | Agency Misc. Charge Order (MCO) 19 | Agency Exchange Order 20 | Agency Group Ticket 21 | Debit Adjustment Duplicate Refund/Use 22 | In-flight Merchandise Ordered 23 | Catalogue Merchandise Ordered 24 | In-flight Phone Charges 25 | Frequent Flyer Fee/Purchase 26 | Kennel Charge 27 | Animal Transportation Charge 28 | Firearms Case 29 | Upgrade Charge 30 | Credit Unused Transportation 31 | Credit Class of Service Adjustment 32 | Credit Denied Boarding 33 | Credit Misc. Refund 34 | Credit Lost Ticket Refund 35 | Credit Exchange Refund 36 | Credit Overcharge Adjustment 37 | Credit Multiple Unused Tickets 38 | Exchange Order 39 | Self-Service Ticket(s) 41 | In-flight Duty Free Purchase 42 | Senior Citizen Discount Booklets 43 | Club Membership Fee 44 | Coupon Book 45 | In-flight Charges 46 | Tour Deposit 47 | Frequent Flyer Overnight Delivery Charge 48 | Frequent Flyer Fulfillment 49 | Small Package Delivery 50 | Vendor Sale 51 | Miscellaneous Tax(es) Fee(s) 52 | Travel Agency Fee 60 | Vendor Refund Credit 64 | Duty Free Sale 65 | Preferred Seat Upgrade 66 | Cabin Upgrade 67 | Lounge/Club Access or Day Pass 68 | Agent Assisted Reservation. Ticketing Fee 69 | Ticket Change or Cancel Fee 70 | Trip Insurance 71 | Unaccompanied Minor 72 | Standby Fee 73 | Curbside Baggage 74 | Inflight Medical Equipment 75 | Ticket or Pass Print Fee 76 | Checked Sporting/Special Equipment 77 | Dry Ice Fee 78 | Mail/Postage Fee 79 | Club Membership Fee - Temporary/Trial 80 | Frequent Flyer Activation/Reinstatement 81 | Gift Certificate 82 | Onboard/Inflight Prepaid Voucher 83 | Optional Services Fee 84 | Advanced Purchase - Excess Baggage 85 | Advanced Purchase - Preferred Seat Upgrade 86 | Advanced Purchase - Cabin Upgrade 87 | Advanced Purchase - Optional Services 88 | WiFi 89 | Packages 90 | Inflight Entertainment/Internet Access 91 | Overweight Bag Fee 92 | Sleep Sets 93 | Special Purchase Fee
        - `electronicTicketIndicator` 'Y' | 'N', required — Indicates if an electronic ticket was issued. Value | Description -------|------------------- Y | Yes N | No
        - `internetIndicator` 'Y' | 'N', required — Indicates if this is an internet transaction. Value | Description -------|------------------- Y | Yes N | No
        - `issueDate` string, ISO 8601, required — The date the ticket was issued to the customer. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `numberOfCities` number, required — The number of airports or cities for each leg on the ticket (including origination and destination cities).
        - `numberOfCarriers` number, required — This field contains the number of airline carriers.
        - `numberOfPassengers` number, required — The number of passengers in the transaction.
        - `passengerArrivalDate` string, ISO 8601, required — Date that the ticket holder is scheduled to arrive at their destination at the time of issuance of the original ticket. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerDepartureDate` string, ISO 8601, required — Date that the ticket holder is scheduled to depart at the time of issuance of the original ticket. The date may be a future one. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerNameRecord` string, required — A passenger name record (PNR) is a record in the database of a computer reservation system (CRS) that contains the itinerary for a passenger or a group of passengers travelling together
        - `restrictedTicketIndicator` '0' | '1', required — Indicates whether this ticket is non-refundable. Value | Description -------|------------------- 0 | No restriction 1 | Restricted (non-refundable) ticket
        - `ticketChangeIndicator` 'C' | 'N', required — Indicates why a ticket was changed. This field should contain spaces or one of the below codes. Value | Description -------|--------------- C | Change to existing ticket N | New ticket
        - `ticketTranType` 'TKT' | 'REF' | 'EXC' | 'MSC', required — This field contains the ticket transaction type code assigned to this transaction. Value | Description -------|--------------- TKT | Ticket Purchase REF | Refund EXC | Exchange Ticket MSC | Miscellaneous (non-Ticket Purchase- and non-Exchange Ticket-related transactions only)
        - `typeIndicator` 'R' | 'O' | 'M', required — Indicates if this ticket is a round trip, multi-city, or one-way ticket. Value | Description -------|--------------- R | Round-Trip O | One Way M | Multi-City
        - `tickets` AirlineTickets[], required — Array of ticket number and passenger name. Note: At least one instance of ticket number and passenger name info should be provided.
          - `passengerName` string, required — Name of the passenger to whom the ticket was issued. This field contains the Passenger Name in format: `SURNAME FIRSTNAME MIDDLEINITIAL TITLE` Example: "Doe Jane M Mrs"
          - `ticketNumber` string, required — The ticket number provided by the Carrier for the passenger.
          - `ticketFare` number, required — Ticket fare is the total amount for each ticket, including service fee or any other fee for each ticket.
        - `flightLegs` AirlineFlightLegs[], required — Array of flight trip leg info. Maximun 4 legs to a trip allowed. Note: At least one instance of flight trip leg info should be provided.
          - `carrierCode` string, required — Code indicating name of carrier (United Airlines, Jet Blue, etc.) for the leg.
          - `couponNumber` number — Number of coupons in the ticket for the leg.
          - `destAirportCode` string, required — Indicates destination city's airport code for the leg.
          - `fare` number, required — This field contains the total Fare for this trip segment. This is not the total amount billed to the customer.
          - `fareBasis` string, required — This field contains primary and secondary discount codes that indicate the class of service and fare level associated with the ticket for the leg. Truncate at 24 bytes, if necessary.
          - `flightNumber` string, required — Number of the airline flight to be taken on Leg of the trip.
          - `legArrivalDateTime` string, ISO 8601, required — The date and time the flight is scheduled to arrive for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `legDepartureDateTime` string, ISO 8601, required — The date and time the flight is scheduled to depart for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `originAirportCode` string, required — Indicates origination city's airport code for the leg.
          - `serviceClass` string, required — Indicates service class for leg. Value | Description -------|--------------- FC | First Class BC | Business Class EC | Economy/Coach Class
          - `stopOverCode` string, required — Indicates whether a stopover is allowed on this ticket for leg. The entry must be a D, O, or X. Value | Description -------|--------------- O | Stopover allowed X | Stopover not allowed D | Destination point
          - `tripLegInfo` string, required — Description of leg or stage of trip.
        - `ancillaryServices` AirlineAncillaryServices[] — Array of ancillary service code and fees. **Conditional: Send if any ancillary services were charged.**
          - `serviceCode` 'BF' | 'BG' | 'CF' | 'CG' | 'CO' | 'FF' | 'GF' | 'GT' | 'IE' | 'LG' | 'MD' | 'ML' | 'OT' | 'PA' | 'PT' | 'SA' | 'SB' | 'SF' | 'ST' | 'TS' | 'UN' | 'UP' | 'WI', required — This field describes the type of service that has been provided. Value | Description ------|--------------- BF | Bundled Service BG | Baggage Fee CF | Change Fee CG | Cargo CO | Carbon Offset FF | Frequent Flyer GF | Gift Card GT | Ground Transport IE | In-Flight Entertainment LG | Lounge MD | Medical ML | Meal/Beverage OT | Other PA | Passenger Assist Fee PT | Pets SA | Seat Fees SB | Standby SF | Service Fee ST | Store TS | Travel Service UN | Unaccompanied Travel UP | Upgrades WI | Wi-Fi
          - `serviceFee` number, required — This field contains the amount associated with the value provided in ancillary Service Code.
        - `travelAgencyCode` string — Code identifying travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `travelAgencyName` string — Name of travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `exchangeTicketNumber` string — The original ticket number that was replaced by a new ticket number.
      - `cardOnFile` CardOnFile — **Conditional: Send this object when the transaction being performed is using a card on file or when the request will result in storing a card on file.** See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for more information.
        - `type` 'S01' | 'S02' | 'U01' | 'U02' | 'U03' | 'U04' | 'U05' | 'U06' | 'U07' | 'U08' | 'U09' — This field specifies the type of the card-on-file transaction. Below is a table showing the valid values for use cases where the cardholder is entering their card data to store on file. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | S01 | Cardholder | No | Yes | Used when the initial transaction/card verification request is not for a recurring payment. | | S02 | Cardholder | Yes | Yes | Used when the initial transaction/card verification request is for a recurring payment. Requires sending `cardOnFile.recurringFrequency` and `cardOnFile.recurringExpiry` | Below is a table showing the valid values for uses cases where you already have a card on file and are using that existing card to process a transaction. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | U01 | Cardholder | No | Yes | Unscheduled transaction using the card on file initiated by the cardholder | | U02 | Merchant | No | No | Unscheduled transaction using the card on file initiated by the merchant | | U03 | Merchant | Yes | No | Merchant initiated recurring payment using the card on file | | U04 | Merchant | No | No | Identifies a transaction as a Reauthorization COF transaction. | | U05 | Merchant | No | No | Identifies a transaction as a Resubmission COF transaction. Only certain merchant categories are able to send a resubmission, and it can only be done if the original authorization attempt was declined due to insufficient funds. | | U06 | Merchant | No | No | Identifies a transaction as an Estimated Authorization COF transaction. | | U07 | Merchant | No | No | Identifies a transaction as a Delayed Charges COF transaction. For example, a hotel might charge a customer for room damages after the guest has already checked out. | | U08 | Merchant | No | No | Identifies a transaction as an Incremental COF transaction. For example, a hotel which authorized a customer’s card for one night at check-in might increase the authorization amount to cover two nights when the customer decides to extend their stay. Shift4 automatically detects this scenario and sends the appropriate value to the processor. | | U09 | Merchant | No | No | Identifies a transaction as a No Show COF transaction. For example, a hotel might charge a customer who does not show up for a booked stay. | See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for additional details.
        - `recurringExpiry` string — Date after which no further authorizations shall be performed. This field is limited to 8 characters, and the accepted format is YYYYMMDD. **Conditional: This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `recurringFrequency` string — Indicates the minimum number of days between authorizations. **Conditional: 'This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `transactionId` string — This field is returned in the initial COF response, and ties subsequent COF transactions to the original authorization. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
        - `transactionLinkId` string — A unique identifier assigned to each transaction to link related events throughout the transaction lifecycle. This field is supported for Mastercard brand only. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionLinkId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionLinkId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
      - `hotel` HotelCheckOut — **Conditional: Utilize this object for Hotel transactions**
        - `arrivalDateTime` string — Arrival date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the arrival date needs to be one day before the sale date.
        - `departureDateTime` string — Departure date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the departure date needs to be the day of the sale.
        - `primaryChargeType` 1 | 2 | 3 — Guest’s transaction type at a hotel. Value|Description -----|----------- 1 | Lodging 2 | Restaurant 3 | Gift Shop
        - `specialCode` 1 | 2 | 3 | 4 | 5 | 6 — This field is used to provide additional detail for lodging transactions. If a lodging charge does not match one of the listed descriptions, the default value of ‘1’ should be sent in the request. When a value of ‘4’ is sent, the `additionalCharges` field needs to be sent as well. Value|Description -----|----------- 1 | No Special Code 2 | Assured Reservation/No Show 3 | Advance Deposit 4 | Delayed Charge 5 | Express Check-Out Service 6 | Assured Reservation/Normal
        - `additionalCharges` HotelAdditionalCharges — Reason codes for additional charges in a lodging sale request at the time a consumer checks out.
          - `giftShop` 'Y' | 'N'
          - `laundry` 'Y' | 'N'
          - `miniBar` 'Y' | 'N'
          - `other` 'Y' | 'N'
          - `restaurant` 'Y' | 'N'
          - `telephone` 'Y' | 'N'
        - `roomRates` HotelRoomRates[] — Room rates broken down by rate and number of nights.
          - `nights` integer — The number of nights being charged at this rate.
          - `rate` number — The per night room rate.
      - `purchaseCard` PurchaseCard, required
        - `customerReference` string, required — A unique value used to identify the consumer or transaction. If a merchant has a significant amount of revenue from purchasing card customers, the interface would use this field to collect the consumer’s purchase order or employee identification number. In lodging transactions, this may be unique transaction details, such as a reservation code or third-party booking source. This field is part of Level 2 card data.
        - `destinationPostalCode` string, required — When items are shipped, the ZIP/postal code to which merchandise will be shipped; otherwise, the ZIP/postal code where the goods or services are rendered. This field is part of Level 2 card data.
        - `productDescriptors` string[], required — A text description of the items purchased or services sold. This can be a generic text description of what the merchant sells (such as “Groceries”) or specific transaction data (such as the name of the item sold). At least one product descriptor field is required in a sale or authorization request. Note: The productDescriptors array is limited to 4 elements. Each element can contain a maximum of 40 characters.
      - `vendorReference` string — Optional field for information that can be searched in the merchant portal.
    - `p2pe` P2PEType0102IDTECH, required
      - `data` string, required — The full output of a P2PE keypad/magnetic swipe reader (MSR).
      - `format` '01' | '02', required — Classifies the type of payment device being used for P2PE. Value|Description -----|----------- 01 | IDTech Enhanced Encryption format (Keyboard Mode) 02 | IDTech Enhanced Encryption format (USB HID Mode)
    - `customer` Customer
      - `addressLine1` string — Cardholder’s street address exactly as it appears on their billing statement. This field is used in AVS.
      - `firstName` string — Specifies a consumer’s first name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `middleName` string — Specifies a consumer’s middle name.
      - `lastName` string — Specifies a consumer’s last name. This field is used in AVS. If the interface sends this field, the value specified by the interface will be returned in the response, unless the API Option [USECARDNAME](/guides/appendices/api-options#usecardname) is included in the request and a Commerce Engine or UTG-controlled PIN pad is in use. If the interface does not send the `customer` object, the consumer's name will be returned in the `customer` object if the name is present in the card's EMV or track data.
      - `postalCode` string — Cardholder’s ZIP/postal code from their billing statement. This field is used in AVS. Do not include special characters. **Note: This field only allows alphanumeric characters (a-z, A-Z, 0-9). Special characters including - are not allowed. If you are sending in zip+4 you must not include the dash so 89134-1234 would be sent as 891341234**
      - `emailAddress` string — Customer email address.
      - `ipAddress` string — Public source IP Address where the request originates, not the IP Address of the web server.
    - `card` object
      - `present` 'Y' | 'N' — **Conditional: Send in the initial authorization/sale request** Indicates whether a card was present (‘Y’) or not (‘N’) at the time a transaction took place. This should be set appropriately in the initial authorization/sale request. In subsequent requests, this field should be left blank or should not be sent. **Note:** Subsequent request here does not apply to the secondary request for card on file type transactions or reuse of the same card. An example of a subsequent request would be a capture after an authorization. You would not include `card.present` in the capture, which is the subsequent request. Another example is when performing an incremental authorization where you perform an authorization, followed by an incremental authorization then a capture. The second authorization (incremental) and the capture are the subsequent requests where you would not include `card.present`.
      - `type` 'CC' | 'DB' | 'GC' | 'HF' | 'PL' | 'YC' — An abbreviation used to specify the type of card that will be used when processing a transaction. If an interface sends a value that is not listed here, that value will be ignored. Value| Description -----|------------ CC | When using a UTG-controlled device, this value will force a card to process as credit. DB | When using a UTG-controlled device, this value will force a card to process as debit. When using a non-UTG-controlled PIN pad, this value must be sent when processing a debit transaction. GC | Gift Card HF | HSA/FSA Card PL | Private Label YC | IT’S YOUR CARD
    - `receiptColumns` integer — Send this field if you want Shift4 to format the receipt text instead of returning individual fields. The value sent will correlate to the column width of the formatted receipt that we return. (This also allows the receipt text to wrap to fit the paper size of the printed receipt.) See the [Printing Receipts](/guides/core-concepts/printing-receipts) section of this document for more information on formatted receipts.
    - `currencyCode` string, ISO 4217 3 Character Alphabetic Code — Transaction currency code. See the [Currency Codes](/guides/appendices/currency-codes) section for details. **Note: This is currently supported when processing for a merchant outside of the US and Canada. If processing for a US or Canadian merchant then this field will be ignored and the transaction will process in the merchant's configured currency.**
    - `apiOptions` string[] — API Options modify the request being made. See the [API Options](/guides/appendices/api-options.md) section for more information.
    - `reportingData` ReportingData — Used to send non-payment related data for reporting purposes.
      - `customerInfo` ReportingDataCustomerInfo[] — Array of customer information objects. The maximum number of customer information objects that can be sent is 10.
        - `firstName` string — Customer's first name
        - `lastName` string — Customer's last name
        - `dateOfBirth` string — Customer's date of birth in MMDDYYYY format
        - `gender` string — Customer's gender
        - `baggage` string — Description for the customer's baggage
        - `seats` string — Customer's assigned seat
        - `boardingPriority` string — Customer's boarding priority
      - `pspData` ReportingDataPspData — Payment service provider (PSP) metadata for third-party processed transactions.
        - `pspId` string — PSP identifier / label
        - `pspMid` string — PSP merchant identifier (MID).
        - `pspTid` string — PSP terminal identifier (TID).
        - `pspTxnTraceNo` string — PSP transaction trace number.
        - `pspTxnDate` string, date — PSP transaction date (YYYYMMDD).
        - `pspTxnTime` string, 24-hour time — PSP transaction time (hhmmss)
        - `pspResponseCode` string — PSP host response code.
        - `pspResponseText` string — PSP host response description/text.
    - `statementSuffix` string — Custom description that will be appended to the merchant name on the customer's statement. For most card brands, the merchant DBA name can be a maximum of 25 characters. Sending this value will cause the merchant name to be truncated to 9 characters. Shift4 will add an asterisk between the merchant name and the `statementSuffix` value. For example, for a merchant named `Joe's Warehouse Emporium` that processes a transaction with `statementSuffix` value of `KDNYZUHQ1`, the merchant statement will show as `Joe's War*KDNYZUHQ1`. **Note: The value that displays on customer statements from card issuers is beyond Shift4's control. We will submit the transaction data as described above, however issuers may modify or truncate that data as they see fit. To best accommodate different issuer limitations, we will truncate the merchant name to the minimum possible value (9 characters) in order to attempt to leave the most room for the statementSuffix to populate on issuer statements.**
  - TransactionsManualsaleP2peTdesdukptEmv
    - `dateTime` string, ISO 8601, required — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
    - `amount` AmountObjectNoSurcharge, required — Object containing information regarding the amount being requested. The `total` field within the object is required and specifies the amount being requested. All other fields are for informational purposes and must also be included in the `total` field. For example, a purchase of $100 with a $20 tip and $8 tax would be `128.00` in the `total` field, `20.00` in the `tip` field and `8.00` in the `tax` field. Note: For merchants that are configured to allow multiple currencies, the amount fields can specify up to three decimal places. However, the number of decimal places can not exceed the number allowed for the specified currency. See the [Currency Codes](/guides/appendices/currency-codes) section for details.
      - `total` number, required — The amount being charged for a particular transaction. If other amount fields are sent, they must be included in the total amount. Amount cannot be zero.
      - `tax` number, required — The amount of sales tax charged for a transaction. The tax amount is used by businesses to track tax expenses for accounting purposes. Identifying the tax amount also helps consumers understand the total amount that they were billed. This field is part of Level 2 card data.
      - `taxIndicator` 'Y' | 'N' — Value|Description -----|----------- Y | Tax is included N | Tax is not included
      - `cashback` number — Specifies the cashback amount in a transaction. When using a UTG-controlled PIN pad with the ALLOWCASHBACK API Option, this field will return the cashback amount requested by the consumer. The interface can also send the desired cashback amount in a request by adding it to the `amount.total` and including it in the `amount.cashback` field. This will bypass prompting the consumer for a cashback amount.
      - `iiasAmounts` IIASAmounts[] — **Conditional: Send in the request if processing for a health care merchant.** For Vision related charges you must send only `iiasAmounts.type = 4V` and the corresponding `iiasAmounts.amount` value. For all other charges, the first entry in the array should have an amount representing the total of all healthcare costs, and `iiasAmounts.type = 4S`. Any subsequent entries should contain the subtotal for each of the other expense types involved in this transaction.
        - `amount` number — The subtotal for this type of healthcare expenses.
        - `type` '4O' | '4S' | '4T' | '4U' | '4V' | '4W' | '4X' — This code classifies eligible healthcare expenses. Value|Description -----|----------- 4O | Cash Disbursement (Discover Only) – Amount of Cash Back Being Requested 4S | Healthcare (Visa/MC Only) – Qualified Medical Expenses or Over-the-Counter 4T | Transit (Visa Only) – Transit Fare Media (e.g., Commuter and Parking Passes, Mass Transit Vouchers, and Tickets) 4U | RX (Visa/MC Only) 4V | Vision (Visa Only) 4W | Clinical (Visa Only) 4X | Dental (Visa Only)
      - `tip` number — **Conditional: Send in the request if a tip is included.** The tip amount of the transaction.
      - `checkTotal` number — Optional field specifying the total amount of the entire bill/invoice that this transaction is part of. It can be larger than `amount.total` in scenarios where the check is being split or if a portion of the check was already paid in cash or another form of payment.
    - `clerk` Clerk, required
      - `numericId` integer, required — A number used to identify the point-of-sale (POS) or property management system (PMS) clerk or user. The value cannot be 0. An interface must be able to dynamically populate this field (not use a hardcoded value), unless the interface will be used exclusively for e-commerce.
    - `transaction` object, required
      - `invoice` string, required — 10-digit invoice number assigned by the interface to identify a transaction. An invoice number serves as a unique key that identifies a transaction within a batch in Shift4's Gateway. **Note: For US and Canadian processing: Although the invoice number is sent as a JSON string it is a numeric value. No alpha characters are allowed.** **For processing outside of the US and Canada alpha characters are allowed.**
      - `authorizationCode` string, required — The authorization code provided by the consumer’s issuing bank. It is provided in a response if an online authorization or sale request is approved. Following a referral response, it is also specified in [Manual Sale](/apis/payments-platform-rest/openapi/transactions/manualsale) requests.
      - `manualTranId` string — This is typically used in a Referral. If a ManualTranID is returned by the issuer with the Auth code, it should be sent to the processor in the ManualTranid field.
      - `notes` string — A free-form notes field that supports the use of HTML tags. This can be used for reference in [Lighthouse Transaction Manager](https://ltm.shift4test.com/) and is not sent to the authorization host. Escaped quotation marks should not be sent in the Notes field.
      - `businessDate` string, ISO 8601 — Desired business date of a transaction. Include when overriding the existing business date of a transaction. The overriding date may be earlier or later than the existing date. (yyyy-mm-dd)
      - `amex` TransactionAmex
        - `propertyCode` string — The code that contains a Merchant-assigned store or location number (or name) that uniquely identifies where the transaction took place.
      - `auto` AutoCheckOut — **Conditional: Utilize this object for Auto Rental transactions**
        - `distanceDriven` integer — The amount of distance the cardholder drove the vehicle.
        - `distanceUnit` 'M' | 'K' — The unit of measure that corresponds to the `distanceDriven` field. Value|Description -----|----------- M | Miles K | Kilometers
        - `lateAdjustment` number — A dollar amount for late adjustment fees for an auto rental, including refueling charges, a surcharge, or charges for damage incurred during use.
        - `noShowIndicator` 'Y' | 'N' — Indicates whether or not the cardholder picked up a reserved rental car. Value|Description -----|----------- Y | customer did not pick up the rental car N | customer did pick up the rental car
        - `additionalCharges` AutoAdditionalCharges — The codes used to provide a reason for additional charges in an auto rental sale. Multiple codes can be specified for the same transaction.
          - `gasoline` 'Y' | 'N'
          - `lateReturn` 'Y' | 'N'
          - `mileage` 'Y' | 'N'
          - `oneWayServiceFee` 'Y' | 'N'
          - `violationFee` 'Y' | 'N'
        - `driver` AutoDriver
          - `license` string — The cardholder's driver's license number.
          - `name` string — In a sale/authorization request for an auto rental, the customer’s name exactly as it appears on their driver’s license.
          - `taxNumber` string — This field contains the driver’s Tax Identification Number.
        - `rental` AutoRental — Information relating to where the rental card was picked up.
          - `agreement` string — Contract number for an auto rental agreement.
          - `city` string — City where rental car was picked up.
          - `countryCode` string — Country where rental card was picked up.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was picked up in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was picked up in U.S. postal abbreviation format.
        - `return` AutoReturn — Information relating to where the rental car was returned
          - `city` string — City where rental car was returned.
          - `countryCode` string — Country where rental card was returned.
          - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
          - `postalCode` string — Postal Code where rental car was returned in U.S. postal abbreviation format.
          - `region` string — Region (State) where rental car was returned in U.S. postal abbreviation format.
      - `airline` AirlineRequest — **Conditional: Utilize this object for Airline transactions in Authorization/Sale requests when possible. If unable to provide this data at Authorization, this object must be sent in subsequent Capture requests for the transaction.**
        - `carrierCode` string, required — The code of the airline carrier issuing the ticket.
        - `carrierName` string, required — The name of the airline carrier issuing the ticket.
        - `conjunctionTicketIndicator` 'Y' | 'N', required — Indicates whether the itinerary contains more than four segments of travel. Value | Description -------|------------------- Y | Yes N | No
        - `documentType` '01' | '02' | '03' | '04' | '05' | '06' | '07' | '08' | '09' | '10' | '11' | '12' | '13' | '14' | '15' | '16' | '17' | '18' | '19' | '20' | '21' | '22' | '23' | '24' | '25' | '26' | '27' | '28' | '29' | '30' | '31' | '32' | '33' | '34' | '35' | '36' | '37' | '38' | '39' | '41' | '42' | '43' | '44' | '45' | '46' | '47' | '48' | '49' | '50' | '51' | '52' | '60' | '64' | '65' | '66' | '67' | '68' | '69' | '70' | '71' | '72' | '73' | '74' | '75' | '76' | '77' | '78' | '79' | '80' | '81' | '82' | '83' | '84' | '85' | '86' | '87' | '88' | '89' | '90' | '91' | '92' | '93', required — This field contains the airline Document Type code, which indicates the purpose of this transaction. This information may appear on the descriptive bill on the Cardmember's statement, or be used to resolve billing inquiries and disputes. The codes entered in the Transaction Type and Document Type fields are used together to describe the purpose of this transaction. Value | Description ------|--------------- 01 | Passenger Ticket 02 | Additional Collection 03 | Excess Baggage 04 | Misc. Charge Order (MCO) / Prepaid Ticket Auth 05 | Special Service Ticket 06 | Supported Refund 07 | Unsupported Refund 08 | Lost Ticket Application 09 | Tour Order Voucher 10 | Ticket by Mail 11 | Undercharge Adjustment 12 | Group Ticket 13 | Exchange Adjustment 14 | SPD/Air Freight 15 | In-flight Adjustment 16 | Agency Passenger Ticket 17 | Agency Tour Order/Voucher 18 | Agency Misc. Charge Order (MCO) 19 | Agency Exchange Order 20 | Agency Group Ticket 21 | Debit Adjustment Duplicate Refund/Use 22 | In-flight Merchandise Ordered 23 | Catalogue Merchandise Ordered 24 | In-flight Phone Charges 25 | Frequent Flyer Fee/Purchase 26 | Kennel Charge 27 | Animal Transportation Charge 28 | Firearms Case 29 | Upgrade Charge 30 | Credit Unused Transportation 31 | Credit Class of Service Adjustment 32 | Credit Denied Boarding 33 | Credit Misc. Refund 34 | Credit Lost Ticket Refund 35 | Credit Exchange Refund 36 | Credit Overcharge Adjustment 37 | Credit Multiple Unused Tickets 38 | Exchange Order 39 | Self-Service Ticket(s) 41 | In-flight Duty Free Purchase 42 | Senior Citizen Discount Booklets 43 | Club Membership Fee 44 | Coupon Book 45 | In-flight Charges 46 | Tour Deposit 47 | Frequent Flyer Overnight Delivery Charge 48 | Frequent Flyer Fulfillment 49 | Small Package Delivery 50 | Vendor Sale 51 | Miscellaneous Tax(es) Fee(s) 52 | Travel Agency Fee 60 | Vendor Refund Credit 64 | Duty Free Sale 65 | Preferred Seat Upgrade 66 | Cabin Upgrade 67 | Lounge/Club Access or Day Pass 68 | Agent Assisted Reservation. Ticketing Fee 69 | Ticket Change or Cancel Fee 70 | Trip Insurance 71 | Unaccompanied Minor 72 | Standby Fee 73 | Curbside Baggage 74 | Inflight Medical Equipment 75 | Ticket or Pass Print Fee 76 | Checked Sporting/Special Equipment 77 | Dry Ice Fee 78 | Mail/Postage Fee 79 | Club Membership Fee - Temporary/Trial 80 | Frequent Flyer Activation/Reinstatement 81 | Gift Certificate 82 | Onboard/Inflight Prepaid Voucher 83 | Optional Services Fee 84 | Advanced Purchase - Excess Baggage 85 | Advanced Purchase - Preferred Seat Upgrade 86 | Advanced Purchase - Cabin Upgrade 87 | Advanced Purchase - Optional Services 88 | WiFi 89 | Packages 90 | Inflight Entertainment/Internet Access 91 | Overweight Bag Fee 92 | Sleep Sets 93 | Special Purchase Fee
        - `electronicTicketIndicator` 'Y' | 'N', required — Indicates if an electronic ticket was issued. Value | Description -------|------------------- Y | Yes N | No
        - `internetIndicator` 'Y' | 'N', required — Indicates if this is an internet transaction. Value | Description -------|------------------- Y | Yes N | No
        - `issueDate` string, ISO 8601, required — The date the ticket was issued to the customer. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `numberOfCities` number, required — The number of airports or cities for each leg on the ticket (including origination and destination cities).
        - `numberOfCarriers` number, required — This field contains the number of airline carriers.
        - `numberOfPassengers` number, required — The number of passengers in the transaction.
        - `passengerArrivalDate` string, ISO 8601, required — Date that the ticket holder is scheduled to arrive at their destination at the time of issuance of the original ticket. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerDepartureDate` string, ISO 8601, required — Date that the ticket holder is scheduled to depart at the time of issuance of the original ticket. The date may be a future one. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
        - `passengerNameRecord` string, required — A passenger name record (PNR) is a record in the database of a computer reservation system (CRS) that contains the itinerary for a passenger or a group of passengers travelling together
        - `restrictedTicketIndicator` '0' | '1', required — Indicates whether this ticket is non-refundable. Value | Description -------|------------------- 0 | No restriction 1 | Restricted (non-refundable) ticket
        - `ticketChangeIndicator` 'C' | 'N', required — Indicates why a ticket was changed. This field should contain spaces or one of the below codes. Value | Description -------|--------------- C | Change to existing ticket N | New ticket
        - `ticketTranType` 'TKT' | 'REF' | 'EXC' | 'MSC', required — This field contains the ticket transaction type code assigned to this transaction. Value | Description -------|--------------- TKT | Ticket Purchase REF | Refund EXC | Exchange Ticket MSC | Miscellaneous (non-Ticket Purchase- and non-Exchange Ticket-related transactions only)
        - `typeIndicator` 'R' | 'O' | 'M', required — Indicates if this ticket is a round trip, multi-city, or one-way ticket. Value | Description -------|--------------- R | Round-Trip O | One Way M | Multi-City
        - `tickets` AirlineTickets[], required — Array of ticket number and passenger name. Note: At least one instance of ticket number and passenger name info should be provided.
          - `passengerName` string, required — Name of the passenger to whom the ticket was issued. This field contains the Passenger Name in format: `SURNAME FIRSTNAME MIDDLEINITIAL TITLE` Example: "Doe Jane M Mrs"
          - `ticketNumber` string, required — The ticket number provided by the Carrier for the passenger.
          - `ticketFare` number, required — Ticket fare is the total amount for each ticket, including service fee or any other fee for each ticket.
        - `flightLegs` AirlineFlightLegs[], required — Array of flight trip leg info. Maximun 4 legs to a trip allowed. Note: At least one instance of flight trip leg info should be provided.
          - `carrierCode` string, required — Code indicating name of carrier (United Airlines, Jet Blue, etc.) for the leg.
          - `couponNumber` number — Number of coupons in the ticket for the leg.
          - `destAirportCode` string, required — Indicates destination city's airport code for the leg.
          - `fare` number, required — This field contains the total Fare for this trip segment. This is not the total amount billed to the customer.
          - `fareBasis` string, required — This field contains primary and secondary discount codes that indicate the class of service and fare level associated with the ticket for the leg. Truncate at 24 bytes, if necessary.
          - `flightNumber` string, required — Number of the airline flight to be taken on Leg of the trip.
          - `legArrivalDateTime` string, ISO 8601, required — The date and time the flight is scheduled to arrive for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `legDepartureDateTime` string, ISO 8601, required — The date and time the flight is scheduled to depart for the leg. The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm).
          - `originAirportCode` string, required — Indicates origination city's airport code for the leg.
          - `serviceClass` string, required — Indicates service class for leg. Value | Description -------|--------------- FC | First Class BC | Business Class EC | Economy/Coach Class
          - `stopOverCode` string, required — Indicates whether a stopover is allowed on this ticket for leg. The entry must be a D, O, or X. Value | Description -------|--------------- O | Stopover allowed X | Stopover not allowed D | Destination point
          - `tripLegInfo` string, required — Description of leg or stage of trip.
        - `ancillaryServices` AirlineAncillaryServices[] — Array of ancillary service code and fees. **Conditional: Send if any ancillary services were charged.**
          - `serviceCode` 'BF' | 'BG' | 'CF' | 'CG' | 'CO' | 'FF' | 'GF' | 'GT' | 'IE' | 'LG' | 'MD' | 'ML' | 'OT' | 'PA' | 'PT' | 'SA' | 'SB' | 'SF' | 'ST' | 'TS' | 'UN' | 'UP' | 'WI', required — This field describes the type of service that has been provided. Value | Description ------|--------------- BF | Bundled Service BG | Baggage Fee CF | Change Fee CG | Cargo CO | Carbon Offset FF | Frequent Flyer GF | Gift Card GT | Ground Transport IE | In-Flight Entertainment LG | Lounge MD | Medical ML | Meal/Beverage OT | Other PA | Passenger Assist Fee PT | Pets SA | Seat Fees SB | Standby SF | Service Fee ST | Store TS | Travel Service UN | Unaccompanied Travel UP | Upgrades WI | Wi-Fi
          - `serviceFee` number, required — This field contains the amount associated with the value provided in ancillary Service Code.
        - `travelAgencyCode` string — Code identifying travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `travelAgencyName` string — Name of travel agency if the ticket was issued by a travel agency. **Conditional: Send if a travel agency service was used.**
        - `exchangeTicketNumber` string — The original ticket number that was replaced by a new ticket number.
      - `cardOnFile` CardOnFile — **Conditional: Send this object when the transaction being performed is using a card on file or when the request will result in storing a card on file.** See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for more information.
        - `type` 'S01' | 'S02' | 'U01' | 'U02' | 'U03' | 'U04' | 'U05' | 'U06' | 'U07' | 'U08' | 'U09' — This field specifies the type of the card-on-file transaction. Below is a table showing the valid values for use cases where the cardholder is entering their card data to store on file. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | S01 | Cardholder | No | Yes | Used when the initial transaction/card verification request is not for a recurring payment. | | S02 | Cardholder | Yes | Yes | Used when the initial transaction/card verification request is for a recurring payment. Requires sending `cardOnFile.recurringFrequency` and `cardOnFile.recurringExpiry` | Below is a table showing the valid values for uses cases where you already have a card on file and are using that existing card to process a transaction. | Value | Initiator | Recurring | 3D Secure | Description | |--------|------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | U01 | Cardholder | No | Yes | Unscheduled transaction using the card on file initiated by the cardholder | | U02 | Merchant | No | No | Unscheduled transaction using the card on file initiated by the merchant | | U03 | Merchant | Yes | No | Merchant initiated recurring payment using the card on file | | U04 | Merchant | No | No | Identifies a transaction as a Reauthorization COF transaction. | | U05 | Merchant | No | No | Identifies a transaction as a Resubmission COF transaction. Only certain merchant categories are able to send a resubmission, and it can only be done if the original authorization attempt was declined due to insufficient funds. | | U06 | Merchant | No | No | Identifies a transaction as an Estimated Authorization COF transaction. | | U07 | Merchant | No | No | Identifies a transaction as a Delayed Charges COF transaction. For example, a hotel might charge a customer for room damages after the guest has already checked out. | | U08 | Merchant | No | No | Identifies a transaction as an Incremental COF transaction. For example, a hotel which authorized a customer’s card for one night at check-in might increase the authorization amount to cover two nights when the customer decides to extend their stay. Shift4 automatically detects this scenario and sends the appropriate value to the processor. | | U09 | Merchant | No | No | Identifies a transaction as a No Show COF transaction. For example, a hotel might charge a customer who does not show up for a booked stay. | See the [Card On File Transactions](/guides/advanced-concepts/card-on-file-transactions) section for additional details.
        - `recurringExpiry` string — Date after which no further authorizations shall be performed. This field is limited to 8 characters, and the accepted format is YYYYMMDD. **Conditional: This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `recurringFrequency` string — Indicates the minimum number of days between authorizations. **Conditional: 'This field is required if it's the first recurring transaction (`cardOnFile.type = S02`). This field is not needed if the transaction is not recurring or if the transaction is a subsequent recurring transaction.**
        - `transactionId` string — This field is returned in the initial COF response, and ties subsequent COF transactions to the original authorization. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
        - `transactionLinkId` string — A unique identifier assigned to each transaction to link related events throughout the transaction lifecycle. This field is supported for Mastercard brand only. For example, if a merchant runs a Sale on a card for the first time, they will receive a transactionLinkId back in the response. A month later, when the merchant wants to perform an additional Sale with the card on file, they would send a Sale request including the transactionLinkId they received from the first sale. **Conditional: Must be sent in subsequent COF requests if you are not processing with a Global Token Vault token. If using Global Token Vault tokens then this field is not required**
      - `hotel` HotelCheckOut — **Conditional: Utilize this object for Hotel transactions**
        - `arrivalDateTime` string — Arrival date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the arrival date needs to be one day before the sale date.
        - `departureDateTime` string — Departure date and time of a guest’s hotel stay ISO8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). For hotel transactions that are a straight sale (such as advanced deposit, no-show charge, and late charges), the departure date needs to be the day of the sale.
        - `primaryChargeType` 1 | 2 | 3 — Guest’s transaction type at a hotel. Value|Description -----|----------- 1 | Lodging 2 | Restaurant 3 | Gift Shop
        - `specialCode` 1 | 2 | 3 | 4 | 5 | 6 — This field is used to provide additional detail for lodging transactions. If a lodging charge does not match one of the listed descriptions, the default value of ‘1’ should be sent in the request. When a value of ‘4’ is sent, the `additionalCharges` field needs to be sent as well. Value|Description -----|----------- 1 | No Special Code 2 | Assured Reservation/No Show 3 | Advance Deposit 4 | Delayed Charge 5 | Express Check-Out Service 6 | Assured Reservation/Normal
        - `additionalCharges` HotelAdditionalCharges — Reason codes for additional charges in a lodging sale request at the time a consumer checks out.
          - `giftShop` 'Y' | 'N'
          - `laundry` 'Y' | 'N'
          - `miniBar` 'Y' | 'N'
          - `other` 'Y' | 'N'
          - `restaurant` 'Y' | 'N'
          - `telephone` 'Y' | 'N'
        - `roomRates` HotelRoomRates[] — Room rates broken down by rate and number of nights.
          - `nights` integer — The number of nights being charged at this rate.
          - `rate` number — The per night room rate.
      - `pin` TransactionPin — **Conditional: Include in the request for PIN debit and EMV Online PIN transactions. This object does not apply to UTG-controlled devices.**
        - `block` string — Encrypted PIN data received from a POS-controlled PIN pad (not controlled by the UTG).
        - `ksn` string — Key serial number (KSN) received from a POS-controlled PIN pad (not controlled by the UTG). This field is a hexadecimal field that should be padded with leading ‘F’s.
      - `purchaseCard` PurchaseCard, required
        - `customerReference` string, required — A unique value used to identify the consumer or transaction. If a merchant has a significant amount of revenue from purchasing card customers, the interface would use this field to collect the consumer’s purchase order or employee identification number. In lodging transactions, this may be unique transaction details, such as a reservation code or third-party booking source. This field is part of Level 2 card data.
        - `destinationPostalCode` string, required — When items are shipped, the ZIP/postal code to which merchandise will be shipped; otherwise, the ZIP/postal code where the goods or services are rendered. This field is part of Level 2 card data.
        - `productDescriptors` string[], required — A text description of the items purchased or services sold. This can be a generic text description of what the merchant sells (such as “Groceries”) or specific transaction data (such as the name of the item sold). At least one product descriptor field is required in a sale or authorization request. Note: The productDescriptors array is limited to 4 elements. Each element can contain a maximum of 40 characters.
      - `vendorReference` string — Optional field for information that can be searched in the merchant portal.
    - `device` object, required
      - `manufacturer` 'Ingenico' | 'Innowi' | 'PAX' | 'Verifone' | 'Castles' | 'Miura', required — Specifies the company which manufactured the device.
      - `model` string, required — **Conditional: Required when using a non-UTG-controlled device.** Specifies the model of the device.
      - `serialNumber` string, required — Specifies the serial number of the device.
      - `capability` DeviceCapability, required — **Conditional: Required when using a non-UTG-controlled device.**
- … truncated; see the full OpenAPI document linked below

## Response `200`

Transaction was processed

- object
  - `result` object[]
    - `dateTime` string, ISO 8601 — The date and time in ISO 8601 format including the timezone offset (yyyy-mm-ddThh:mm:ss.nnn+hh:mm). Must be sent as the local date/time of the merchant. For example, a request processed at a merchant in the Pacific time zone at 9:18am on April 15th 2021 would be sent as 2021-04-15T09:18:23.283-07:00
    - `amount` Amount — Object containing information regarding the amount being requested. The `total` field within the object is required and specifies the amount being requested. All other fields are for informational purposes and must also be included in the `total` field. For example, a purchase of $100 with a $20 tip and $8 tax would be `128.00` in the `total` field, `20.00` in the `tip` field and `8.00` in the `tax` field. Note: For merchants that are configured to allow multiple currencies, the amount fields can specify up to three decimal places. However, the number of decimal places can not exceed the number allowed for the specified currency. See the [Currency Codes](/guides/appendices/currency-codes) section for details.
      - `total` number, required — The amount being charged for a particular transaction. If other amount fields are sent, they must be included in the total amount. Amount cannot be zero.
      - `tax` number, required — The amount of sales tax charged for a transaction. The tax amount is used by businesses to track tax expenses for accounting purposes. Identifying the tax amount also helps consumers understand the total amount that they were billed. This field is part of Level 2 card data.
      - `taxIndicator` 'Y' | 'N' — Value|Description -----|----------- Y | Tax is included N | Tax is not included
      - `cashback` number — Specifies the cashback amount in a transaction. When using a UTG-controlled PIN pad with the ALLOWCASHBACK API Option, this field will return the cashback amount requested by the consumer. The interface can also send the desired cashback amount in a request by adding it to the `amount.total` and including it in the `amount.cashback` field. This will bypass prompting the consumer for a cashback amount.
      - `iiasAmounts` IIASAmounts[] — **Conditional: Send in the request if processing for a health care merchant.** For Vision related charges you must send only `iiasAmounts.type = 4V` and the corresponding `iiasAmounts.amount` value. For all other charges, the first entry in the array should have an amount representing the total of all healthcare costs, and `iiasAmounts.type = 4S`. Any subsequent entries should contain the subtotal for each of the other expense types involved in this transaction.
        - `amount` number — The subtotal for this type of healthcare expenses.
        - `type` '4O' | '4S' | '4T' | '4U' | '4V' | '4W' | '4X' — This code classifies eligible healthcare expenses. Value|Description -----|----------- 4O | Cash Disbursement (Discover Only) – Amount of Cash Back Being Requested 4S | Healthcare (Visa/MC Only) – Qualified Medical Expenses or Over-the-Counter 4T | Transit (Visa Only) – Transit Fare Media (e.g., Commuter and Parking Passes, Mass Transit Vouchers, and Tickets) 4U | RX (Visa/MC Only) 4V | Vision (Visa Only) 4W | Clinical (Visa Only) 4X | Dental (Visa Only)
      - `surcharge` number — **Conditional: Send in the request if a surcharge was applied to the transaction.** In a sale or authorization transaction, the `surcharge` field specifies a fee amount that a consumer is charged in addition to the transaction amount. The fee amount is also added into `amount.total`. For example, if the transaction request had `amount.total = 100` and the `surcharge.percentage` was 1.5% the transaction would include `amount.total = 101.50` and `amount.surcharge = 1.50`
      - `tip` number — **Conditional: Send in the request if a tip is included.** The tip amount of the transaction.
      - `checkTotal` number — Optional field specifying the total amount of the entire bill/invoice that this transaction is part of. It can be larger than `amount.total` in scenarios where the check is being split or if a portion of the check was already paid in cash or another form of payment.
    - `card` CardResponse
      - `entryMode` '1' | '2' | 'C' | 'E' | 'M' | 'Q' | 'R' — **Conditional: The Card Entry Mode should be sent in an initial request; in subsequent requests, it should be left blank or not sent. When using a Universal Transaction Gateway® (UTG®)-controlled PIN pad, this field should be left blank or not sent in a request; the UTG will capture the card entry mode and return it in the response. When P2PE data is being sent from a non-UTG controlled device, this field is not needed** The method used to capture a payment card in an authorization/sale request. Value|Description -----|----------- 1 | Track 1 Only or Dual Track (Track 1 & 2) 2 | Track 2 Only C | EMV Contactless via card or mobile wallet E | EMV Chip M | Manual Entry Q | QR Code R | Contactless MSD
      - `expirationDate` integer — **Conditional: Requires API Option "RETURNEXPDATE".** Card expiration date in MMYY format. This value will only be populated if "RETURNEXPDATE" is included in the `apiOptions` array.
      - `levelResult` string — Classifies the type of card used in an authorization/sale request. This field is returned in a response if the data is provided by the processor. See [Card Level Results]/guides/appendices/card-level-results) for a complete list of values.
      - `number` string — The card number field will always be masked when returned in a response.
      - `present` 'Y' | 'N' — **Conditional: Send in the initial authorization/sale request** Indicates whether a card was present (‘Y’) or not (‘N’) at the time a transaction took place. This should be set appropriately in the initial authorization/sale request. In subsequent requests, this field should be left blank or should not be sent. **Note:** Subsequent request here does not apply to the secondary request for card on file type transactions or reuse of the same card. An example of a subsequent request would be a capture after an authorization. You would not include `card.present` in the capture, which is the subsequent request. Another example is when performing an incremental authorization where you perform an authorization, followed by an incremental authorization then a capture. The second authorization (incremental) and the capture are the subsequent requests where you would not include `card.present`.
      - `type` 'AX' | 'AP' | 'BC' | 'CI' | 'DB' | 'GC' | 'JC' | 'MC' | 'NS' | 'PL' | 'SC' | 'VS' | 'WP' | 'YC' — An abbreviation used to specify the type of card that was used when processing a transaction. Value| Description -----|------------ AX | American Express AP | Alipay BC | Backed Card CI | Citgo DB | Debit card GC | Gift Card JC | JCB MC | Mastercard NS | Discover/JCB/Novus PL | Private Label SC | Sears Canada VS | Visa WP | WeChat Pay YC | IT’S YOUR CARD
      - `balance` CardBalance
        - `amount` number — The balance remaining on the card. Depending on which processor is being used, the balance may be returned for a gift card, debit card, EBT card, or other stored value card.
      - `securityCode` CardSecurityCodeResponse — **Conditional: Returned if card.securityCode was sent in the request.**
        - `result` 'M' | 'N' | 'P' | 'S' | 'U' | 'Y' | '1' | '2' | '3' — **Conditional: Returned if `card.securityCode.indicator` and `card.securityCode.value` are sent in the request.** The result of a CSC check. This field will be used by Shift4 to determine the value sent in the `card.securityCode.valid` field (based on the merchant’s list of accepted verification results as configured with Shift4). Value|Description -----|------------ M | CSC matched. N | CSC did not match. P | CSC not processed. S | CSC should have been present. U | Issuer unable to process. Y | CVC1 incorrect. 1 | CSC Unavailable - processor / card type does not support this parameter. 2 | An unrecognised result code was returned by the processor. 3 | No result code was returned by the processor.
        - `valid` string — **Conditional: Returned if `card.securityCode.indicator` and `card.securityCode.value` are sent in the request.** A simplified CSC check result based on the value in the `card.securityCode.result` field and the merchant’s accepted verification results as configured with Shift4. The value returned will be ‘Y’ if CSC verification passed or ‘N’ if CSC verification did not pass.
      - `token` CardTokenResponse
        - `value` string — This field is used to specify a card token. Whenever CHD is sent in a request, a card token will be returned in this field. Your interface should be designed to store this card token for future use. The latest card token received should be used in any subsequent request that references the same card data.
      - `debitType` 'girocard' | 'eftpos' | 'Interac' | 'Visa Interlink' | 'Visa US Common Debit' | 'Maestro Int'l' | 'Maestro US Common Debit' | 'Amex US Common Debit' | 'Discover US Common Debit' | 'DNA Debit' | 'UnionPay' — Specifies the type of debit card that was used when processing a transaction. Only returned if `card.type` = `DB`
    - `customer` object
      - `firstName` string — Specifies a consumer’s first name. This field is returned whenever the customer name is supplied in the request or if the track/EMV data contains the cardholder name.
      - `lastName` string — Specifies a consumer’s last name. This field is returned whenever the customer name is supplied in the request or if the track/EMV data contains the cardholder name.
    - `clerk` ClerkResponse
      - `numericId` integer — A number used to identify the point-of-sale (POS) or property management system (PMS) clerk or user. The value cannot be 0. An interface must be able to dynamically populate this field (not use a hardcoded value), unless the interface will be used exclusively for e-commerce.
    - `emv` EMV — **Conditional: Required when processing an EMV transaction without using a UTG.**
      - `emptyCandidateList` 'Y' | 'N' — When EMV is attempted but fallback occurs due to an empty candidate list, this field should be sent as 'Y' and `emv.fallback` should also be sent as 'Y'. If this field is not sent, a value of 'N' is assumed.
      - `tlvData` string, required — This field will contain all EMV tags in standard TLV format including the P2PE encrypted tags (5A and 57). The P2PE encrypted tags (5A and 57) will have the entire TLV string encrypted and the encrypted data will be in a TLV format using the same tag. For example, tag 5A would look like the following: - Encrypted: 5A103737DA95D8062F647A0FF747CC496570 - Decrypted: 5A084761739001010010
    - `merchant` MerchantResponse
      - `mid` number — The merchant ID associated with the merchant account.
      - `name` string — The merchant’s business name as configured with Shift4.
    - `receipt` Receipt[] — Array of receipt key/value pairs that should be printed on the receipt.
      - `key` string — The identifier the interface vendor can use to programmatically determine where to print a specific value.
      - `printName` string — The label that relates to the `printValue` field. When present in the response, this must be printed to the left of the `printValue`.
      - `printValue` string — The value that relates to the `printName` field. This must be printed to the right of the `printName`.
    - `server` Server
      - `name` string — The name of the server that processed the request.
    - `signature` Signature
      - `data` string — The base64-encoded data sent when a signature is captured as a Portable Network Graphics (PNG) file.
      - `format` 'P' — The data format the signature data will be in. "P" for PNG format.
    - `transaction` object
      - `authorizationCode` string — The authorization code provided by the consumer’s issuing bank. It is provided in a response if an online authorization or sale request is approved. Following a referral response, it is also specified in [Manual Sale](/apis/payments-platform-rest/openapi/transactions/manualsale) requests.
      - `authSource` 'E' | 'O' | 'A' | 'F' — In a response, a code returned by the processor to indicate which host issued the response. Value | Description -------|---------------------------- E | Engine (Online) O | Offline A | APM (Online) F | Payment Platform (Online)
      - `invoice` string — 10-digit invoice number assigned by the interface to identify a transaction. An invoice number serves as a unique key that identifies a transaction within a batch in Shift4's Gateway. **Note: For US and Canadian processing: Although the invoice number is sent as a JSON string it is a numeric value. No alpha characters are allowed.** **For processing outside of the US and Canada alpha characters are allowed.**
      - `responseCode` 'A' | 'C' | 'D' | 'e' | 'f' | 'P' | 'R' | 'X' | 'S' | 'I' — Code indicating the Shift4 host response. Value | Description | Details -------|---------------------------------------------------------------------------------------|-------- A | Approved | The transaction is approved. C | Approved | The transaction is approved without requiring additional authorization because it is less than or equal to a ceiling amount. (The ceiling amount is the original authorization amount multiplied by the tolerance per the merchant’s settings with Shift4.) D | Declined | The transaction is declined. <b>Note: Shift4 automatically declines AVS/CSC failures if the [POSHANDLEAVSFAIL Api Option](/guides/appendices/api-options#poshandleavsfail) was not sent in the request.</b> e | [Error](/guides/appendices/error-codes) | There is an error condition. f | [AVS or CSC failure](/guides/response-handling/understanding-avs-and-csc-verification)| An AVS or CSC failure has occurred (credit card only). <b>Note: This value will only be returned if the [POSHANDLEAVSFAIL Api Option](/guides/appendices/api-options#poshandleavsfail) was sent in the request.</b> P | [Partial approval](/guides/advanced-concepts/partial-approval) | A partial approval has occurred. Check `amount.total` for the approved amount. R | Voice referral | The transaction requires a voice referral. [blank]| Status is unknown | The approval status is unknown. X | Expired card | There is an error condition due to the card being expired. S | SCA Online PIN required | The contactless EMV transaction requires strong customer authentication to continue. The terminal must gather the online PIN if supported by the device form factor and CVM list then resubmit the transaction request. I | SCA Interface switch required | The contactless EMV transaction requires strong customer authentication to continue. The terminal must look at the form factor indicator to determine if the transaction should be declined, switched to EMV contact or tapped again using CDCVM. J | Soft decline after exemption request | Transaction was soft declined. Returned when requesting an exemption by sending `transaction.exemptionAction = 02` and the card issuer rejects the exemption.
      - `saleFlag` 'A' | 'C' | 'S' — Specifies a transaction is a sale (‘S’) or credit (‘C’). In an [Invoice Information](/apis/payments-platform-rest/openapi/transactions/getinvoice) request, an 'A' may be returned to differentiate an authorization from a sale.
      - `amex` TransactionAmex
        - `propertyCode` string — The code that contains a Merchant-assigned store or location number (or name) that uniquely identifies where the transaction took place.
      - `avs` AVS
        - `postalCodeVerified` 'Y' | 'N' — Identifies whether the ZIP/postal code was verified (‘Y’) or not (‘N’) in an AVS check with a processor.
        - `result` 'A' | 'E' | 'G' | 'N' | 'R' | 'S' | 'U' | 'W' | 'X' | 'Y' | 'Z' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' — Identifies the response code returned from an Address Verification System (AVS) check with a processor. Value|Description -----|----------- A | Street address matched, but ZIP/postal code did not match. E | Error (AVS data is invalid or not allowed). G | Card issuer does not participate in AVS. N | No street address and no ZIP/postal code match. R | Card issuer system is unavailable. S | AVS service not supported. U | Street address information unavailable. W | Street address did not match, but ZIP/postal code matched. X | Street address and 9-digit ZIP/postal code matched. Y | Street address and 5-digit ZIP code matched. Z | Only the ZIP/postal code matched. 1 | Cardholder name and ZIP match 2 | Cardholder name, address, and ZIP match 3 | Cardholder name, address match 4 | Cardholder name matches 5 | Cardholder name incorrect, ZIP matches 6 | Cardholder name incorrect; address and ZIP match 7 | Cardholder name incorrect; address matches 8 | Cardholder name, address, and ZIP do not match
        - `streetVerified` 'Y' | 'N' — Identifies whether the street number was verified (‘Y’) or not (‘N’) in an AVS check with a processor.
        - `valid` 'Y' | 'N' — Simplified AVS result based on the merchant’s list of accepted responses as configured with Shift4: (‘Y’) if accepted or (‘N’) if not accepted.
    - `universalToken` UniversalToken
      - `value` string — An identifier for a card or payment account across all Shift4 merchants.

## Other responses

- `400` — Error
- `504` — Timeout

---

[API](https://skmtc.net/shift4/apis/shift4-payment-api.md) · [All operations](https://skmtc.net/shift4/apis/shift4-payment-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/shift4/shift4-payment-api/versions/b923fc55b203/schema)