Understanding Card Declines and Authorization Events

Overview

When a Slash card transaction is declined, Slash shows the authorization event in your card activity with the clearest available decline reason. Decline details can help you understand whether the issue came from card controls, available balance, merchant restrictions, issuer rules, or another processing check.

Some authorization events are informational and do not represent real spending. For example, merchants may run zero-dollar verification checks to confirm that a card is valid. Slash filters these probes out when possible so your card activity is easier to read.

Common reasons a card authorization may be declined

• Insufficient available balance or credit: The account or card does not have enough available spending capacity for the attempted transaction.
• Card limits or controls: The transaction exceeds a card limit, merchant lock, card group policy, or other spend control.
• Card status: Paused, inactive, closed, or otherwise unavailable cards cannot authorize new purchases.
• Merchant or network restrictions: Some merchants, merchant categories, countries, or transaction types may not be supported for a given card program.
• Issuer or risk checks: The card issuer or network may decline an authorization based on its own rules, fraud checks, or transaction requirements.

How to review a declined transaction

Open the card or transaction activity in your Slash dashboard and select the declined authorization. Review the decline reason, card status, card limits, available balance, and merchant details. If the decline reason points to a card control or limit, an admin can update the card settings and the merchant can retry the transaction.

If the decline reason is unclear or you believe the transaction should have been approved, contact Slash Support with the card name, merchant, amount, date, and any decline reason shown in your dashboard.

Zero-dollar verification events

Some merchants send a $0 authorization to verify that a card exists before charging it. These checks usually do not require action and do not move money. Slash may filter these events from customer-facing activity so you see fewer confusing card events.

Pending spend after a decline

If a card authorization is declined after a pending spend intent was created, Slash reverses the related pending activity where supported. This helps keep your available balance and transaction activity accurate after a failed card attempt.

Need more help?

If you still need help understanding a card decline, use the in-app chat in your Slash dashboard or email support@slash.com. Include the card, merchant, attempted amount, date, and decline reason so the team can investigate faster.