# Payments An event type can ask for payment before a meeting is booked. The invitee picks a time, fills in your booking form and pays on Stripe's checkout page. The meeting is confirmed when Stripe reports the payment. The money goes straight to your organization's own Stripe account: 42min never holds it and adds no fee of its own (Stripe's processing fees apply as usual). Payments need a connected payment provider. An admin connects one for the whole organization; see [Stripe](/help/integrations/stripe). Stripe is the only provider today. PayPal is listed as coming soon. ## Turning it on 1. Open the event type from [Event Types](/360/events) and expand the **Payment** card. 2. Check **Require payment to book**. 3. Enter the **Price** and pick the **Currency**. A new price starts in the default currency of your Stripe account, and you can pick any other currency Stripe supports. 4. Optionally, write **Payment terms** (up to 500 characters). They appear on the booking page and on Stripe's checkout page, so this is the place for a cancellation or refund policy. 5. Save. Each currency has a minimum charge set by Stripe (50 cents in USD, for example), and the price field won't accept less. The highest price is 999,999.99. Taxes aren't added on top: include them in the price. Once saved, the event type's card in the list shows its price. If the organization's Stripe connection is later removed or stops working, the card shows a warning icon reading "Payment provider not connected", and nobody can book that event type until an admin connects again. If the card says "No payment provider is connected", no provider is set up yet. An admin sees a link to [Integrations](/360/integrations?category=payments); everyone else sees "Ask an admin to connect a payment provider." ## Which event types can take payment - **One-on-one** and **round-robin** event types can require payment. - **Group** and **Group + Round Robin** event types can't, so the Payment card isn't shown for them. Switching an event type to a group kind turns payment off. - **Recurring series booked by invitees** and payment don't mix: while one is on, the other is disabled in the editor. - A **managed** event type shows its template's payment settings read-only. Change the price on the template. - You can't open a [Roundtable](/help/roundtables/overview) on a paid event type. Payment is collected on the public booking page only, including team pages, [routing form](/help/routing-forms/destinations) destinations, [single-use links](/help/booking-pages/single-use-links) and [embeds](/help/booking-pages/embedding). A meeting created any other way (through the [API](/help/api/overview), an [AI assistant](/help/ai-assistants/overview), Zapier or n8n, or by a host) is confirmed right away and unpaid. ## What your invitee sees The price appears next to the duration on the booking page, and your payment terms sit above the button, which reads **Continue to Payment**. After they submit the form, 42min sends them to Stripe's checkout. On an embedded page, they first see a short screen with a link that opens the checkout in the full browser window. The time they picked is held for them for 42 minutes while they pay. If the payment doesn't arrive by then, the time is released and other people can book it. That's also why a paid event type never offers a time that starts in less than 45 minutes, even if your [minimum notice](/help/event-types/duration-buffers-and-limits) is shorter. When the payment goes through, they land on the usual confirmation page with a "Paid" line and a link to Stripe's receipt, and the confirmation email carries the amount and the same receipt link. Some payment methods (bank debits, for example) take a while to complete. In that case the page says the payment is being processed, the time stays held for up to three days, and the meeting is confirmed once Stripe reports success. ## Payment and approval together An event type can require both payment and a host's approval. The invitee pays first, and then the request waits for a host to approve it. If the host declines or the request expires, the invitee is refunded in full automatically. ## On the Meetings page On [Meetings](/360/meetings), a paid meeting carries a badge with its amount. Expand the meeting to see the **Payment** block: provider, amount, status, when it was paid, the payer's email when it differs from the invitee's, and a link to the receipt. Bookings that are waiting for payment are listed under [Needs review](/help/workspace/meetings) as "Awaiting payment", with the time the hold expires. They don't count toward the review badge, since nothing is waiting on you. **Release** cancels the request and frees the time right away. ## Refunds The host, a manager of the host's group, or an admin can refund from the meeting's Payment block. **Refund** opens a dialog prefilled with the remaining amount. Lower it for a partial refund. Stripe doesn't return its processing fee on a refund. The invitee gets an email once the refund has gone through. Some refunds happen without anyone clicking: | When | What 42min does | |---|---| | A host or admin cancels a paid meeting | Refunds the remaining amount in full | | A paid request is declined or expires before approval | Refunds in full | | A payment arrives after the held time was released | Refunds in full | | The invitee cancels a paid meeting | Nothing automatic. The invitee is told that refunds are handled by the host, and the host's cancellation email links to the meeting, where Refund is offered | A refund you issue from the Stripe Dashboard shows up on the meeting too. When a payment ends without a meeting (for example, the invitee paid and then canceled the request while it waited for approval), it stays under **Needs review** as "Payment needs attention" until it's refunded. If 42min can't issue the refund itself, usually because the Stripe connection was removed, refund the payment in the Stripe Dashboard and click **Mark as refunded in Stripe** to close the item. That button only records your statement: it doesn't move any money. ## Common pitfalls - **The checkbox won't turn on.** Your organization has no active payment connection, or the event type is set to recurring series booked by invitees. An admin can connect Stripe from [Integrations](/360/integrations?category=payments). - **Times in the next 45 minutes are missing.** That's the payment hold at work; see above. - **The booking page says "This event type cannot be booked right now."** The Stripe connection was removed or broke. Ask an admin to reconnect. - **A price change didn't affect a pending booking.** Each booking keeps the price it was made at. Turning payment off or changing the price applies to new bookings only.