Service Unavailable

Why it happens

Payment processing runs through a chain of systems: the merchant's payment gateway, Stripe's infrastructure, card networks like Visa or Mastercard, and the issuing bank. `service_unavailable` points to a gap somewhere in that chain being temporarily down or overloaded rather than actively rejecting the request. For recurring billing, this often clusters around known high-volume periods, batch renewal runs where many subscriptions bill on the same day or the same hour, which can occasionally strain a link in that chain. It can also occur during scheduled maintenance on any system in the path. None of this reflects anything about the specific customer or card being charged.

How to fix it

Yes. This is a systems-level, transient condition, and by the time a retry is attempted the unavailable service has typically come back up. There's nothing about the card to fix here, just a window of time to wait out. Space retries out similarly to other network declines: a first attempt within a few hours of the failure, and a second attempt around the one day mark if the first one doesn't clear it. If the merchant knows their subscription renewals cluster at a particular time of day or month, it's worth checking whether `service_unavailable` clusters around those same windows, since that points to volume-related strain rather than a random outage. As with other network-category declines, hold off on customer emails until retries have been tried. The customer did nothing wrong and telling them otherwise erodes trust.

Questions

• Is `service_unavailable` the same as the customer's bank being down?+

  Not necessarily. It can point to any part of the processing chain, the gateway, the card network, or the issuing bank, being temporarily unavailable rather than pinpointing the bank specifically.

• Does `service_unavailable` mean there's a problem with the customer's card?+

  No. It's a systems-availability issue in the payment infrastructure, not a statement about the card's condition, balance, or standing.

• Why would `service_unavailable` cluster around certain times of day or month?+

  If a merchant's subscription renewals batch together at a particular hour or date, the resulting volume spike can occasionally strain part of the processing chain, producing more `service_unavailable` declines in that window.

• Should I retry immediately after seeing `service_unavailable`?+

  An immediate retry sometimes works, but spacing the first attempt out by a few hours gives the affected system more time to recover, which improves the odds of success.

• Does Foxhound distinguish `service_unavailable` from a hard decline like an expired card?+

  Yes. Foxhound's classifier routes `service_unavailable` into the retryable network bucket, while hard declines like expired cards go into a separate, non-retryable bucket that skips automated retries entirely.