ISO 8583 response code: 61

Issuers cap how much can be authorised on a card in one transaction and across a day or other window, independently of the available balance. A 61 says the amount breached one of those ceilings. It is distinct from 51 — the money is there, the permission to spend that much at once is not — and distinct from 65, which caps the number of transactions rather than their value.

• A single transaction above the card's per-transaction ceiling.
• The cumulative daily total already close to the limit, so a modest transaction pushes it over.
• A card with a low default ecommerce or international ceiling that the cardholder has never raised.
• An inflated pre-authorisation — a hotel or fuel hold far above the eventual charge — breaching the limit unnecessarily.

1. Ask the cardholder to raise the limit with their issuer, or to use a different card. Many banks allow this instantly in-app.
2. Split the payment into smaller amounts if your business model and the scheme rules permit it.
3. Review your pre-authorisation amounts. Authorising far more than you will capture converts perfectly good transactions into limit declines.
4. Retry after the limit window resets — typically the next day — rather than immediately.

• ISO 8583 65Exceeds withdrawal frequency limit
• ISO 8583 51Not sufficient funds
• Stripe card_velocity_exceededcard_velocity_exceeded

• ISO 8583 message parser

How is 61 different from 51?

A 51 means the money is not there. A 61 means the money is there but the issuer will not let this much move in one transaction or one period. The distinction matters for retries: a 61 clears when the limit window resets, whereas a 51 clears only when the balance changes.