Your client says the payment went through. Your assistant sees a booking, but its status is not what either of you expected. The useful response is a calm check of the evidence, not another payment link sent in a hurry.
For your Manchester coaching practice, keep three questions separate: is the time reserved, has the relevant payment succeeded, and is the appointment confirmed for delivery? They usually belong to one journey, but they are not interchangeable facts.
Gbeya connects paid bookings with checkout and payment processing. This guide explains how to reason about that journey and how to investigate an exception without treating a browser message, email or calendar entry as the entire record.
Which part of the journey needs attention?
Use the references for this exact booking and transaction.
- What service and slot did the client request?
- What does the provider say about the matching payment now?
- Does the order amount and currency agree?
- Is the intended appointment currently confirmed and available?
- Is there a separate cancellation, partial refund or unresolved client action?
Investigate the first disagreement between records and assign its next action. Preserve facts that already agree.
This is an operational method, not permission to alter payment records or a guarantee of provider settlement.
Track 1
Appointment: held → confirmed → delivered
A temporary hold protects a slot. Check the confirmed appointment before treating the session as ready to deliver.
Track 2
Payment: pending → verified → refund if applicable
Check the paid record separately from a browser response. A refund needs its own verified outcome.
These are parallel operating tracks, not live transaction data. At each handover, check the relevant appointment and payment records together; investigate any mismatch rather than assuming one changed the other.
1. Understand what a held slot means
A hold gives the client time to complete the next step without immediately offering the same slot to someone else. It does not establish that payment has succeeded. Make the distinction visible in the language your team uses with the client.
Gbeya’s paid-booking flow creates a pending reservation before checkout. If payment cannot be arranged through the configured route, the client may instead receive a message about arranging payment. Your team needs an owner for that exception and a clear way to check whether the reservation remains available.
- Why this matters
- A reservation is a scheduling decision; payment is a commercial event. Keeping them separate lets you release an abandoned hold without pretending a successful charge never happened.
- Work through the example
- Suppose a client chooses a £180 session on Tuesday at 10:00 but closes checkout. Record the appointment as awaiting resolution, not as £180 of collected revenue.
- When the approach changes
- A free discovery call may legitimately be scheduled without a payment. Do not impose the paid-session interpretation on every appointment type.
- Your decision
- Read the service and booking context before deciding what the status means. Confirm both the appointment and payment evidence before promising a paid session.
2. Verify the payment rather than the return screen
A person can reach a return page before a payment has reached its final state, or pay successfully and lose their connection before returning. Use the relevant provider payment record and the matching Gbeya order, not the browser journey alone.
Provider guidance distinguishes payment initiation, pending processing and successful completion. Names differ between providers, so use the actual status for the configured method. Check the amount and currency alongside the order reference; a similar customer name is not enough to match a transaction.
- Why this matters
- The provider’s payment state and the application’s order state describe different parts of the same transaction. Comparing their references and values exposes a delayed update or mismatch without requiring the client to repeat payment.
- Work through the example
- For the £180 booking, verify the matching payment reference and GBP amount, then inspect the order and appointment. If the provider reports pending processing, explain that precise state rather than saying the payment failed.
- When the approach changes
- Some payment methods complete later than an immediate card payment. A longer processing interval is not by itself a defect, but the client needs an accurate next step.
- Your decision
- Do not collect a second payment until the first attempt has been reconciled. Escalate an unknown state with its reference and time instead of guessing.
3. Check the appointment after the payment
A paid order should lead to the intended service outcome, but you still need to verify the appointment that the coach will actually deliver. Check the client, service, date, time zone and current availability. A receipt and a calendar invitation do different jobs.
If payment arrives after an earlier hold has been released or the client has changed plans, do not assume the original slot can still be honoured. Resolve the schedule with the client and preserve the payment evidence. A clear explanation is more useful than silently changing the appointment to make the records look tidy.
- Why this matters
- Payment confirmation does not remove scheduling constraints. A late or corrected event must be reconciled with the current appointment, not only the original intention.
- Work through the example
- Suppose the client completes payment after leaving the original booking flow. Your assistant checks whether Tuesday at 10:00 remains the agreed available session before sending a final confirmation.
- When the approach changes
- A deliberately prepaid arrangement may allow payment before the client chooses a time. That is a different offer and needs its own allocation rules.
- Your decision
- Treat the booking as ready when the correct appointment is confirmed and its required payment evidence agrees. Investigate either side that remains unresolved.
4. Give each exception one owner and one next action
Use a short exception note: booking reference, order reference, observed payment state, current appointment state, time checked and next action. Keep payment credentials and unnecessary personal information out of that note. Your assistant needs enough context to resolve the case, not a copy of everything.
Tell the client what is known, what remains under review and when they should expect the next update from your practice. Clear error and success feedback helps people understand whether their action worked. Avoid sending contradictory messages from different colleagues while the case is being checked.
- Why this matters
- An owned exception is less likely to become repeated client effort. The note separates a verified fact from an assumption and makes the handover possible without restarting the investigation.
- Work through the example
- For the booking, the note might say: payment confirmed against the order; appointment time requires review; assistant to contact the coach before confirming an alternative. It should not say “fixed” until the agreed outcome is recorded.
- When the approach changes
- A straightforward resolved payment needs no elaborate incident report. Keep the process proportionate while retaining the reference needed for a later question.
- Your decision
- Close the exception only when the client-facing outcome is verified, not when a message has merely been sent.
5. Separate cancellation, refund and future access
Cancelling a session changes the appointment. Requesting a refund starts a financial process. A provider-confirmed refund and the money appearing in the client’s account are further observations. Explain the relevant state accurately and avoid promising a universal arrival time.
Check the applicable cancellation terms and the actual refund record. If a refund is partial, record the retained amount and what service remains agreed. If the client also has a package or another entitlement, review that separately; a single appointment decision should not silently rewrite every part of the relationship.
- Why this matters
- Different state changes can complete at different times. Keeping them separate prevents a cancelled calendar entry from being misreported as money returned, or a refund request from being treated as final settlement.
- Work through the example
- If the £180 session is cancelled and a £45 partial refund is agreed, the gross amount retained is £135 before fees or other adjustments. That calculation does not prove the provider completed the refund.
- When the approach changes
- A reschedule with no refund may be appropriate under the agreed terms. Preserve the distinction instead of using refund language for any appointment change.
- Your decision
- Verify the refund result and the service arrangement independently. Communicate pending or failed financial steps plainly and follow the authorised resolution process.
A calm reconciliation is better than another payment request
The useful unit of work is the complete appointment journey. A hold, a payment, a confirmation and a refund each need their own evidence. Provider guidance supports those distinctions, while your service rules determine what happens next.
Gbeya links these stages, but an exception still deserves a specific check. A successful-looking message is not enough to establish that every downstream action finished. The client should not have to discover the gap when they arrive for their session.
High confidence in keeping these states separate. Check the configured service and payment method before relying on the complete journey.
This guide explains an operating method. It does not establish that a particular payment, appointment or refund has completed.
Reconciliation calculation with stated assumptions
Keep held value, collected value and refunds separate
Assume ten £180 session requests. Eight matching payments are verified, and one of those payments later has a provider-confirmed £45 partial refund. These assumed counts are not measured Gbeya results.
Requested value: 10 × £180 = £1,800. Verified gross payments: 8 × £180 = £1,440. After the £45 refund: £1,395 before fees and other adjustments.
The two unpaid requests are not £360 of collected revenue. Nor does the calculation establish how many sessions were delivered or the final bank payout.
Report the figures with their state and period. Reconcile delivery and provider settlement separately.
Assumptions worth checking
A slot hold means the client paid.
A hold reserves time; the payment needs separate evidence.
A return page proves completion.
Check the authoritative payment and matching application records.
A receipt proves the appointment is ready.
Verify the current service, time and confirmation too.
Cancelling an appointment returns the money.
Cancellation and refund are separate actions and states.
Experienced operators can match by name alone.
Use the exact transaction and order references, amount and currency.
Your next 30 days
Days 1–7
Map the paid-session journey
List the hold, checkout, confirmation and cancellation rules for one service.
Ready for the next step: A shared vocabulary and owner for each exception.
Days 8–14
Verify ordinary outcomes
Use authorised non-production cases for successful, pending and failed payment paths.
Ready for the next step: Matching records and clear client messages for each tested state.
Days 15–21
Test the difficult timing
Review late payment, released holds, repeated notifications and refund handling in a safe test environment.
Ready for the next step: Specific failures assigned and retested; no unsupported automatic-recovery promise.
Days 22–30
Reconcile real exceptions
Review genuine unresolved records through authorised controls and preserve dated outcomes.
Ready for the next step: No case labelled resolved without the intended appointment and financial state verified.
Questions before you proceed
Does a pending booking mean payment failed?
Not necessarily. It can mean a reservation awaits a further step. Check the matching provider and order state.
Should I send another payment link if the client says they paid?
First reconcile the existing attempt. A second request can create confusion or a duplicate payment.
Is a calendar invitation proof of payment?
No. It concerns scheduling. Verify the commercial record separately.
Does cancelling a session automatically refund it?
Do not assume so. Check the cancellation policy and the actual refund process and result.
Can I treat a deposit as full payment?
Only if that accurately describes the agreed offer and implemented state model. Keep a deposit, outstanding balance and full settlement distinct.
How do I know an exception is resolved?
The matching records agree, the intended service outcome is confirmed and the client has a clear next step. A sent message alone is not enough.
Sources and further reading
Prepared by Gbeya · Sources reviewed 30 October 2026.