BookPro Stripe lets your BookPro booking site take card payments through Stripe. A customer chooses an appointment, moves on to checkout and enters card details on your own site. When the payment succeeds, the booking is confirmed automatically, so you are not checking each payment by hand. The add-on suits businesses that want payment built into the booking journey itself, rather than arranged as a separate step once the appointment has been made.

How a card payment moves through a booking

Payment happens inside the booking process on your own site. Behind the scenes, the add-on uses Stripe’s PaymentIntents interface, which Stripe designs for payments that may need extra steps. Where a customer’s bank requires strong customer authentication under European rules, or a 3D Secure check, the add-on applies that step as needed, so the verification screen appears only when the bank asks for it.

Once a payment succeeds, the booking is confirmed without any manual step on your part. Failed and pending payments deserve more attention, because the experience a customer has in those moments shapes how they view your business, even when everything else has gone smoothly. Test those cases yourself in test mode before you take real payments, so you know exactly what a customer will see.

What you need before installing

BookPro must be installed and active, because the add-on works on top of it.
Your server should run PHP 7.x or 8.x, and the vendor suggests PHP 8.1.
Your WordPress version should fall within the range the vendor lists, which runs from 6.7 through 7.0.
You need a Stripe account, with test keys for trial bookings and live keys for real ones.

Installing the add-on

Install and activate BookPro first, because the payment add-on depends on it. Then open the Plugins screen in your WordPress dashboard, choose Add New Plugin, use the upload option to select the add-on’s archive and complete the upload. Activate the add-on once the upload finishes, and check that your booking pages still load normally. If an error appears after activation, deactivate the add-on, look for the cause and try again before you accept any payments.

Connecting Stripe and running a test booking

Add your Stripe test keys first. The vendor confirms that you can run a full checkout with test credentials before switching to live keys, and that is the sensible order. Make a test booking from start to finish, use the test card numbers that Stripe publishes for different outcomes, and confirm that the booking is confirmed once the payment succeeds. Then find the same payment in your Stripe dashboard so you can see how the two records line up.

When the test run behaves as expected, replace the test keys with your live keys and make one small real booking to check the final setup. Store both sets of keys securely, so you can repeat the test later if something needs troubleshooting.

Troubleshooting a payment that does not complete

Failed test payments often trace back to a few common causes. One frequent cause is a mismatch between test and live keys, where a live key is paired with test-mode settings or the reverse. Check that both halves of the configuration belong to the same mode before you look anywhere else.

Next, confirm that BookPro and the add-on are both active, and that the booking page is served over HTTPS. If the problem appears only in one language, check the translated checkout pages as well, since a missing translation can make a working step look broken. Keep a note of the time, the appointment date and the customer’s name for each failed attempt, because that record makes it much easier to match a problem to a log entry in Stripe.

Choosing currencies

The add-on follows the currency settings that BookPro already uses. The add-on material does not list individual currencies, so check two things before launch: that the currency you need is available in BookPro, and that your Stripe account can accept charges in that currency. If you serve customers in more than one currency, test a booking in each one before you advertise the service.

Reconciling payments with bookings

A payment record and a booking record are only useful together. Set a regular routine, perhaps weekly, to compare the bookings marked as confirmed with the successful payments in your Stripe dashboard. Any booking without a matching payment, or any payment without a matching booking, deserves a quick look. Catching those gaps early keeps your books tidy and prevents an awkward conversation with a customer later.

Keeping keys and access secure

Treat your Stripe keys as passwords. Never paste them into a public forum, a shared document or a code repository, and limit access to the WordPress dashboard to people who genuinely need it. If you suspect a key has been exposed, rotate it in Stripe and replace the old key in the add-on’s settings straight away. Where team members only need to view payments, give them a restricted level of access rather than full control of the account.

Languages and layout

BookPro Stripe is set up for translation and is compatible with WPML and Polylang. It also includes right-to-left layouts. Before you launch a multilingual site, walk through checkout in each language, because button labels, field captions and confirmation messages are the words visitors read most carefully when they are about to pay.

Notes for developers

The code is namespaced and offers hooks and filters. Developers who want to adjust the checkout experience or the messages attached to payments can do so without changing the add-on’s own files. Keep those changes in a companion plugin so they remain separate from the add-on.

Before you go live

Serve every booking page over HTTPS, because card details should never travel over an unencrypted connection. Confirm on the Plugins screen that both BookPro and the add-on are active. If you plan to offer refunds, check in test mode how a refunded booking appears on the site, and decide in advance who issues refunds and where each one is recorded, so that nobody is guessing when a customer asks.

Testing different card outcomes

A successful payment is only one of several outcomes your site must handle. Stripe provides test card numbers that simulate a declined card, a card that needs additional authentication and other situations customers encounter. Work through several of these during your trial period, and note exactly what the booking page shows and whether the booking stays open, becomes confirmed or is cancelled in each case. Those notes become your reference when a real customer asks what happened to their payment.

Writing clear messages around payment

A payment step is where a visitor is most likely to hesitate, so the words around it matter. Tell customers plainly what they are about to pay for, which appointment it covers and when they can expect confirmation. If a payment fails, say what the customer can do next, such as checking the card details or trying a different card, rather than leaving them with an unexplained error. Short, direct sentences reduce anxiety and cut down the number of abandoned bookings you have to chase later.

Keeping a payment checklist for your team

Several people may touch a payment configuration over the life of a site, so a short written checklist helps. List the keys, the mode each key belongs to, the date they were last changed and the person responsible for them. Add a line for each test you ran and its result. When a new team member takes over, the checklist shows what has been done and what still needs attention, which avoids repeated work and missed steps.

Who this suits

Businesses that take bookings for appointments, classes or services, and want payment to happen during the booking rather than afterwards, will find the add-on most useful. It also suits agencies that set up payment flows for clients, because test mode and WPML and Polylang compatibility make it simpler to hand over a site that is ready to trade.

BookPro Stripe connects a booking site with a card payment provider inside one continuous journey. Test it thoroughly, keep your keys private, and the path from choosing a time to a confirmed booking can stay short and reassuring for the customer.