Use this checklist as an authorized manager. Complete only the controls that are available to your organization and role. It is not a promise that every feature, payment method, recipient, report, Wallet balance, or payout is available for every property or environment.

1. Confirm your authorized scope

  • Confirm your signed-in role can manage the intended organization, property, department, outlet, or employee.
  • Verify the active property and environment displayed by Aplauso before making operational changes.
  • Do not make payment or operating changes while a property data-mode transition is in progress; those operations can pause until the transition is verified.

2. Confirm the guest journey

  • Use the currently published guest entry point for the authorized recipient.
  • Confirm the recipient and any applicable property or outlet resolve as expected before sharing or deploying an entry point.
  • Treat payment methods, service charges, room-charge availability, language, and rating prompts as configuration-dependent. Do not promise a method or price that is not displayed in the live flow.

3. Confirm recipient and team readiness

  • Assign people only through controls available to your permitted scope.
  • Give team members the appropriate role and explain the guest flow they will use, without sharing passwords, verification codes, payment data, or tokens.
  • Review recipient, allocation, Wallet, and payout information only in the authorized experience. A profile, balance, or setup screen does not by itself establish payout eligibility.

4. Validate safely before a Live launch

  • Use an approved non-live environment when one is available to your organization.
  • Confirm the property, recipient, and guest entry point resolve to that same environment before testing.
  • Check the recorded result through current authorized controls. A Sandbox or Demo result does not prove a corresponding Live transaction, report, Wallet balance, or bank payout.

5. Launch deliberately

  • Confirm the active Live environment and current operational readiness with an authorized administrator before accepting guest payments.
  • Do not switch environments during an active guest or payment flow.
  • Keep a non-sensitive support path for staff. Report the authorized scope, displayed environment, approximate time, and a non-sensitive error or reference; never send card data, bank data, passwords, codes, or tokens.