Product Code Mapping for Online Credit Card Payments

When Avcard and AIR Card payments are processed online through FBO One and the MSTS payment gateway, in the background a special code for each service/product on the order is passed along the gateway to the card processor. These codes match up with AIR Card's standardized allowed products list, confirming to AIR Card that the service/product sold is one that is allowed to be paid by AIR Card. These standardized codes also appear on the monthly statements sent by Avcard or AIR Card to cardholders.

Product Mapping

In order to process credit card payments online, or send e-invoices to NetJets, each service/product that will be sold needs to be "mapped" to the appropriate product code. This mapping is only used by the card processing gateway, it does not change the name of products in your FBO One system.

Go to Administration / Products / Product Mappings. 

  • Product column is the FBO One service/product.
  • Type column is used to show when multiple components make up one service/product. 
    In the example below, only the parent Handling Fee needs to be mapped, since the children components use the same code.
  • Mapped Value column is the special code.
  • Remark column, is a free format field to enter some extra remarks for the mapping
  • Warning column can show a mapping warning e.g. 'This product has no mapping' .

A product in FBO One can be mapped by clicking on the Product. A product can also be mapped when the product is first created in FBO One (recommended).

On the edit screen for the product, locate the section Payment gateway product mapping definition. Select the appropriate code in the AHT Product Group field.


It is best to map products to the most specific available product code. For example, for a Fork Lift product, it is better to map to the ForkLift product code than the more general GroundEquipment code. 

If you accept AIR Card, AIR Card / KHI will not accept any products mapped as handling fees, so avoid using product codes: AirCraftGroundHandling, IntlHandlingFee.

Fuel Products

Fuel products must be mapped to a specific fuel type code, for example: Jet A Fuel, Jet A1 Fuel, Avgas 100LL. One general "Fuel" product cannot be used for multiple fuel types.

Fuel products must be sold in recognized fuel units, such as usg (US Gallon) or ltr (Litre). For example, a sale of 100 usg of Jet A at a rate of $5.00 is acceptable. A sale of 1 item of Jet A at $500 is not acceptable.

If fuel taxes will be broken out on the order, the taxes should be a child of the fuel product. If help is needed with setting up fuel taxes, please contact for assistance.


If fuel is sold with Prist/Additive always included (additive mixed in the tank/truck with the fuel), map to the "wAdd" product code. 

If Prist is added separately, create a separate product for Prist and map to "Fuel Additive".


If a child product is a discount of the parent product, the special product code "Discount" can be used. A stand alone product may not be mapped to product code "Discount".

Third Party Disbursements

If third party services are added to orders with a child product for disbursement or administration fees, the appropriate product code for the disbursement product is "VendorAdminFee"

Product mapping not required

Any product that will be sold and paid by credit card must be mapped to a product code. 

A service or product that is provided at no cost does not require mapping to a product code. For example, Send Quote to Client does not require mapping. In this case, the red warning can be ignored.

Tips & Tricks

Do not use "Miscellaneous" as a code because the will cause rejects with some Payment Cards. Instead, use "VendorAdminFee" for any charge for which there is no reasonable match.

Product Mapping Groups

To see a list of all the standard product codes, go to Administration / Products / Product Mapping Groups.

There is no need to edit this list, since it already contains all the special product codes needed. It can be used as a reference. 

Product category mandatory

The property 'Product category mandatory' indicate that the category is mandatory. When this property is true an product of the mapped group should have a category.
This field should always be true in case of the AHT product mapping group.

Special mapping products

When a mapping g groups is created there will be always two default mapping products:


The main reason for this special group is to add remarks to a product mapping but no actual mapping is there.
Normal when no mapping is set in the mapping page the remark will show  'From parent.....' so not possible to add remarks:

If you want to be able to add some remarks but the product must still take the mapping from the parent select DoNotMap:

N/A Does not apply

When this mapping is selected the product should never be mapped (e.g. has never an amount like a Sign order line).

There is some logic in the payment process when a FBO1 product is mapped to this and there is an amount for this service the online payment should fail. 

Order sample with a Sign service of 25 dollar:

Mapping definition:

When try to do an AHT online payment you will get the next message:

Inactive products of an mapping group

Every mapping product has a bit field Active, when the product is not active a warning is shown on the admin mapping page:

Sample BaggageFee is not active:

When still used on the mapping page a warning will be shown: