Structured Amounts Object Now Available in ASA

Overview

Authorization Stream Access requests now include a new top-level amounts object that provides a structured breakdown of various transaction amounts. This object groups cardholder, merchant, hold, and settlement amounts in a single place, making it easier to distinguish between the original authorization amount and the hold amount when hold adjustments are applied. The structure mirrors the amounts object already available on the Get Card Transaction endpoint.

Details

The amounts object contains four sub-fields:

amounts.cardholder represents the original authorization amount in the cardholder's billing currency, before any hold adjustment is applied.

• amount (integer): The original amount in minor units (e.g., cents).
• conversion_rate (string): The currency conversion rate applied.
• currency (string): The cardholder's billing currency code (e.g., "USD").

amounts.merchant represents the transaction amount in the merchant's local currency.

• amount (integer): The merchant-side amount in minor units.
• currency (string): The merchant's currency code (e.g., "CZK").

amounts.hold represents the total hold amount that should be placed on the cardholder's account, in the cardholder's billing currency. This amount may differ from cardholder.amount when a hold adjustment has been applied (e.g., gas station pre-authorization padding).

• amount (integer): The hold amount in minor units.
• currency (string): The cardholder's billing currency code.

amounts.settlement is reserved for consistency with the Transactions API. In the ASA request context, this field is always null, since settlement has not yet occurred at authorization time.

Hold Adjustment Behavior

When no hold adjustment is present, amounts.cardholder.amount and amounts.hold.amount are identical, and both match the (now deprecated) top-level authorization_amount field.

When a hold adjustment is present (e.g., a gas station authorization padded from $10 to $100), amounts.cardholder.amount reflects the original merchant-requested amount, while amounts.hold.amount reflects the adjusted hold placed on the cardholder's account.

Example: ASA Request with Amounts Object

{
  "token": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "status": "AUTHORIZATION",
  "amount": 1000,
  "merchant": {
    "acceptor_id": "333301802529120",
    "descriptor": "COFFEE SHOP",
    "mcc": "5812"
  },
  "amounts": {
    "cardholder": {
      "amount": 1000,
      "conversion_rate": "1.000000",
      "currency": "USD"
    },
    "merchant": {
      "amount": 1000,
      "currency": "USD"
    },
    "hold": {
      "amount": 1000,
      "currency": "USD"
    },
    "settlement": null
  }
}

Deprecated Fields

The following top-level fields are now marked as deprecated. These fields will continue to be populated in ASA requests and there is no current scheduled plan for removal, but new integrations should use the corresponding fields within the amounts object instead:

• amount
• authorization_amount
• merchant_amount
• merchant_currency
• cardholder_currency
• conversion_rate

Release Timeline

• Production availability: February 12, 2026

User Impact

This change is additive only. Existing integrations will continue to function without modification, as all deprecated top-level fields remain populated. The new amounts object provides clearer separation between the original cardholder authorization amount and the hold amount, which was not previously surfaced as distinct values in the ASA request.

Updated Documentation

For complete ASA request specifications, visit our API Reference.

If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.

The Lithic changelog has an RSS feed! To monitor for new update announcements, subscribe with your preferred RSS reader.