A customer buys a pair of headphones through a buy now, pay later service. The purchase takes a few taps. The payment schedule appears in the app. Weeks later, a payment is missed and an unfamiliar number calls.

The customer may have forgotten the date, changed bank accounts or run short of money. The collection process has to find out which. Treating every unanswered call as unwillingness to engage leaves those very different situations unexplained.

In the Federal Reserve's 2025 survey, 26% of U.S. buy now, pay later users reported paying late at least once in the previous year. The finding, published in May 2026, shows why repayment deserves deliberate design alongside acquisition. It does not tell a lender which channel an individual customer prefers. Federal Reserve, 2025 SHED

Make the next step recognizable

Return to the customer with the missed instalment. Before making a payment, that person needs to recognize the sender, understand the account and see what action is available.

A permitted message can direct the customer to a secure account experience. Once verified, the customer should be able to review the balance, check recent payments and understand the available options. Language matters here. An unclear amount or a payment button without an explanation can create another reason to stop.

The route should also work when the customer starts independently. Opening the lender's app should lead to the same account status and available options as following an authorized communication. Conflicting information undermines the whole exchange.

Leave room for a different answer

Digital access solves an access problem. It cannot assume the person has the money to pay.

Someone who can settle a missed instalment needs a straightforward payment route. Someone disputing the balance needs a different process. Someone whose circumstances have changed may need a conversation with a specialist who can explain the support available under the lender's policies.

These routes should be visible before a customer reaches a dead end. When human help is needed, the specialist should receive the account context and steps already attempted. Requiring the customer to reconstruct the same history adds effort at a difficult moment.

Follow the payment beyond the button

A submitted payment and an updated account are separate events. Confirmations should state what has happened, what remains pending and when the customer can expect the account to reflect it.

The operation should then check whether customers complete the available steps, where they leave and which problems return through another channel. A high message-open rate says little if people cannot finish.

Repayment should feel like a continuation of the credit relationship. Give the customer a clear view of the situation, a usable next step and access to someone who can help when the standard options do not fit.