Paid meetings add a checkout step between choosing a time and confirmation. Payment collection is a documented requirement on the paid scheduling page; confirm availability before publishing a paid event. The Stripe guide covers what a connection would exchange.
Before you start
- Price, currency, and refund terms.
- A test card for approved, declined, and abandoned attempts.
- Where the transaction record should be reconciled.
How to complete this task
- Connect the payment account and choose price and currency.
- Publish refund and cancellation terms beside the paid event.
- Test approved, declined, abandoned, and duplicated checkout attempts.
- Reconcile the provider transaction with the confirmed booking.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
A payment succeeded but no booking exists.
Never leave this state unresolved. Reconcile the provider transaction against the booking record and either issue the meeting or refund.
A guest disputes a cancellation charge.
Refund and cancellation terms must be visible beside the paid event before checkout, not only in the confirmation email.
Duplicate charges appeared.
Test the double-submit and browser-back cases specifically. Checkout must be idempotent for a single booking attempt.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
