Skip to main content

Stripe

ProEvents Manager Pro - StripeRequires Events Manager Pro. Compare plans

The Stripe add-on adds two gateways to Events Manager Pro. Both charge through your own Stripe account, record refunds and disputes against the booking, and can be used on the same site at the same time.

Before you start
  • Events Manager Pro 3.2.7 or later, and the Events Manager Pro - Stripe plugin installed and activated. Paying from the payment page and taking deposits need Pro 3.10 and Stripe add-on 2.6.0.
  • A Stripe account.
  • A site served over HTTPS. Neither gateway is offered to visitors without it, in test mode as well as live mode.
  • Legacy Mode for gateways switched off. The Stripe gateways don't load in Legacy Mode.

Checkout or Elements​

Stripe CheckoutStripe Elements
Where the customer paysOn a payment page hosted by Stripe. They are sent there after submitting the booking form and brought back afterwards.In a payment form that Stripe draws inside your booking form. They never leave your page.
What the customer sees before payingAn itemized order: each ticket type, surcharges, discounts and tax, with the event's featured image.The booking total on your own booking form.
Payment methodsWhatever your Stripe account has enabled for Checkout.Whatever your Stripe account has enabled, shown by Stripe's Payment Element.
Works as a Quick Pay buttonYesNo
My BookingsAdds a Resume Payment button to unpaid bookingsNo button of its own. Use the payment page for this
Payment page, deposits, Multiple Bookings Mode, admin-made bookingsYesYes
Refunds and disputes recordedYesYes

Choose Stripe Checkout if you want Stripe to handle the whole payment screen and show the customer an itemized order. Choose Stripe Elements if you want the customer to stay on your booking page from start to finish.

If you activate both, visitors see two payment methods. Give them clearly different names in each gateway's Gateway Title setting, because a site that updated from an old version of the add-on can have both titled Pay with Stripe.

What both gateways share​

  • Each gateway has its own settings, its own API keys and its own webhook. Setting up one does not set up the other.
  • Card details go straight from the customer's browser to Stripe. Your site never receives a card number.
  • Payments are captured immediately. Strong Customer Authentication (3D Secure) is handled by Stripe when the customer's bank asks for it.
  • Refunds are made in your Stripe Dashboard, not in WordPress. Stripe then tells your site, and the booking is updated.
  • The charge is made in your Events Manager currency (Events then Settings then Bookings then Pricing Options).