Direct debit sounds beautifully simple: a borrower gives permission, and repayments happen on time. No awkward reminders. No “I was just about to transfer it.” Everybody wins.

Then you try to build it.

At Lendsqr, setting up a mandate could involve a customer, a lender, a bank, and a payment provider. One might say the request was received. Another still needed the customer to authorize it. The bank might take longer to activate it. Meanwhile, the product had to answer a very ordinary question: is this ready to collect a repayment or not?

I worked on this with Donald Peters. We had to make the journey understandable for the person setting up the mandate and trustworthy for the lender relying on it. A green “Success!” screen was tempting, but banks have never been known to speed up because a button looked confident. 😭

A request was not an active mandate

We worked through the journey from the lender starting a request, to the borrower giving consent, to the bank confirming activation, to the first collection. That exposed the central product problem: creating a mandate and activating it are different events. If we treated the first as the second, a borrower could think they were finished while a lender expected repayments from a mandate that was still pending.

So we made the steps visible. A borrower can be guided through the action they actually need to take, whether that is completing authorization or waiting for the bank. The lender can see the mandate’s current state and follow its progress instead of guessing from a single optimistic label. If something stalls, support has a clearer place to start looking.

We also made the journey work from more than one starting point. A lender might raise a mandate request; a borrower might reach it during a loan application. Both should lead into a familiar flow, not two slightly different versions of “please connect your bank.”

The next step depended on the provider

Different banks and providers do not all activate mandates the same way. We did not need to pretend they did. We needed the product to give each customer the right next step while describing the resulting state consistently.

That meant being careful with the language of success. A provider accepting a request is useful progress; it is not proof that the bank has activated the mandate. We kept pending states pending until there was a real update. Not the most exciting status badge, perhaps, but one I would trust with a repayment.

A collection needed an honest status

The same honesty matters after activation. A collection might only partially succeed, or its result might take time to confirm. The product should record what was actually collected and make the remaining amount clear. When the outcome is uncertain, the next step is to check what happened before trying to collect again. “Maybe charge them twice” is not a product strategy I wanted to ship. 😂

Donald and I worked across those customer, lender, and provider boundaries to make direct debit feel simpler without hiding the parts that matter. The result is a clearer path to authorize a mandate, a more truthful view of its status, and a safer basis for collecting repayments.

Good financial products do not make uncertainty disappear by changing its color to green. They tell people what happened, what is still pending, and what they can safely do next.