Sale API Request Object
The description of the Sale API request object
You form a Sale API request in standard JSON format. The following tables list the properties of a Sale API request:
Top-Level Properties
Property | Description | Data Type | Length | Required | Allowed Values |
---|---|---|---|---|---|
| How you entered the payment method. | Enum | YES |
| |
| The type of card that you processed. Currently, only | Enum | 7 | YES |
|
| The AIR Card® number. | Varchar | 50 | YES | |
| The AIR Card® Card Verification Value, which you can use for manual card processing. | Varchar | 3 | NO | |
| The card expiration date in the format of | Char | 7 | YES | |
| The name of the software vendor transmitting the transaction. | Varchar | 100 | NO | |
| The | Object | YES |
invoice
Subobject
invoice
SubobjectProperty | Description | Data Type | Length | Required | Allowed Values |
---|---|---|---|---|---|
| The invoice number, which must be unique within the context of the FBO. | Varchar | 50 | YES | |
| The number of the original invoice that you are rebilling in this transaction. | Varchar | 50 | NO | |
| The transaction currency. | Varchar | 4 | YES | A valid currency code. |
| The flight type associated with the transaction. | Enum | 50 | NO |
|
| The invoice date in the format of | Char | 10 | YES | |
| The invoice total amount. The sum of all line items on the invoice, not including taxes and fees, should match this number, and you must round it to two decimal places. | Decimal | 10,2 | YES | |
| Any transaction notes. | Varchar | 1000 | NO | |
| The name of the captain. | Varchar | 150 | NO | |
| The ICAO code of the flight’s origin airport. | Varchar | 4 | NO | |
| The ICAO code of the flight’s destination airport. | Varchar | 4 | NO | |
| Whether or not the flight is domestic or international. Domestic is considered a flight that has an origin and a next destination within the same country. | Boolean | NO | ||
| The aircraft’s tail number. | Varchar | 50 | YES | |
| The | Array | YES |
details
Subobject (Array)
details
Subobject (Array)
Important Notes
You must send taxes and fees associated with a specific product or service in a
taxAndFeesBreakdown
subobject array.If you charge a "vendor fee" for non-fuel items, however, you must include this fee in a
details
subobject and not in ataxAndFeesBreakdown
subobject. Also, the gateway validates that the percentage of this fee in relation to the total value of non-fuel items matches the percentage that you specified in your configuration.If you've applied a government discount to a transaction, you must reflect this discount in the difference between the
postedPrice
and theunitPrice
properties.A
details
subobject can only include one item of typeFuel
but can have several non-fuel items.The
lineTotal
andunitPrice
properties can be zero, but theqty
property must be greater than zero.If
itemCode
has a product type ofFuel Related
, there must be another item in thedetails
subobject that has a product type ofFuel
.
Property | Description | Data Type | Length | Required | Allowed Values |
---|---|---|---|---|---|
| A line identifier that a merchant’s POS system generates, which must be unique within the context of a single transaction. | Integer | 1000 | YES | |
| A valid product code. | Varchar | 100 | YES | |
| The name of the product or service provided by the vendor in the POS system. | Varchar | 100 | YES | |
| The flight number. | Varchar | 50 | NO | |
| The unit of measure for the item sold. | Enum | 50 | YES |
|
| The processing type, either If you input an If you are not under contract at an airport for that fuel or related contract product, you cannot send transactions to the gateway if another merchant is under contract at the same airport (though system overrides may apply). If you are a third-party merchant with an | Enum | YES |
| |
| The delivery ticket number for fuel products, which must be unique within the context of the FBO. | Varchar | 50 | Required if the item is a fuel type. | |
| The date and time the service was delivered, in the format | Char | 19 | Required if the item is a fuel type. | |
| The product or service quantity, which can include up to two decimal places. | Decimal | 8,2 | YES | |
| The unit price of the line item, which can include up to six decimal places. | Decimal | 10,6 | YES | |
| The line total amount, up to two decimal places. If the product has taxes, you should specify them separately in the | Decimal | 10,2 | YES | |
| The posted price of the line item. | Decimal | 19,8 | NO | |
| Any additional descriptive note for the line item. | Varchar | 1000 | NO | |
| The | Array | NO |
taxAndFeesBreakdown
Subobject (Array)
taxAndFeesBreakdown
Subobject (Array)
Important Notes
You cannot include the taxes and fees that have been specified in a
taxAndFeesBreakdown
subobject in theinvoiceTotal
property.You can only include taxes and fees that the gateway has approved in a
taxAndFeesBreakdown
subobject.The
lineTotal
andunitPrice
properties can be zero, but theqty
property must be greater than zero.
Property | Description | Data Type | Length | Required | Allowed Values |
---|---|---|---|---|---|
| A valid product code. | Varchar | 100 | YES | |
| The name of the product or service provided by the vendor in the POS system. | Varchar | 100 | YES | |
| Whether the tax or fee is percentage based or fixed per unit. | Enum | YES |
| |
| The tax or fee percent. Required only if | Decimal | 5,2 | NO | |
| Whether the tax or fee is a sales or cost tax. | Enum | YES |
| |
| Should specify the quantity for which the tax or fee applies, which will usually be the same as the quantity of the product the tax applies to. | Decimal | 10,6 | YES | |
| The actual tax or fee value, which you should always send in decimal format. So if | Decimal | 10,6 | YES | |
| The tax or fee line total rounded to 2 decimal places. Should equal | Decimal | 10,2 | YES | |
| Any additional descriptive note for the line item. | Varchar | 1000 | NO |
You can find examples of this request object here.
Updated 5 months ago