How do payments work on ezerve?

The payments design starts from one rule and never bends it: your customers' money is your money. ezerve is not in its path.

Your Stripe account, your money

You connect your own Stripe account (Stripe's standard account type — yours, in your name, under your agreement with Stripe). When a customer pays for a booking, the charge lands directly on your account. You are the merchant of record: the statement descriptor is yours, payouts go to your bank on Stripe's schedule, and refunds and disputes are handled in your own Stripe dashboard, where you have full control.

What ezerve never does

• Never holds, routes, or "settles" customer funds — there is no ezerve balance your money sits in.
• Never takes a percentage of a customer payment, and never adds an application fee on top of one.
• Never deducts platform fees from your payouts. What ezerve charges you appears in exactly one place: your ezerve subscription invoice. See the per-booking meter.

This isn't a pricing choice that could quietly change — it's how the system is built, and the codebase carries automated checks that block any change that would violate it.

Payments are optional

Not connecting Stripe is a supported state, not an error. Bookings, confirmations, and your calendar all work without payments — offerings simply don't collect money online, which suits pay-at-location and free bookings fine. When you do connect, priced offerings start collecting at booking time. Deposits and cancellation fees ride the same rails and are on the roadmap.

Where this is in early access

Payments are rolling out to early-access businesses now. If your account doesn't show the connect flow yet, it's sequencing, not policy — the engine underneath is the one described here.