01 · Entry
Code entry
Verify the code communicated to the customer. The field normalizes the entry to uppercase, but the text must still match the expected code.
A code may be rejected because it is invalid, inactive, expired, or not eligible for the context. Final validation remains server-side.
The code field can be opened on request. Entered text is normalized to uppercase. In the documented journey, the code is then verified server-side and the interface displays a success or error message. The summary and total are recalculated only when the benefit is accepted.
It indicates that the code cannot be applied in the verified context. It does not automatically mean the rest of the booking is invalid.
Start with the confirmed general conditions. They help distinguish an entry error from a benefit that does not match the configured package or threshold.
A referral program may, for example, verify its validity period, package, duplicates, self-referrals, or a configured cap. These conditions must not be generalized to every promo code.
The code field, referral programs, and credits already recorded in the account do not represent the same mechanism.
The summary and total are recalculated after the benefit is accepted server-side.
The amount remains unchanged and the interface displays an error message. In applicable journeys, a code may also be removed before confirmation if the booking choices change and no longer meet the applicable conditions.
To facilitate diagnosis, prepare the following information before contacting the technical support team.
Contact supportYour response helps identify articles that still need clarification.