New Account Type Field for ATM Transactions
Release Date
July 1, 2025
Products Affected
ASA and Transaction APIs
Impact
New field added to ASA requests and Transaction events providing account type visibility for ATM transactions
Audience
All customers
Action Required
None, this change is additive only
Overview
The new account_type
field included in transaction data shows which account (checking, savings, etc.) cardholders select at ATMs. This enables accurate decline messages and account-specific authorization decisions, avoiding confusing generic errors when cardholders select accounts not linked to their card.
Details
The new account_type
field appears at the root level of ASA and transaction event objects for ATM transactions only (withdrawals, deposits, balance inquiries). The field is null
for point-of-sale transactions.
Values:
DEFAULT
- The cardholder's default account when they don't select a specific account or the ATM doesn't offer account selectionCHECKING
- Checking account when the cardholder selects "Checking" at the ATMSAVINGS
- Savings account when the cardholder selects "Savings" at the ATMCREDIT_CARD
- Credit card account when accessing available creditnull
- No account type specified for non-ATM transactions or when account type cannot be determined
Example: ASA Request with Account Type
{
"merchant": {
"acceptor_id": "333301802529120",
"descriptor": "ATM WITHDRAWAL",
"mcc": "6011"
// ... other merchant fields
},
"card": {
"token": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"last_four": "1234"
// ... other card fields
},
"account_type": "SAVINGS", // New field
"amount": 10000,
// ... additional required fields
}
Release Timeline
- Production: Tuesday, July 1st, 2025
User Impact
This change is additive only and doesn't require modifications to any existing integrations.
Updated Documentation
Visit our API Reference for integration details.
Contact us via HELP in your Lithic Dashboard with questions.
The Lithic changelog has an RSS feed! Subscribe for update announcements.