Skedda makes it really easy to accept and manage online payments for your bookings with Stripe Payments. Stripe is a leading payment processing platform that provides the most reliable and secure infrastructure to manage online payments for your customers. By integrating Stripe with Skedda, you can seamlessly and securely manage online payments with confidence. The venue user card details are securely held within your Stripe payment gateway, whilst the booking details are securely managed on Skedda.

The very first step is to review's Stripe website and product offering, and make sure Stripe is available in your country. You can set up a Stripe account for free, perfect for looking around and testing out their platform! Stripe's pricing differs per country, please check their website for more information.

Online Payments with Skedda is a paid feature, $19 USD per month. 

There are three steps in setting up Online Payments with Skedda

Step 1: Connect your gateway
Step 2: Choose your payments approach
Step 3: Choose if anybody is exempt from your chosen payments approach

Step 1 Connect your gateway

The first step is integrating your Stripe account with Skedda. This is quick and easy, it's just a matter of copying the Stripe API Keys into Skedda. We provide detailed instructions in the next article: Stripe Integration Instructions.

It's very likely that you'll want to test out creating a chargeable booking and managing online payments before you integrate with Stripe. We've created the 'test mode' for a quick evaluation. In the test mode, you can act like a Regular User and attempt to create a chargeable booking with test-card details.

Here are the steps to successfully evaluate Skedda in test mode:

  1. Have a pricing condition set up under the space settings area. If you need some help setting up a pricing condition, review the article 'Creating Pricing Conditions'.
  2. Click into Venue Settings > Online Payments and enable 'test mode'
  3. Look to Step 3 and choose the payment approach you would like to test
  4. If you are set up as a public venue, that takes bookings from anyone, log out and attempt to make a booking. You will see valid-test card numbers to enter, just like a real booking.
  5. If you are set up as a private venue, or a venue that only takes bookings from invited users, then go to the users page and find Skedda Fred (your test user). If the pricing condition you are testing includes a user tag, give Skedda Fred this user tag by clicking on 'edit user'. Now log out and attempt to make a booking. You will see valid-test card numbers to enter, just like a real booking.

If you have any questions whilst in test mode, don't hesitate to reach out!

Step 2 Choose your payment approach

The next step is deciding on the best payments approach for your venue and processes. Let's look at each approach in some more detail.

The Upfront approach

When on the upfront payment approach, your users are charged in the final step of the online booking process. The booking holder's credit card is debited the full booking price. After the booking is complete, the booking is always 'locked-in' and the holder cannot cancel it in a self-service manner online (only an administrator can remove the booking).

You should choose this approach if your organization requires full and immediate payment for the confirmation of a booking, and cancellations are rare (or simply not allowed).

The Book now, Pay later approach (BNPL)

When on the book now, pay later approach, your users are not charged anything immediately to secure a booking online. The booking holder is, however, required to provide a valid credit card to show that they're genuine. Their card details are stored securely in your payment gateway's vault. You and your co-administrators have the ability to charge the credit card for the booking price from the Skedda admin interface.  Alternatively, you could decide to take payment another way, e.g. in cash,  and simply mark the booking as paid.

Note that bookings created with this approach respect your venue's cancellation lock-in margin. For example, if you have a cancellation lock-in margin of 24 hours and a user creates a booking 48 hours in advance, they still have 24 hours to cancel the booking before it is 'locked in'. 

You can only charge their card once the booking is locked in, and you can charge from the day, month and list view. The list view displays a blue charge card, so you can clearly see bookings that are ready to be charged.

This approach is ideal if:

  • You often deal with refunds and/or cancellations
  • You want to make the booking process attractive and frictionless for your users
  • You want to offer alternative payment options to your users (e.g. cash on arrival or customised invoicing)
  • You can want to have card details for a booking as a security measure, even if you don't plan to charge their booking at all

Step 3 Exempt Users

This step allows you to choose if any members of your community should be exempt from the payment approach. They will be able to create bookings without being charged with the Upfront approach, and without adding card details to the booking with the BNPL approach.

Do you need some help with getting Online Payments set up? Take a look over our frequently asked questions and reach out to us with your questions too.

Did this answer your question?