Faster collection when a customer changes card
When a customer's card has been declined and the customer updates it in the customer portal, Alunta now tries to collect the money right away instead of waiting for the next charge run.
When a customer’s card has been declined and the customer updates it in the customer portal, Alunta now tries to collect the money right away instead of waiting for the next charge run.
Charge the new card right away
If the customer puts a new card on the subscription through the portal (also after card setup with QuickPay, Stripe or Cost+), Alunta queues one charge immediately: the due periods, or the first due installment slice. This happens when automatic card charging is on and the provider is connected. The normal charge run collects the rest. Teams with manual card charging are not affected.
The portal now tells the customer that the payment may be attempted right away once the card is updated.
Fewer pointless attempts on cards that cannot be used
- A wait per card. After a decline, Alunta waits 24 hours before trying the same card again. The wait applies only to the declined card, so a new card can be used at once.
- Stripe cards stop at once on permanent declines. If the card is reported lost or stolen, the card number is invalid, the authorization has been revoked, or the bank asks not to try again, automatic attempts on the card stop immediately. Other providers stop after 8 declines in a row. Attempts resume when the customer puts another card on the subscription, or a charge on the card succeeds.
- Retry, then end the subscription. If the card was stopped by a permanent decline, it is not tried again when the deadline is reached. The subscription is ended under the rule without contacting the bank one more time.


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.
