Customers can now replace their card themselves when a payment fails
When a subscription payment through QuickPay fails, your customer can now fix it themselves in the customer portal. The affected subscription shows an "Update card" button where the customer can pick another saved card or add a new one. The payment is then retried automatically within 1-2 days - no money is taken during the card change itself.
Historical retrospective - August 2026 This article was written afterwards and describes the feature as it worked during the stated period.
When a subscription payment through QuickPay fails, your customer can now fix it themselves in the customer portal. The affected subscription shows an “Update card” button where the customer can pick another saved card or add a new one. The payment is then retried automatically within 1-2 days - no money is taken during the card change itself.
If a new card is saved but cannot be attached immediately, the customer portal keeps showing what to do next. The notice disappears automatically once that card is selected for the subscription.
You can also alert the customer directly from the renewal overview: a failed payment now shows a “Notify customer of failed payment” button that sends a reminder in your name with a link to the customer portal.
In addition, a card with a payment in progress can no longer be removed by mistake, and customers with no saved cards at all can now add their first card in the portal.
Default card and subscription card
Later card management distinguishes the customer’s default card for new purchases from the card on an existing subscription. When replacing a card, check which of the two places the change applies to. A new card does not reopen old periods or prove that an unresolved attempt completed. Follow payment status separately. See the current guide (Markdown file, AI agent-friendly)
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.
