A QR code is one way to open a published Aplauso guest entry point. Its destination, availability, language, rating, tip, payment, and service-charge options are determined by the current recipient, environment, configuration, device, and provider availability. A QR image or link does not itself authorize a charge, guarantee a payment method, create an allocation, or establish Wallet or payout readiness.

Use only an authorized, currently available entry point

An authorized business operator or recipient can use the QR or link controls currently visible to their permitted scope. Confirm the displayed recipient, property when applicable, and active environment before sharing, printing, or installing an entry point. Do not promise a fixed path, file format, template, download option, resolution, or self-service management control from this guide.

If a code or link is unavailable, do not invent a destination format. Ask an authorized administrator to confirm the intended recipient and supported distribution method.

Validate before distribution

Scan or open the intended code through an ordinary guest browser context and confirm that the displayed recipient and environment are the expected ones. Use only an approved non-live test flow when your organization has access to one. Do not use real customer data, payment data, bank data, passwords, verification codes, or tokens for validation.

Do not use a redirect or thank-you screen alone as final payment confirmation. When a controlled non-live result is recorded, review it through the authorized controls in the same environment. A Sandbox or Demo result does not prove a corresponding Live entry point, payment, report, Wallet balance, or payout.

Deploy responsibly

Place a guest entry point only where the organization is authorized to invite guest use and can keep the recipient context accurate. Recheck a printed or digital placement after operational changes to the recipient or environment. Do not claim that a department, outlet, employee, or kiosk has a particular QR type, payment method, allocation rule, or immediate update unless the current published flow shows it.

Get help safely

For a QR or guest-link issue, share the authorized recipient or property, displayed environment, approximate time, and a non-sensitive error or reference. Do not send a payment detail, bank detail, password, verification code, token, or any private guest data.