Skip to main content
All CollectionsTrip Organizer's GuideManaging a Trip
How to Stop Automatic Payments for Travelers
How to Stop Automatic Payments for Travelers

You now have the option to stop automatic payments for specific travelers. This document explains how you can do that.

Updated over a month ago

You can now stop automatic payments for specific travelers, giving you enhanced control and flexibility in managing traveler payments. This article will demonstrate how to stop automatic payments for a traveler and explain how it works.


Where can we find the option to stop automatic payments?

The option to stop automatic payments is located in the company stats section in the booking details of the traveler.


How to stop one automatic payment?

Example explained:

  1. Open "Company Stats".

  2. Find the traveler that you wish to stop the payment for.

  3. Open the Booking details for that traveler.

  4. Select the "Payment Details" option on the right side.

  5. On the Payment Details page as part of the payment option plan we have a "Stop Auto Payment" button.

  6. When we click on this button we are prompted to confirm our command.

  7. After we have confirmed it, payment has been paused/stopped.


How to stop all automatic payments?

Example explained:

  1. Open "Company Stats".

  2. Find the traveler that you wish to stop the payment for.

  3. Open the Booking details for that traveler.

  4. Select the "Payment Details" option on the right side.

  5. On the Payment Details page as part of the payment option plan we have a "Stop all Auto Payments" button.

  6. When we click on this button we are prompted to confirm our command.

  7. After we have confirmed it, payments have been paused/stopped.

☝️ Note: After we have stopped one or more payments, travelers will receive an e-mail notifying them that the change has been made.
​


Have questions? We have answers! 😊

Email us at [email protected] or send us a message via chat.

Have a feature request that would make your life easier? Share it with us on our public feature request board.
​

Did this answer your question?