Gorilla Dash

Help Centre

Guides for every part of Gorilla Dash

Step-by-step how-to guides written by the team that builds the product. Read them here, or download any guide as a PDF.

Network Store Billing

Failed payments: retries, suspension and getting paid

Download PDF

What happens when a renewal charge is declined, how to set the retry schedule, and the fastest route back to a working payment method.

Last updated September 2, 2026


Cards expire, get replaced after fraud, and get cancelled when someone leaves. Failed renewals are routine traffic in any store with subscriptions, not a sign something is broken.

What happens automatically

  1. The renewal charge is attempted and declined.
  2. The unpaid renewal order appears in Accounts Receivable.
  3. The charge is retried on your schedule — by default 3 days later, then 7 days after that.
  4. If you set a suspend threshold, the subscription is suspended after that many failures. Left blank, it never suspends on its own.

The schedule lives in Settings → Failed payments and applies to the whole store.

Choosing a retry schedule

ScheduleSuits
3 then 7 daysThe default. Long enough for a replacement card to arrive, short enough to catch the month.
1 then 3 then 7Higher volume stores where a fast retry catches temporary declines.
Retries offOnly where you collect manually and would rather chase by phone.
RETRIES DO NOT FIX A DEAD CARD
Retrying helps with a temporary decline — insufficient funds, a bank block. An expired or cancelled card will fail every time, however many attempts you allow. Two failures on the same card means stop retrying and ask for new details.

Suspension

A suspend threshold stops a subscription after that many failures. It is blank by default, and most networks leave it that way — you would usually rather chase a tribe than cut off their service over an expired card.

Set it where the thing being sold costs you money to keep supplying, and where cutting it off is a proportionate response. Tell the network the rule exists before you turn it on.

WITHOUT A THRESHOLD, NOTHING STOPS ON ITS OWN
A tribe can fail every renewal indefinitely and keep the service. That is a deliberate default, but it only works if somebody is watching Accounts Receivable. Nobody watching plus no threshold equals free service.

The actual fix

Almost always new card details. Send a card request from Accounts Receivable — the tribe gets a secure link, enters the details themselves, and the next retry succeeds. Nobody reads a card number aloud and your team never handles it.

Getting ahead of it

The dashboard tile Will be billed, no card lists tribes due to renew with nothing saved to charge. Everything on it is a failure that has not happened yet. Clearing that tile weekly prevents more failures than any retry schedule.

Next · Network Store BillingAccounts Receivable: seeing and collecting what you are owed