The Unread Bank Message Behind Insurers' Involuntary Churn

An interview with Nicolas Lejaeghere by Sean Murphy
A policyholder closes her bank account and moves to another bank. She has no intention of cancelling her insurance, and the bank switching service even informs the insurer of her new account number. Inside the insurer, nothing changes. Her record still flags her as a direct debit customer, the next collection fails, and the bank sends back a message saying the mandate is no longer active. The failed payment passes to debt management, which sends letters, asks a local office to call her and eventually writes the premium off. By then the customer has gone, and the insurer has an explanation ready. "If they don't pay, it's their problem. They are not insured," is the sentence Nicolas Lejaeghere often hears when he raises this topic.
Lejaeghere has spent eight years at Twikey, the Belgium based fintech that connects to banks for account-to-account payments and to payment service providers for cards. That reach across both, he says, is why insurers are interested, since most of them collect premiums through bank payment methods. Twikey currently serve 2,200 customers in 16 countries, Lejaeghere says, onboard around 300 new ones a year, with offices in Belgium, the Netherlands and Germany. Customers include Société Générale and ING's insurance business. When Smile Sail invested in Twikey in February, the deal announcement said the company had processed more than €29 billion in recurring payments in 2025.
Insurers, in Lejaeghere's experience, automate almost everything in their internal processes but pay little attention to the payment itself. He separates voluntary churn, when a customer asks to stop a policy, from involuntary churn, when a customer leaves because a payment failed and the process around it failed too.
Card payments fail for three main reasons; insufficient funds, chargebacks and problems with the card itself, such as an expired card or token, and each needs its own fix.
In Western Europe, though, most insurers collect by direct debit through their own bank, and few understand why those collections fail.
The same issue turns up in most of the payment analysis he runs, and he is running plenty of them these days. An insurer's ERP system flags tens of thousands of customers as paying by direct debit when a large share of them no longer do.
A consumer can open a banking app and cancel a mandate, and the insurer's system never hears about it. Once a customer is flagged as paying by direct debit, in his experience, the system treats them that way for good. A closed account is not a request to end a policy, yet the bank's return message signalling the inactive mandate goes unread. The logical response, in his view, is to switch the customer to manual payment, tell them so and offer a link to sign a new mandate.
Insufficient funds need a different routine. Under the SEPA rulebook, an insurer must tell the customer that the collection failed and that it will try again, with a formal pre-notification, before it can retry. A few days later, Lejaeghere says, the money is there in around 60 per cent of cases. With adjustments like these, Twikey's customers reach payment success rates of 99.5 to 99.8 per cent, he says, leaving a small remainder for debt management. Manual payers, in Twikey's analyses, pay on average 15 days later, which weighs on an insurer's liquidity.
Twikey's answer is to bring the payment methods together under one set of rules. On the account-to-account side are SEPA Direct Debit for recurring premiums at a few cents a transaction, SEPA credit transfers for paying out claims, Bacs Direct Debit in the UK and "pay by bank", an instant SEPA credit transfer the customer confirms in their own banking environment. If a retry fails, the insurer can email a link to pay the open amount by bank. Pay by bank can also activate a new policy: the first premium brings in the customer's name and account details, which can support a legal mandate for future collections, and the payment can even serve as a signature on a document. On the card side, Twikey support recurring payments through Apple Pay, Google Pay, Bancontact and others. Insurers connect through an API or use Twikey's portal without an integration, and the rules of each scheme are built in.
He sees a newer tool in Verification of Payee, which euro-area payment providers have had to offer since 9 October 2025 under the Instant Payments Regulation to check that an account number matches the payee's name. When a new customer enters an IBAN to set up a direct debit, Twikey can run that check in the background without changing the screen the customer already sees.
He is still waiting for an insurer to give recurring payments the attention it gives the rest of its operations. The policyholder who switched banks didn’t necessarily want to cancel their policy, and in Lejaeghere's account she is the customer an insurer can most easily keep.



