New SUSPECTED_FRAUD ASA Response

Overview

A new SUSPECTED_FRAUD decline reason is now available for ASA (Authorization Stream Access). This decline reason may be returned when a transaction violates program fraud rules designed to stop third-party fraud. Accurately using this new response enables more precise fraud reporting within Lithic as well as more granular decline responses passed to the card networks.

SUSPECTED_FRAUD should only be used when no other decline reason more accurately describes the decline. For example, transactions at a blacklisted merchant should still use the UNAUTHORIZED_MERCHANT decline reason, even if this behavior may be indicative of fraud.

Available Decline Reasons

The complete list of ASA decline reasons now includes:

• SUSPECTED_FRAUD - Transaction violates program fraud rules designed to stop third-party fraud
• AVS_INVALID - Address verification failed
• INSUFFICIENT_FUNDS - User has insufficient funds
• UNAUTHORIZED_MERCHANT - Restricted MCC, country, or transaction type
• VELOCITY_EXCEEDED - Transaction exceeds velocity limits
• CARD_PAUSED - (Select programs only) Card is in a paused state
• DRIVER_NUMBER_INVALID - Driver ID does not match expected value (fleet cards only)
• VEHICLE_NUMBER_INVALID - Vehicle ID does not match expected value (fleet cards only)

Example Response

ASA responses with the new decline reason follow the standard response format:

{
  "result": "SUSPECTED_FRAUD",
  "token": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}

Release Timeline

Available now; October 6th, 2025

User Impact

This change is additive only. Existing integrations will continue to function without modification.

Updated Documentation

For complete ASA response 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.