Tip from SmartRetry Instead of a blind retry, configure your payment engine to re-route the card over alternative rails such as PINless debit if supported by the BIN. If your gateway cannot alter the processing path, suppress automated retries immediately and prompt the customer for an alternate card.
Visa
Visa Issuer Response Code 39: No Credit Account
hard declinetechnical decline
Last updated: September 25, 2026
About 39 - "No credit account"
Key details
- 39
- Issuer Response Codes
- 39
- No credit account
hard declinetechnical decline
What it means
Visa decline code 39 indicates that the card number presented for the transaction is not associated with a usable credit account. This typically occurs when a payment is routed through a credit transaction path for a card product that does not support credit processing.
Classification & retryability
hardtechnicalRetryable: conditional
Although Visa classifies code 39 under Category 2 allowing up to 15 retries within 30 days, immediate retries without modifying the transaction routing or card will likely fail. Reserve retries for after updating the payment method or correcting the transaction path.
Why does code 39 occur?
- The payment was submitted through a credit processing path for a card that does not support credit transactions.
- The cardholder attempted to use a non-credit product in a payment flow or terminal configured exclusively for credit processing.
- The payment gateway or merchant account is improperly routing the transaction type for the presented card BIN.
How to solve 39?
Verify that the transaction type and payment-method routing configured in your gateway match the actual card product presented. Do not repeatedly resubmit the identical transaction, as code 39 reflects a fundamental product incompatibility rather than a transient timeout. If the technical routing is correct but the account cannot support the requested credit transaction, prompt the customer to provide a different eligible credit account or an alternative payment method.
Solving as a merchant
Confirm your response-code mapping with your acquirer to ensure code 39 is being accurately reported. Check your gateway's routing logic for the specific card BIN. For recurring billing operations, trigger a payment-method recovery sequence or send a customer outreach email rather than initiating an aggressive short-interval retry schedule.
Solving as a customer
Provide an alternative payment method, such as a valid credit card, or contact the issuing bank to confirm whether the current card can support the requested transaction type.
Frequently asked questions about this topic
Share this article
Author
Kyle Regacho
Find me on LinkedinFocused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >Related codes
Articles you may find interesting:
View all
Turning Payment Declines into Revenue with Context-Aware Retry Logic
Blind retries waste fees and damage issuer trust. By analyzing decline codes and timing reattempts around payroll cycles, payment teams can successfully salvage recurring revenue without customer disruption.
Why Payments Fail: Decoding Decline Codes and Modernizing Retry Logic
Surface-level decline messages conceal critical issuer signals. Discover how intelligent retries, network tokens, and behavioral timing protect MID health and systematically recover lost recurring revenue.
Decoding Payment Declines: Turning Authorization Failures into Recovered Revenue
Blindly retrying failed transactions hurts authorization rates and risks network fines. Discover how decoding issuer responses turns card declines into recovered revenue.
The Real Cost of Payment Declines and How to Recover Lost Revenue
Payment failures cost merchants billions in uncaptured revenue and customer churn. Discover how data-driven retries and response code intelligence help teams recover failed transactions and protect conversion.