Most agency dashboards can tell you the contact rate.

Many can break down promises to pay by campaign, collector, or time of day.

Far fewer can answer two basic questions:

Of the consumers who start a payment, how many actually finish?

And when they don’t finish, where do they stop?

That missing part of the payment journey is easy to overlook. A consumer agrees to pay, the payment does not settle, and the account appears the next morning as another broken promise.

But that doesn’t always mean the consumer changed their mind.

Sometimes the payment process lost them.

Every incomplete payment represents intent the agency already worked to create. Improving completion can increase collected dollars without requiring the team to generate another contact or another promise to pay.

What is payment abandonment in collections?

Payment abandonment in collections happens when a consumer begins the payment process but leaves before submitting the transaction.

The intent was there. The payment wasn’t completed.

That is different from a payment that was submitted but declined. It is also different from a payment that was approved and later returned.

All three leave the agency without a completed payment, but they’re not the same problem.

A useful payment funnel separates them:

1. Started to submitted: Did the consumer complete the payment form or IVR flow?
2. Submitted to approved: Was the transaction authorized?
3. Approved to settled: Did the money successfully settle without being returned?

The exact processing timeline varies between card and ACH payments, but this framework provides a practical way to see where completion breaks down.

When agencies group everything under “the consumer did not follow through,” they lose the information needed to fix the actual problem.

One issue may require a different follow-up strategy. Another may require a better payment page, a clearer recovery path, or support from the payment provider.

Where do consumers drop off?

Public benchmarks specific to collection-payment abandonment are scarce. That is part of the problem. Most agencies aren’t measuring it.Still, there are five places worth checking first.

Still, there are five places worth checking first.

1. The payment channel changes

A consumer agrees to pay over the phone but receives a link to a portal. Or they agree over text but learn they must call during business hours.

In each case, the consumer starts in one channel and must finish somewhere else. Every handoff adds another step and another chance to lose the payment.

The consumer who felt ready to pay at 8:40 on Tuesday night may not feel the same way at 9:15 the next morning.

Whenever possible, the channel that creates the payment intent should also help the consumer complete the transaction.

2. The payment form asks for too much

Entering card details on a phone is not difficult in theory.

In real life, the consumer may be sitting in a car, walking through a store, managing children, or searching through a wallet while trying to keep a browser open. A long form makes that moment harder.

Card number. Expiration date. Security code. Billing ZIP. Name. Address. Account details. Login credentials.

Each additional field creates another opportunity for a typo, confusion, or interruption.

Research from Baymard Institute shows that many e-commerce checkouts contain more form fields than they need. Collections and e-commerce are different, but the basic lesson still applies: unnecessary steps make completion less likely.

A collections payment page shouldn’t ask for information the agency already has or does not truly need.

3. The session expires

A consumer pauses to find a card or check a bank balance.

They return a few minutes later and discover that the session has expired.

The information they already entered is gone, and they are asked to begin again.

Some will.

Others will decide they have spent enough time on it for now.

Session security matters, but so does understanding how long a real person may need to complete the process. Agencies should review timeout settings, warning messages, and what happens when a consumer returns after a session ends.

4. The mobile experience is technically functional, but still difficult

A payment page can open on a phone without being easy to use on one.

Small fields, crowded screens, unclear buttons, slow load times, and forms that require constant zooming can all interrupt the transaction.

The best way to understand the mobile experience isn’t to review it from a desktop preview.

Open the payment link on a phone. Start at the same place the consumer starts. Try to complete the payment without using information that has already been saved in the browser.

That simple test often reveals problems that are difficult to see from an internal dashboard.

5. The total changes late in the process

A consumer agrees to pay one amount and sees a higher total near the final screen.

Even when the fee is valid, properly structured, and permitted for the transaction, the timing of the disclosure matters.

If someone agrees to pay $200 and later sees a total of $214.95, the experience has changed. The consumer is no longer simply completing the payment they already accepted. They’re being asked to make another decision.

That’s where trust can slip.

Agencies should always review convenience fee payment programs with qualified counsel because these programs carry important compliance considerations.

From the payment-completion side, the direction is straightforward:

• Disclose the fee clearly.
• Disclose it early.
• Show the full amount before the consumer reaches the final confirmation screen.

The amount being discussed should match the amount the consumer is being asked to authorize. When possible, explain the base payment and the fee together rather than separating them across different screens or steps.

That gives the consumer a clearer decision and gives the agency a cleaner record of what was presented. Clear disclosure can support compliance and payment completion at the same time.

How should agencies measure payment completion?

Start with a top-line payment completion rate: Settled payments divided by payment starts.

That number gives you a broad view of how many initiated payments reach the finish line.

It does not, however, tell you why the others did not.

For that, measure each stage of the payment funnel.

Started to submitted

Of the consumers who opened the payment page or began the IVR process, how many submitted a transaction?

A large drop here may point to:

• A long or confusing form
• A channel handoff
• Mobile usability issues
• Session timeouts
• Late fee disclosure
• Missing payment options

This is the stage where true payment abandonment occurs.

Submitted to approved

Of the payments submitted, how many were approved?

A drop here may be caused by:

• Insufficient funds
• Incorrect card or account information
• Issuer declines
• Payment method restrictions
• Authorization or processing issues

This isn’t usually a form problem. The consumer completed the process, but the transaction didn’t receive approval.

Approved to settled

Of the payments that moved forward, how many settled and remained collected?

A drop here may point to:

• ACH returns
• Closed or invalid accounts
• Disputes
• Reversals
• Other downstream processing issues

This stage captures both settlement issues and payments that were lost later through a return, reversal, dispute, or chargeback. These outcomes require a different response than a consumer who left before submitting anything.

What do the numbers tell you?

Once you can see the three stages, begin segmenting the results.

Compare:

• Mobile and desktop
• Agent-assisted and self-service
• Portal, text, phone, and IVR
• Card and ACH
• One-time and recurring payments
• Different fee and no-fee payment paths

The goal is not to create another oversized report.

The goal is to find the gap between your strongest payment path and your weakest one.

Desktop submission rates that significantly outperform mobile may point to a form or usability issue. Strong payment intent paired with weak completion in one channel may signal a broken handoff. Frequent declines after submission may require another payment option or a clearer recovery path.

Returns and disputes, however, call for a different operational response.

Ask your payment provider or web team what step-level information is currently available. You may not need a new platform, but you may need to ask more of the data you already have.

Even a basic view of starts, submissions, approvals, and settlements can reveal more than a single promise-to-pay number.

And on a high-volume payment path, even a modest improvement in completion can mean more collected dollars without increasing contact activity or adding work for collectors.

Not every unfinished payment can be fixed

Some consumers will reconsider, lack the necessary funds, or encounter an issue outside the agency’s control. The goal is not to eliminate every incomplete payment. That isn’t realistic.

The goal is to understand which failures reflect an ability-to-pay issue, which reflect a processing outcome, and which point to a payment experience the agency can improve.

A consumer who could not pay is different from a consumer who tried to pay but could not get through the process. When agencies can see that difference, they can respond more appropriately and focus on the parts of the journey they actually control.

Where Payment Savvy fits

Payment Savvy helps agencies turn payment intent into completed, retained payments by connecting the channels, processing, fee-program execution, and reporting behind the payment moment.

You can begin this work internally. Pull your starts, submissions, approvals, settlements, and returns. Open the payment path on a phone and complete it the way a consumer would. Then walk each handoff with operations, compliance, and the people responsible for your payment channels.

A strong payment partner should help you validate what the data shows, identify gaps across channels, and prioritize the changes most likely to improve completion.

If you would like a second set of eyes, we would be glad to review the payment path with you.

The distance between “yes” and paid

A promise to pay matters. It shows that the conversation moved forward and the consumer made a decision.

But the payment process still has work to do.

The channel needs to be available. The instructions need to be clear. The form needs to work. The amount needs to match what was discussed. And the transaction needs to move through processing and settlement successfully.

Some payments will still fail for reasons no agency or payment provider can prevent.

But the process itself should not be the reason a ready consumer cannot finish.

A promise to pay is progress.

A completed payment is the finish line.

Our job is to make the distance between the two as short and clear as possible.