Failed card payments: choose a path and inspect charge details
After a failed card payment, the plan's path is shown: continue, cancel immediately, or retry until a deadline. Open details for attempt status, authorizations, and planned attempts. An authorization or planned date is not proof of a completed charge. For installments, the individual unpaid, due slice is evaluated. See the current guide ### Choose the next action
Historical retrospective - March–April 2026 This article was written afterwards and describes the feature as it worked during the stated period.
After a failed card payment, the plan’s path is shown: continue, cancel immediately, or retry until a deadline. Open details for attempt status, authorizations, and planned attempts. An authorization or planned date is not proof of a completed charge. For installments, the individual unpaid, due slice is evaluated. See the current guide (Markdown file, AI agent-friendly)
Choose the next action
First check whether the payment is declined or still pending. Update an expired or invalid card, but do not treat card replacement as proof that an earlier attempt succeeded. A planned date shows the next plan, not the result of a charge.
Step by step
First check whether the attempt is declined or pending. Open the plan choice, check whether the card expired, and choose update card or manual retry when offered. Wait for a new status before cancelling. A later attempt can succeed, so a pending payment must not be treated as failed.
Example: An attempt is pending Monday and the plan offers cancel after failure. Wait for the outcome because pending is not declined. The next action follows a documented decline.
When to seek help
If status remains pending, a replaced card cannot be selected on the subscription, or invoice and payment show conflicting information, follow the visible integration status. Do not conclude from card expiry alone. For an installment, the relevant slice must be unpaid and due before a cancellation decision.
FAQ: Can I cancel based on an authorization? Not before its outcome is resolved. Is a planned charge a receipt? No. Can I retry at any time? Only when the current flow offers it.
FAQ and boundaries
A plan’s action after failure is not a payment. “Retry” is a plan, “declined” is an outcome, and “pending” requires waiting. Card update helps only when the new card is actually selected on the relevant agreement. When statuses conflict, use the specific payment and invoice as evidence, not the planned date alone.
Support scenario
A new attempt can change the next action. Check payment status again after card replacement or manual retry before cancelling. If the customer has several subscriptions, identify which subscription owns the failed period; one failed attempt is not an overall customer status.
Check after the action
Use this check during follow-up: note what was visible before the action, perform only the selected action, and check the document or mandate afterwards. Read a status again before informing the customer if it changes later. The retrospective describes the documented milestone; the current guide and interface determine today’s steps. Examples use fictional customers, amounts, and dates.
If the result differs
If the result does not match expectations, keep the visible status and investigate the relevant prerequisite instead of repeating the action blindly. Check currency, date, customer, payment method, and whether the document was already sent or booked. When answering a customer, distinguish what the system recorded from what the bank or recipient has not yet confirmed.
The people and AI helpers behind the updates
Bo Møller and Emil Højbjerg are the primary developers behind Alunta. They spend most of their time coding, so they have delegated the wording of these explanations to our AI helpers.
The AI helpers write from the updates we have deployed to the product. Bo and Emil are behind the changes and remain responsible for ensuring the information reflects what was actually released.
