Discount code for a User

If you have found a discount code or have been given one, then now as a Stebby User you can apply it when purchasing a service. When making a purchase, please keep in mind that:

  1. Discounts can be entered one step before the purchase in the checkout view. Once the discount code has been entered, you will see the discount value deducted in the “Ticket price” list.
  2. Discount codes can be used only for pre-purchasable tickets. They cannot be used for on-site purchases.
    1. However, if the Company that you're working for has a special discount rate applied by the Service Provider, then this kind of discount can also be used when performing a purchase on-site or through different API connected cashier systems. This kind of discount applies automatically and doesn't require any discount code to be entered into the system.

      You can purchase services at a discounted rate only through Stebby's website and not through the Stebby app.

      Discounts can only be used when purchasing services from Service Providers. At this stage discounts do not apply for Event Organizers.

      When you get an error message when trying to purchase a service that you know should have an active discount code, then:

    2. The discount code redemption limit might have been reached
    3. The discount code period might have ended
    4. The discount code period might not have started yet
    5. The discount code might have been deleted or deactivated
    6. The discount code you have entered is not existent → Check if you are buying from the correct Service Provider and/or whether the code is typed correctly
    7. In very rare cases it might happen that you have entered a discount code into the system, but at the moment of purchase the system gives you an error message that the discount has become inactive. This is because the discount codes are applied at the moment of purchase, not while they are being entered into the discount code field.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.