The guest journey starts at the entry point an organization has published for its intended recipient. The visible language, rating, tip, payment, and service-charge choices depend on that entry point, device, environment, active configuration, and provider availability. Do not promise a fixed QR placement, guest account requirement, amount choice, payment method, or thank-you behavior.
Follow the published recipient journey
The published entry point identifies the canonical recipient: employee, outlet, or department. A guest can submit the rating and tip details the current flow presents. That destination remains canonical if an allocation plan later distributes a tip to eligible beneficiaries.
Before a card payment is created, Aplauso validates the prepared canonical tip, currency, payment amount, and any configured service charge. Payment methods are contextual. Room charge is shown only when the recipient and active kiosk flow can complete its separate authorization; it is not a general PMS or folio-settlement promise.
A payment screen is not final settlement
Aplauso creates a Stripe PaymentIntent using the canonical total and reconciles verified provider events before finalizing a successful tip. A client redirect, processing state, or thank-you screen alone is not proof a payment settled. Failed, canceled, refunded, disputed, and duplicate events follow the recorded payment and adjustment rules.
After a recorded result
The rating and tip retain their canonical recipient. The saved allocation plan determines any eligible beneficiaries; Wallet availability and later payout status remain separate from the guest payment. Do not tell an employee that a guest action guarantees a balance, bank payout, or fixed arrival time.
Protect payment and guest data
Use only the interface currently shown by Aplauso and Stripe. Never provide a card number, password, bank detail, or verification code to an employee, property, or Support. For a payment investigation, provide a non-sensitive reference, property, amount, currency, approximate time, and active environment. Refunds and disputes require authorized handling; do not promise a self-service refund or reversal timetable.