Explain payment results that are still pending

What this means for your practice

Ask the supplier to demonstrate delayed-result handling and a safe status-check route. A timeout should not automatically be described as a declined payment or a confirmed booking.

Questions to take to your supplier

Ask the supplier to delay a fictional provider notification. Inspect the visitor message and the staff review queue when the late result arrives. The team should be able to resolve the pending state without asking the person to infer the outcome from a frozen page.

Agree the working process

Write the visitor and staff wording for a pending result before testing the payment connection. The person needs to know what is known, what remains uncertain and the appropriate next step, without being pushed to pay again based on an assumption. Ask the supplier how the actual provider supplies later results and how those are connected to the original attempt. Keep a staff review route for pending states that remain unresolved beyond the practice's agreed window. Test both a late successful result and a late unsuccessful one through the provider's supported arrangements.

Inspect what changes in the administrative record and what, if anything, is communicated. A delayed payment notification should not silently create an unrelated confirmed booking unless the authorised business process supports that action. Give reception a way to check the current result using the appropriate reference. Reviewing pending cases by their age helps the team identify a stuck handover while avoiding the misleading conclusion that every short delay is a failed transaction.

How to check the result

Track unresolved payment states beyond the agreed review window.