Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Deposits on my online bookings fail, vanish or are charged twice

Short answer

Booking deposit problems come from three places: a card hold that expires before it is captured, a payment confirmation that never reaches your booking system, or a retry that charges twice. Card holds are limited by the card network and the time limits are documented. Check the payment dashboard before telling customers anything.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The customer says they paid the deposit but the booking shows unpaid.
  • A booking is confirmed but there is no payment in my payment dashboard.
  • A customer was charged twice for one booking.
  • A held payment was released before I charged the rest.
  • Refunds for cancelled bookings do not match what the system says.

Why does this happen?

  1. A card hold only lasts for a limited time

    Stripe documents that a card authorization held for later capture has a validity window, which depends on the card brand and the type of transaction, and that funds are released and the payment is cancelled if they are not captured in time. A booking made far ahead cannot rely on a hold alone.

  2. Not every payment method can be held

    Stripe lists payment methods that support separate authorisation and capture and others that do not, such as ACH and iDEAL. A booking flow built around a hold fails for a customer who chooses a method without that option.

  3. The confirmation does not reach the booking system

    Payment providers tell your system about a payment through a message sent to a web address, a webhook. If that address returns an error, is behind a redirect or rejects the signature check, the booking stays unpaid while the money has moved.

  4. A retry creates a second charge

    When a request times out and the system sends it again, the provider cannot tell a retry from a new request unless a key is attached. Stripe supports an idempotency key for this, so repeating the same request does not do the operation twice.

  5. Booking and payment are saved in separate steps

    If the booking is saved first and the payment second, a failed payment leaves a confirmed booking. If the order is reversed, a lost booking leaves a paid customer with nothing.

What can I do about it today?

  1. Look in the payment dashboard firstFind the payment by customer email or amount. Whether it is paid, held or failed there is the fact; the booking tool may be behind.
  2. Do not refund or re-charge yetUntil you have seen the payment status, a second charge or a refund can make the situation harder to untangle.
  3. Tell the customer you are checkingA short message that you have received their booking and are confirming the payment keeps them calm.
  4. Save the evidence for each caseKeep the customer's name, time, amount and any error shown, for each affected booking.
  5. List which payment methods your form offersNote whether customers can pick methods that cannot be held, and whether your bookings are made more than a few days ahead.

When should I bring someone in?

  • Several bookings show the same mismatch, which points to the connection, not a one-off.
  • Customers have been charged twice and money has to be returned.
  • The booking system is custom and the payment code was written by someone who has left.

How do I handle it?

  1. Trace one booking end to endI follow a single booking from the form, through the payment provider's log, to the message received by your system, and mark where it broke.
  2. Decide whether a hold or a charge fitsA deposit taken at booking time is usually a real charge. A hold is used only when the time to capture is within the provider's documented window.
  3. Make confirmation messages reliableThe receiving address answers quickly, checks the signature, and processes each event once even if it is sent twice.
  4. Attach a key to every payment requestA retry returns the first result instead of charging again.
  5. Reconcile bookings against paymentsA small check compares booked deposits with provider payments and lists differences, so a gap is seen the same day.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Should a deposit be a hold or a real charge?

Holds expire. Stripe documents validity windows that depend on the card and transaction type, so a booking made weeks ahead normally needs a real charge or a saved payment method.

Why was my customer charged twice?

Most often a retry without an idempotency key, or two booking attempts by an impatient customer. The payment dashboard shows whether both payments were completed.

Can I fix the missing confirmations myself?

Check that the webhook address in the payment dashboard is correct and that recent deliveries show success. Changes in code need a developer.

Are refunds affected?

They can be, if the system does not hear about the refund. Always check the dashboard, not only the booking tool.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.