Terminal Charge

Last Updated: June 11, 2024

What's in this article?

By default, the authorization will be captured and included in the current batch.

AUTHORIZATIONS:
BasicAuthentication
REQUEST BODY SCHEMA: application/json

amount
required

Transaction amount in USD.

If a mandatory surcharge is set by the ISO/MSP, the actual amount charged could be different than the amount submitted in this field. The revised amounts will be returned in the response.

The /surcharge endpoints can be used to check the surcharge before processing. The surcharge will also be returned by the Hosted Tokenization library.

terminal_id
required
string

The serial number of the terminal. This must match a terminal that is boarded in the gateway.

amount_details
object (AmountDetails)

Breakdown of the amount. These fields do not affect the actual transaction amount and are for reporting and Level 3 only.

name

Name on payment method (credit card or check).

transaction_details
object

Additional optional transaction details.

line_items
Array of objects (Item) non-empty

Line item details for Level 3 data.

The data will not be checked for accuracy, e.g. if the totals add up correctly.

billing_info
object (Address)

shipping_info
object (Address)

custom_fields
object (CustomFields)

ignore_duplicates


Determines whether to override any duplicate transactions detection.

customer
object
Help us improve. Was this article helpful?