Salons, gyms, classes & shops
A deposit reduces no-shows at the busiest hours. A cancellation rule is stated as somebody books, rather than discovered afterwards.
The payment link goes out during the conversation, and its real status is tracked to the end — paid, pending, or nothing at all.
7 days, 20 answered calls, no card
A deposit asked for during the conversation gets paid; one asked for the next day does not. It is that simple, and it separates a confirmed booking from a slot held for nothing.
This add-on creates the payment request at your provider, sends the link to the person, and tracks the real status of that payment rather than the hope it went through. A file changes state once money arrives, not once a link was sent.
It decides nothing on your behalf. Cancellation, refund and exception rules stay yours: the conversation applies them where they are clear, and passes the situation to whoever is responsible where they are not. Refunding is no automatic act.
The payment request is created at your payment provider, on the amount your rules set for that service. The conversation sets no price that is not in your price list.
The link goes out on the channel where somebody already is. A deposit sent later is a deposit to chase, which is exactly what this avoids.
Status comes from the provider. Until the payment is confirmed, the file says so, and a retry creates no second payment request.
Once payment arrives, follow-up stops and the file moves on. Where it does not arrive, whichever rule you set decides what happens to the booking.
The add-on covers your business’s payments. It creates the payment request at your provider and tracks its status until the money arrives, for the files you authorised.
It replaces neither accepting an estimate nor authorising a repair. A connected store order and a restaurant order already carry their own payment: in those cases this add-on is not needed.
A deposit reduces no-shows at the busiest hours. A cancellation rule is stated as somebody books, rather than discovered afterwards.
Groups and events confirm with a deposit. A held date stops being a verbal promise, and a room knows what is genuinely booked.
A materials deposit ahead of ordering is common. The amount comes from whatever you defined for that type of work, and the trace stays on the customer file.
A specially ordered part gets paid up front in many shops. The payment request is attached to whichever repair order it belongs to.
A refund, an exception and an out-of-rule cancellation are your decisions. A payment request does not turn into permission to refund.
The add-on carries its own monthly volume of payment requests, which you follow in your app.
Your contract with your payment provider stays yours, at its own rates.
The merchant account stays yours, and the money reaches you. The connection is authorised from your account at the provider.
No. The merchant account stays yours and the money reaches you, under your contract with your payment provider.
No. The file changes state once money arrives. Status comes from the provider; until the payment is confirmed, the file says so, and a retry creates no second payment request.
No. A refund, an exception and an out-of-rule cancellation are your decisions: a payment request does not turn into permission to refund.
Not for those orders: a connected store order and a restaurant order already carry their own payment, and this add-on is not needed in those cases. It serves any other billing.
From your rules for that service. The conversation sets no price that is not in your price list, and the request is created at your provider on that amount.
What comes ahead of payment, or a full store order.
Deposits and payments