A customer is arranging cat-sitting visits before a weekend away. They reach the payment stage, their bank asks them to approve the transaction, and the process does not complete. They message you: “Has it booked? Do I need to pay again?”
Your team needs a clear way to answer both questions. Handling failed pet-care payments means establishing what happened to the money and what happens to the booking. This guide explains the checks to make, the messages to send and how to assess TailPro’s payment workflow before relying on it.
Check these five things before asking for another payment
- The booking: customer, pet, service dates and booking reference.
- The amount: full charge, deposit or remaining balance.
- The transaction: successful, unsuccessful, awaiting action or still unresolved.
- The booking status: requested, held or confirmed under your actual process.
- The next action: who needs to do what, and by when.
These are practical checks, not a list of TailPro interface labels.
A payment error on the customer’s screen is a reason to check the transaction, not proof that another payment is needed.
1. Establish the payment status first
Find the relevant payment record and compare its amount and reference with the booking. If the result is unclear, investigate through the payment system or support before requesting a fresh payment.
Use a simple decision process:
| What the record shows | What to do next |
|---|---|
| Payment succeeded | Check its allocation to the booking; do not request payment again. |
| Payment failed | Follow the available recovery guidance and explain the next step. |
| Customer authentication is required | Ask the customer to complete the bank’s step through the payment journey. |
| Payment is processing or the outcome is unclear | Resolve the status before starting another attempt. |
Do not guess why a bank declined a payment. A customer may need to contact their card issuer, but your staff do not need to diagnose their bank account.
TailPro’s Income Protection page describes deposits, full payment at booking and payment-status visibility. Use that information alongside the actual transaction outcome when answering a customer.
2. Explain the booking position separately
Tell the customer whether the service is confirmed, awaiting payment or being held temporarily. Do not leave them to infer this from a payment message.
If you hold appointments while a customer resolves payment, define how long you will hold them and who can authorise an exception. Check that your booking system supports the arrangement before promising it.
An unpaid new request is different from an existing confirmed booking with an outstanding balance. Follow the terms already agreed for that booking rather than automatically cancelling it because a later payment attempt fails.
Keep the operational team informed too. Staff preparing tomorrow’s visits need an accurate schedule, not a payment conversation they have never seen.
3. Give the customer one useful next step
Where the payment journey asks for bank authentication, the customer should complete that step themselves. Where it offers a supported alternative card or payment method, they can consider that option.
Only mention options actually available in your setup. Do not promise Apple Pay, Google Pay, bank transfer or another wallet simply because some payment systems support them.
Ask customers to use your established payment journey. Do not ask them to send card numbers, security codes or bank authentication codes in messages.
If the same attempt fails again, review the result before continuing. Repeatedly clicking “pay” is not a recovery process.
Worked example: a £72 cat-sitting booking
Illustrative business scenario — not a customer case study.
A customer requests four cat-care visits at £18 each: 4 × £18 = £72. The business requires full payment before confirming this new request.
The first payment attempt fails after the customer does not complete bank authentication. The business checks that the transaction is unsuccessful and the booking remains unconfirmed.
It then sends this example message:
“The £72 payment for your four cat-care visits did not complete. Your booking is not confirmed yet. Please return to the payment page and follow the bank’s approval step if prompted. If you see a pending or completed £72 payment in your banking app, contact us before trying again so we can check it.”
The customer follows the available payment process and completes payment. The business checks that one successful £72 payment is allocated to the correct booking, then confirms the visits.
“We’ve received your £72 payment and confirmed all four cat-care visits. There is no remaining balance for this booking. Please check your booking confirmation for the visit dates and arrangements.”
The figures are illustrative, not TailPro service prices. The messages are examples, not claims about automatic TailPro notifications.
4. Close the loop after payment succeeds
Before marking the issue resolved, check that:
- The successful amount matches what was due.
- The payment is linked to the correct booking or invoice.
- Any earlier deposit or credit has been accounted for.
- The booking status reflects the agreed outcome.
- The customer has received a clear confirmation.
For example, a £90 booking with a confirmed £30 deposit leaves £60 to collect, not £90. Check the existing payment before requesting the balance.
If two payments appear successful, investigate the records and follow the appropriate correction process. Do not simply delete a booking to make the totals look right.
TailPro’s Help Centre describes customer invoice views with billing details and charge breakdowns, as well as statements showing charges and payment entries. These records help make the outcome easier to explain.
5. Agree how staff handle unresolved cases
Give one person responsibility for each unresolved payment. Record the booking reference, amount, verified status, customer contact and next review time.
If payment cannot be completed, explain the available choices under your booking terms. That may mean another supported payment method, an authorised payment arrangement or ending an unconfirmed request.
Do not promise that a failed payment will recover automatically or that care will proceed regardless of payment status. Where care is already underway, escalate the issue to the responsible manager and maintain appropriate care arrangements while it is resolved.
Check your TailPro workflow before relying on it
Explore TailPro’s payment and deposit tools and ask the team to demonstrate your important scenarios:
- A successful payment and booking confirmation.
- An unsuccessful payment and the customer’s next step.
- An unfinished authentication step or uncertain transaction outcome.
- Payment of a remaining balance after a deposit.
- How staff identify and resolve an exception.
A small business may manage occasional exceptions with a clear checklist. A shared system becomes more useful when several staff handle bookings and customers otherwise receive conflicting answers.
Start with one service and test the supported workflow before changing how existing customers pay. Use a test environment or team-guided demonstration where available rather than deliberately creating failed live charges.
TailPro offers an ongoing Free plan with no monthly software subscription. Applicable transaction and off-app charges remain, and features differ by plan. Check the current pricing details and confirm any alternative-payment requirements.
Frequently asked questions
Does a failed payment cancel the booking?
Not necessarily. Check the booking status and your agreed process. Do not assume that payment failure automatically cancels, preserves or confirms a place.
Should the customer immediately try again?
Only after checking the outcome and following the available guidance. An unresolved or processing payment needs investigation before another attempt.
Can customers pay another way?
Only where that method is supported and accepted by your business. Verify the option and how it will be recorded before offering it.
Can TailPro recover every failed payment?
No recovery outcome can be guaranteed. Confirm the available guidance and controls in your setup; the reviewed supporting pages do not establish automatic retries or guaranteed recovery.
Make the next payment problem easier to resolve
Bring the booking details, payment record and customer explanation together. A useful recovery process ends with everyone knowing what has been paid and whether the service is confirmed.
Start free with TailPro to explore the booking and payment workflow.
Have a particular payment problem to address? Talk to us about your payment process.
