Level 2 Card Processing

Additional data can be passed across to the api in order to qualify for better interchange rates when processing credit cards.

Card processing can be put into one of 3 different buckets: Level 1, Level 2, or Level 3. As you progress up the levels more contextual information about the order is required in order to qualify.

🚧

Only corporate, government, and some business cards are eligible for Level 2 and 3.

Level 2 Data

For Level 2 processing, the following data should be supplied.

  • Order Number
  • Sales Tax Amount
  • Shipping Postal Code is recommended if the order is being shipped

Order Info

All Sale endpoints have an order_info object that can be used to pass across Level 2 card processing data. This object can also simply be used as convenience for storing order data regardless of the payment method. There is no validation on the object beyond the lengths of the fields.

Fields

order_info FieldTypeDescription
amount_discountdecimalTotal amount of discount on the payment that is included in the amount field of the sale.
amount_taxdecimalTotal amount of tax on the payment that is included in the amount field of the sale. Required for Level 2 processing, if order_number is set this will default to 0.00.
order_numberstringMax length 50. The order number, invoice number, or purchase order number, etc. Required for Level 2 processing.
shipping.amountdecimalTotal amount for shipping that is included in the amount field of the sale.
shipping.destination_postal_codestringMax length 10. Postal code where the order is being shipped. Recommended for Level 2 processing when order is being shipped.

Sale Request

{
  "...",
  "order_info": {
    "amount_discount": .50,
    "amount_tax": 2.56,
    "order_number": "ord_3847476",
    "shipping": {
      "amount": 3.70,
      "destination_postal_code: "80202"
    }
  }
}