Stripe
Connecting Stripe lets your hosts charge for meetings. Once an admin connects the organization's Stripe account, any host can turn on Require payment to book on an event type, and invitees pay on Stripe's checkout page before the meeting is confirmed. Payments land directly in your Stripe account. 42min adds no fee; Stripe's own processing fees apply.
What it does
- One account for the organization. The connection belongs to the organization, not to a person, so every host's paid event types charge through the same Stripe account. A Stripe account can be connected to one 42min organization at a time.
- Stripe's hosted checkout. Invitees pay on a page served by Stripe, carrying your Stripe account's branding and the payment methods you enabled in your Stripe Dashboard. No card details pass through 42min.
- Refunds both ways. A refund issued from a meeting in 42min goes out through Stripe, and a refund you make in the Stripe Dashboard shows up on the meeting.
- Receipts. The invitee's confirmation email always carries the amount and a link to Stripe's receipt, whatever your Stripe email settings are.
Connecting Stripe
Only an admin or the owner can connect Stripe. Other users see the Stripe tile dimmed with "Ask an admin to connect it."
- Open Integrations and pick the Payments filter.
- Click the Stripe tile. Stripe opens and asks you to sign in.
- Choose the Stripe account to connect (or create one) and approve the connection.
- You come back to Integrations with "Stripe connected. Hosts can now require payment on their event types." Stripe now sits in the connected list at the top of the page.
If Stripe still needs details from you before the account can take charges (identity or bank details, for example), the Stripe row shows Continue setup. Click it to finish in Stripe. Hosts can turn payment on in the meantime, but Stripe won't take an invitee's payment until it enables charges on the account.
If the connection fails, the page says why: the Stripe account is already connected to another workspace, the connection was canceled at Stripe, or the link expired (start again from Integrations).
The Stripe page
Click Settings on the Stripe row to open the Stripe page. It shows:
- the Account name and Account ID;
- the account's Country and Default currency (new prices on event types start in this currency);
- Charges: "Enabled", or a note to finish the setup in your Stripe Dashboard, with a Continue setup button;
- who connected the account and when, and how many event types require payment.
A Test mode label next to the heading means the connected account is in Stripe's test mode: checkouts take Stripe's test cards and no real money moves.
If the connection stops working (for example, someone removed 42min's access from the Stripe side), the page says so and offers Reconnect. Until it's fixed, paid event types can't be booked.
Disconnecting
Click Disconnect on the Stripe page and confirm. If any event types require payment, the dialog warns that they can't be booked until you connect again.
Disconnecting doesn't change your event types: their prices stay, and they become bookable again as soon as Stripe is reconnected. Any booking that's still waiting for payment is released. Payments already taken keep their status and receipt on the meeting, but 42min can't refund them while Stripe is disconnected: refund them in the Stripe Dashboard instead, then use Mark as refunded in Stripe if 42min lists the payment as needing attention. See Refunds.
Common pitfalls
- Connected, but invitees can't pay. Check Charges on the Stripe page. Until Stripe enables them, finish the setup with Continue setup.
- "This Stripe account is already connected to another workspace." One Stripe account serves one 42min organization. Disconnect it there first, or connect a different account.
- The invitee didn't get a Stripe receipt email. Stripe sends its own receipt only when your account has receipt emails turned on, and never in test mode. The 42min confirmation email links to the receipt either way.
Last updated October 15, 2026.