Changing a saved billing method did not change an open invoice

Translate “I changed my card” into a recorded action

Record where the update happened, when it happened and what the confirmation actually said. Saving a method, selecting a method during checkout and setting a billing default describe different actions to investigate. Match the action to the provider customer reference used by the affected subscription; a matching email or familiar display label alone does not establish that the invoice uses the same record.

Stripe’s setup-mode guidance separates saving a payment method from charging it. A successful save therefore does not establish that an outstanding invoice was paid. Keep the saved-method reference and the invoice reference separate, and use only non-sensitive internal references in the worksheet. Do not ask the buyer for a card number or authentication code to compare the records.

Read the default hierarchy on the affected invoice

For subscription invoice collection, Stripe documents the priority in this order: the invoice’s default payment method, the subscription’s default payment method, the customer’s default payment method, and the legacy customer default source. Inspect the settings attached to the particular invoice and subscription. A customer-level change cannot, by itself, establish that a higher-priority invoice or subscription setting changed.

Work down that hierarchy and record each setting as present, absent or not yet inspected. The first applicable documented default explains the configured precedence, subject to the actual collection setup. If an invoice or subscription still names the earlier method, that is a concrete scope mismatch to address with the billing owner. If only the customer default changed and no higher setting is established, the hierarchy still does not prove that an already-created payment attempt has been updated.

Also record whether this invoice is collected by automatic charging or by emailing the invoice. Stripe documents both routes. Do not apply an automatic-collection expectation to a record that uses the other route. The installed store connector may expose its own controls; its version and documented behavior are needed to say which provider setting an action actually updates.

Put the existing payment attempt on its own timeline

Compare the method-change time with the invoice and any linked payment-attempt times. Read the attempt’s own reference, method reference and current recorded result. Do not substitute today’s customer default for the method shown on a historical attempt. Preserve what the records say before editing a default or asking for another payment.

The documented precedence does not answer whether your connector changes an existing attempt, creates another one, or leaves it awaiting another action. If that behavior is unconfirmed, name it as the remaining question. An unresolved attempt requires reconciliation before another collection action, because changing a setting is not evidence that prior payment activity has stopped or that an outstanding amount remains unpaid.

Choose a correction with a defined scope

If the update only saved a method, establish whether a billing-default change was actually requested. If a higher-priority setting retains the previous method, identify that setting and ask the authorized billing owner to decide the intended scope. If the defaults appear consistent but the current attempt differs, investigate that attempt and the connector’s documented handling. These findings lead to different actions; repeatedly saving the same method does not resolve the distinction.

Before any future use, retain the customer’s agreement for that use. Stripe’s save-and-reuse guidance requires specific consent for offline charging and future-purchase reuse; saving a method is not unrestricted permission to charge it. After an authorized correction, use the affected invoice and payment result to describe what actually happened rather than promising that every open or future invoice has changed.

For a Prism checkout-review consultation, describe the store, research-only products, update surface and unresolved setting or attempt in plain language. Keep full billing records in the authorized systems. Scope, responsibilities, fees and terms are discussed before work. The inquiry receives email follow-up and does not book an appointment, buy a repair or submit a processing application.

Billing-default scope map

Complete the map for one actual open invoice. Mark each scope present, absent or uninspected and retain the time of the observed action. The map identifies which setting or attempt needs attention; it does not authorize a charge or establish the method a future attempt will successfully use.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.