It is common practice to import orders with an existing payment transaction. Most often this is a pre-authorization, but sometimes this could be a settled payment transaction. When importing orders with either type of payment transaction, there are fields in addition to the basic required fields that are required to import the order. Below lists these fields and briefly describes what we are expecting in each field. The OrderLogix Real-Time Order Submission API spec should be referred to for full field definitions.
USE_PRICES, USE_SHIPPING, and USE_TAXES are recommended to be sent as "Y" so that the values for price, shipping, and tax that were used when calculating the amount for the payment transaction are used when validating the order for import to OrderLogix.
PAYMENT_TYPE will need to be sent as either AUTH for a pre-auth payment transaction or SALE for a settled or captured payment transaction.
AMOUNT_ALREADY_PAID should represent the amount that the payment transaction was for. If there are multipay offers included on the order, this may not be the entire order value.
Note: This will need to equal the sum of all of the "paid" fields on the order (PAID_PRICE_PROD##, PAID_SHIPPING_PROD##, PAID_TAX_PROD##)
MERCHANT_TRANSACTION_ID is the transaction ID received from the merchant processor for the payment transaction. This must match exactly to what was provided, as this will be used for settling the pre-auth or refunding the settled payment transaction.
PAID_PRICE_PROD## for each item should represent the product price that was included in the payment transaction for this given product.
Notes: If the product is a multipay offer, this would represent just the amount for the first payment.
if the quantity ordered is greater than one, then this would be the unit price multiplied by the quantity ordered.
If a discount is applied to the item, this would be less the amount that was discounted.
PAID_SHIPPING_PROD## for each item should represent the shipping amount included in the payment transaction for the given product.
Notes: If the product is a multipay offer, and shipping is distributed across the installments, this would represent the shipping amount for the first payment.
PAID_TAX_PROD## for each item should represent the tax amount included in the payment transaction for the given product.
Notes: If the product is a multipay offer, and tax is distributed across the installments, this would represent the tax amount for the first payment.
If tax is being charged on shipping, this should represent the amount of tax charged on the unit price and the shipping for the first payment.
TAX_CALCULATION_METHOD setting should be provided if the method used to calculate tax is different than that default (ORDER). This would alternatively be ITEM or TOTAL. A difference in tax calculation method may result in a difference of 0.01 or more, up to a few cents, between what the source system has sent and what OrderLogix has calculated when validating the order upon import.
TAX_ROUNDING_METHOD setting should be provided if the method used to round tax is different than the default (ROUND). This would alternatively be UP, DOWN, or BANKERS. A difference in tax rounding method may result in a difference of 0.01 or more, up to a few cents, between what the source system has sent and what OrderLogix has calculated when validating the order upon import.