Each time Rhythm charges an installment entry, or a recurring line's repeat order finishes, Rhythm updates the schedule based on the result. This article explains what changes after a success, decline, or other failure, and when a schedule closes automatically.
When a Charge Succeeds
A successful charge or repeat order marks the related entry as billed. If the schedule was already cancelled, a later success sets the schedule back to active. This can happen when a charge was already in progress before the schedule was cancelled, so a late success can reactivate a schedule you expected to stay closed.
In rare cases, a successful payment might not fully satisfy its related invoice because of a timing issue from an earlier billing-run period. If the invoice stays open after the payment succeeds and the member's status does not reflect the payment, you may need to close the related order manually to restore their active status.
When a Charge Is Declined
A declined charge reopens the related entry, so the entry returns to unbilled instead of staying tied to the failed attempt. Rhythm also changes the schedule status to payment declined.
Billing runs use payment declined status to decide which schedules should receive reminders or eventually be cancelled. See How Billing Run Pre-Processing Selects What to Do for how Rhythm chooses those reminders and cancellations. The member is only notified of the decline when the billing run has a failed-payment notice configured. Rhythm does not automatically recharge the card, does not automatically change the related membership when an installment is past due, and does not offer a report built specifically to list failed installments.
Rhythm does not always show a specific reason for a declined charge, and more than one cause is possible. These common responses are worth checking:
- A mismatched billing ZIP or postal code can fail a payment attempt by itself, and the card is not actually charged.
- An "expired card" response can appear even when the card's expiration date on file is correct and current. If you have confirmed the date is right, check whether the replacement card has been activated.
- A generic authorization-declined response can mean the issuer cancelled or otherwise declined the card's authorization.
- A "transaction not allowed" response can point to a card restriction, such as a daily spending limit, rather than a problem with the payment itself.
- Suspected fraud on the issuer's side usually means the cardholder needs to check with their bank before trying again.
When you troubleshoot a decline, start with your payment gateway or processor's response reason and decline code. Those individual codes usually point to a specific, addressable cause, so do not assume the failure means there is a broader outage. If your gateway shows no transaction attempt for the failed charge, it has no decline reason to give you. In that case, the payer's bank is the better place to ask about the card's restrictions or capabilities. If the cause still is not clear, have the cardholder check with their issuing bank. If the bank confirms the charge should be approved, it can be tried again on a later billing run.
Each installment entry tracks its own outcome, so installments on the same schedule do not succeed or fail together as a group. One installment can remain declined and unresolved while a later installment on the same schedule fails at first and then settles successfully. If a customer's payment history on a schedule looks inconsistent, with some installments paid and others unpaid, check for repeated declines on the account before assuming something else is wrong. Confirm the card details and available funds before retrying.
Tip
Rhythm has no built-in notification specifically for a declined installment payment. If you want to track these as they happen, set up a billing query on installment schedules filtered to error status with a message containing "declined," include the schedule's error message in the output, and schedule the query for regular delivery.
When a Charge Fails for Another Reason
A charge or repeat order that fails for a reason other than a decline also reopens the affected entry. If the error is not related to the card or bank account itself, Rhythm reopens the entry and sets the schedule status to error instead of payment declined. A missing transaction token during a renewal or checkout charge is one example of this kind of failure. It can appear alongside a pending or unsettled authorization still showing on the card processor's side. Another example is a billing-run installment charge that fails because the saved payment method is no longer correctly linked to the schedule. If Rhythm cannot find a payment token from your processor when it processes a later charge, that now appears as a failure rather than letting the order complete silently. If you ever see a completed order or membership with no matching payment record behind it, treat that as something to investigate.
This distinction matters because billing runs do not follow up on errored schedules the same way they follow up on payment-declined schedules. No automatic reminder or cancellation ever reaches a schedule in error status. If a customer's installment schedule has stopped billing and is not in payment-declined status, check whether it is in error status instead. A staff member needs to find and resolve those schedules directly, because nothing brings them back automatically.
In rarer cases, multiple payment attempts on the same installment entry can contribute to a duplicate charge or a fulfillment mismatch. If you see a duplicate charge tied to an installment, check whether more than one payment attempt was made for that same entry.
Which Schedules Billing Runs Can Even Find
A billing run's charging step finds only active schedules with a next billing date, and its reminder step finds only payment-declined schedules. A schedule in error status appears on neither list. That means an errored schedule does not surface through the normal billing-run process, so you need to locate it directly. Once a schedule moves to payment declined or error, it also drops off the charging list, so later installments stop generating automatically until the schedule is active again.
Cancelling a related recurring gift through the Portal does not necessarily cancel the installment schedule behind it. If the schedule itself stays active after the Portal cancellation, Process Installment Schedules can still find it and charge the donor again. A successful charge can then set the recurring gift's status back to active.
Schedule Totals and Next Dates Stay Current
Rhythm recalculates a schedule's billed total, outstanding total, and next installment date whenever the schedule is saved through the usual charging and update paths. Those figures should reflect the schedule's current entries.
If a schedule's totals or next date do not match its entries, refresh the page or reopen the schedule. A save that goes through another path can occasionally leave those figures stale until the next ordinary update recalculates them.
In rarer cases, an individual installment can get stuck showing Processing even after its payment appears to have gone through. While the installment is in that state, you generally cannot delete it or otherwise change it from the schedule. Later installments may not process normally until the stuck installment's status clears.
When a Schedule Closes on Its Own
A schedule closes automatically as completed when every entry on it is billed. This rule overrides the schedule's previous status, so a cancelled or payment-declined schedule still becomes completed if all of its entries end up billed.
The exception is a schedule with any recurring entry. Because a recurring line has no fixed end, a schedule that contains one never completes on its own, no matter how many billed entries it has. A recurring schedule closes only when you cancel its recurring line yourself.
When an Outcome Does Not Match Anything
If a payment or repeat-order outcome does not match a schedule, or does not match an entry on a schedule that is waiting on it, Rhythm discards the outcome. Nothing changes on any schedule, and no billing run is notified. This is expected when an outcome arrives after its matching entry has already been resolved another way. It is not an error; it is a signal with nothing left to update.
One way this appears is when an installment's processing attempt reports that no invoice was created, then a retry creates a second invoice. The installment entry can remain Open even though a related invoice was eventually paid, because the paid invoice is not the one the installment entry is tied to. Another way this appears is when a billing run repeatedly fails against a deleted or missing saved-card token, then payment is later collected outside the billing run with an updated method. The final installment can still be left open, because the earlier billing-run failure was never matched to that later, different payment path.
Related
See the related articles for how a schedule is first built from an order, managing a customer's installment schedule day to day, processing installments outside their normal date, and how a billing run decides what to charge, remind, or cancel.