What does service_not_allowed mean?

The service_not_allowed decline code is returned when the issuing bank does not permit this type of transaction on the card. The card is valid, but the specific service — recurring billing, cross-border charge, merchant category, or transaction type — has been disallowed at the issuer level.

Is it a soft or hard decline?

service_not_allowed is a soft decline. The cardholder's account is in good standing; only the specific service type is blocked. Recovery is possible through routing changes, retries with adjusted parameters, or collecting an alternate payment method.

Common root causes

• Prepaid or gift cards that don't support recurring billing

• Business or corporate cards with category spending restrictions

• Debit cards that don't support card-not-present transactions outside certain regions

• Cross-border restrictions that block international merchants

• BIN-level rules the issuer applies uniformly to all cards in that range

Recommended recovery steps

1. Check the card type. Prepaid and restricted corporate cards often can't support subscriptions at all — a new card is required.

2. Retry with different routing. Acquirer or network routing can sometimes change whether the issuer views the transaction as "allowed."

3. Prompt for an alternate payment method. Bank transfers, wallets, or a personal card usually resolve the block.

4. Review acceptance settings. For MCC mismatches, confirm your merchant category code is classified correctly with your processor.

How FlyCode handles service_not_allowed

FlyCode's per-merchant ML models recognize service_not_allowed patterns tied to specific BINs and card types. For BINs that support retries with different parameters, FlyCode automatically adjusts routing and timing. For BINs that structurally cannot accept the transaction (like closed-loop prepaid cards), FlyCode immediately triggers AI-driven outreach to request a compatible payment method, skipping wasted retries.