| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
These resources support advanced transaction features and integration troubleshooting:
Metatdata
To request transaction metadata, append the include query parameter to your request:
/v1/charges?include=transaction_metadata
LEVEL 2 or LEVEL 3 Card Data
When creating a new charge, you have the option to provide additional card data at LEVEL2 or LEVEL3. These enhanced data levels can provide benefits such as lower Visa and Mastercard interchange rates, particularly for commercial, corporate, purchasing, business, or government cards.
The following fields are required to process a transaction with card_level set to LEVEL2:
- address\_line1
- purchase\_order
- sales\_tax
- zip
To process transactions with card_level set to LEVEL3, you must include the fields required for LEVEL 2, along with the following additional fields:
- customer\_vat\_number
- destination\_country\_code
- duty\_charges
- order\_date
- ship\_from\_zip
- ship\_to\_zip
- shipping\_charges
- summary\_commodity\_code
- tax\_amount
- tax\_category
- tax\_rate
- tax\_type
- vat\_invoice
- product\_details
Instructional Funding (Splits)
Merchants configured with instructional funding are required to include the splits array in the request payload.
At least one valid split instruction must be provided — otherwise, the request may result in errors and could delay funding of the transaction.
API Troubleshooting
When creating a new charge, you may encounter the following error codes. Each status is associated with a specific error message. You can find a detailed error message breakdown in our Charges FAQ.