Your employee needs to know when a customer has paid. They do not need your wallet recovery phrase to hear a confirmed amount or keep a payment QR visible.
That distinction matters at a small shop. An owner may control the receiving wallet, while staff handle orders, packaging and handover. A payment display lets those jobs stay separate without turning the counter tablet into the owner's wallet device.
AI-generated concept illustration, not a PayIn screenshot or real payment. The scan pattern is nonfunctional. Separate devices illustrate responsibilities, not named staff accounts or a role-management feature.
Give each person the access their task requires
A wallet controls the funds and signs outgoing transfers. The PayIn management link opens the receiving setup and payment records. The POS link opens a customer-facing display with payment feedback. These are different access surfaces.
| Surface | Who needs it | What to protect |
|---|---|---|
| Public payment link or its QR | Customers | Check the title and intended destination before sharing |
| POS display link | Counter devices used by staff | Keep it off public signs; it exposes payment events |
| Private management link | Owner or a trusted operator | It gives access to records and settings; save it privately |
| Receiving wallet and recovery material | People authorized to control funds | Keep signing keys and recovery words away from counter devices |
This is a division of responsibilities, not a claim that PayIn supplies named employee accounts, per-person permissions or a staff audit log. Currently, creating and using the service does not require merchant registration.
Set up the counter without installing the receiving wallet there
The owner creates the receiving setup with the public wallet address, saves the private management link and opens the Links section. Staff use the separate POS display link on the counter tablet. Customers scan the public payment QR and approve the supported flow on their own phones.
The tablet does not need the merchant's signing keys. Place its screen toward customers and activate audio on that device before service. Use a screen lock and normal device controls when the counter is unattended.
If staff need only the public request for an online customer, share the public payment link instead. Do not send a management URL in a customer message or encode a POS access URL in a printed payment QR.
Let staff notice receipts while doing the sale
A newly confirmed payment can show its amount and trigger sound on an enabled, connected display. That helps an employee packing an order without repeatedly opening the merchant wallet.
Audio still needs a working device and a visible browser. Use the current display's controls to enable and test it. A test sound does not create a payment; a signature on the customer's phone does not establish receipt.
Match the new amount to the sale. When two customers owe the same total, preserve a reference and ask the trusted operator to inspect management if the match is uncertain. Give staff a clear escalation route rather than requiring the owner to hand over wallet credentials.
The POS setup guide shows the actual interface, and the busy-counter guide explains the handover routine.
Prepare for shift changes and exposed links
Keep a private record of which counter devices use the POS link. When access is no longer appropriate, use management's POS-link reset and distribute the replacement to the devices that should continue. Resetting it means all displays using the old POS link need the new one; the public customer link and management link remain separate.
Do not confuse that with replacing a management link. Management access has its own replacement flow, and losing its saved key can prevent recovery. Keep a private backup under the owner's control.
A device can store access locally even if its screen is closed. Follow the device's shift-end/access controls and your business's device policy; simply walking away from an unlocked tablet is not an access-control process.
Decide who handles exceptions and refunds
Write down who staff contact when the display is offline, an amount differs or a buyer says they paid manually. For an already submitted transaction, check the original operation before asking for another payment.
Refunds are separate authorized transfers, not something a cashier should improvise from a customer-facing display. Verify the original receipt, recipient and network through your own refund procedure. Pausing a link or changing a sale record does not reverse a transfer.
The practical benefit is a counter device that supports the sale while the owner's wallet stays separate. Explore the USDC POS display and decide how your team will escalate unclear receipts before opening.