Skip to main content

Save Customer Cards

Get paid faster from repeat customers, powered by Stripe.

Updated over 3 weeks ago

Customers can save their card details after their first payment, so future bookings are quicker. Cards are stored securely through Stripe.

Enable Saved Payment Methods

  1. Go to Payments > Stripe and connect your Stripe account.

  2. Enable Booking Page payments.

  3. Go to Settings > Booking Page > Booking preferences > Booking flow.

  4. Tick the box next to Customer login.

Note: Customers can only save card details when logging in with Google or Facebook. This feature isn't available for email login or guest checkout.

How It Works for Customers

  1. The customer enters their card details as normal at checkout.

  2. They tick Save payment details for future purchases.

  3. Next time they book using the same login, they'll see their saved card ready to go.

  4. They can save multiple cards and switch between them. To edit or remove a card, they click the three dots beside it, pencil icon to edit, trash icon to delete.


FAQs

Can customers remove a saved card? Yes, saved cards can be removed during the payment stage of any booking.

Is this a paid feature? No, this feature is available on every ServiceForge plan.

Can customers use different cards for different jobs? Yes. They can save as many cards as they like and choose which one to use at each booking.

Does this work for classes? Yes, saved cards work for both services and classes, as long as Stripe is connected.

Where are card details stored and how secure is it? Card details are stored by Stripe, our payment partner. Stripe is PCI-compliant, the highest industry security standard. Only the last four digits of a card are ever visible, even in the Stripe dashboard. ServiceForge does not store full card details.

Who can see a customer's saved card? Only the customer, when logged into the same account they used to save it. You can view limited transaction details in your Stripe dashboard, but not through ServiceForge.

Did this answer your question?