Setting up recurring billing is a game-changer for Kiwi businesses. It secures your cash flow, keeps your admin simple, and makes it incredibly easy for your customers to pay. But even the best subscription models have to deal with the occasional failed payment.
A declined card doesn’t have to mean losing a customer. Here is a straight up guide on how to handle failed recurring transactions smoothly, keep your customer relationships intact, and ensure your database stays secure.
Understand why recurring payments fail
When a regular card charge doesn’t go through, our gateway will return a specific error message to help you identify what went wrong.
Token not found or unauthorised: If you see this error, it’s usually an internal setup issue rather than a customer card problem. Double-checking that your Merchant ID matches the original account will usually get this sorted.
Recurring transaction declined: This is the most common error. It doesn’t mean your setup is broken. It simply means the customer’s card has expired, or they have insufficient funds in their account to cover the bill.
Use a secure card-update flow
When a card expires or has insufficient funds, you don’t need to delete the customer’s profile and start from scratch. Chasing clients over the phone for new card numbers is time-consuming and creates security risks.
The best approach is to automatically email the customer and direct them to a secure ‘update card’ page on your website . Our system encrypts the data, stores it in our Level 1 PCI DSS compliant vault, and updates the existing token.
Keep your compliance scope low
Using tokenisation for recurring billing isn’t just about convenience – it’s your best defense against data breaches. Swapping sensitive card numbers for unique tokens ensures that full primary account numbers (PANs) never sit in your local environment .
By keeping raw card data off your servers, you keep your pci compliance scope to an absolute minimum.
