Customers, balance, reviews, and tickets
Buyer records, store credit, feedback, and support.
Open Audience → Customers for buyer records, notes, security reset actions, balance adjustments, exports, and customer details.
The customer detail page can suspend or restore an account. Closing an account revokes access and anonymises optional profile data; invoice, tax, fraud and chargeback evidence is retained for seven years. A buyer can opt into a cross-store purchase summary from Your account → Security. The merchant sees only stores where matching verified customer records also consented.
Use the search box on the customer list for an invoice reference, buyer email or exact serial. Serial search uses the stored blind index and returns no partial matches.
Customer balance is ledger-backed store credit. Adjustments require the right permission and are scoped to the store and mode.
Open Audience → Feedback for reviews and ratings. Buyer-facing feedback routes are public where appropriate, while merchant moderation and settings require store access.
Automatic reviews are on by default, as on SellAuth. A delivered live order with no review, refund, dispute or open ticket gets a 5-star review labelled Automatic after the delay you set in Feedback settings (1–30 days, default 7). It earns no reward coupon. If the buyer writes their own review later, it replaces the automatic one. Filter the list by Kind → Automatic and use Delete automatic to remove them; a deleted automatic review is not created again.
Open Audience → Tickets for support conversations. Tickets can be tied to invoices and include attachments where enabled.
A signed-in buyer can create a 15-minute order verification code. Staff enter it with the invoice reference on the ticket list. Ticket rows can be selected for one idempotent bulk close, reopen or archive action. A linked ticket shows invoice payment and delivery state plus controls to resend the receipt or retry a failed delivery.
Buyers can open Your account → Files for file entitlements from paid invoices. Each click creates a fresh, short-lived grant for the exact entitled version.
Buyer API tokens
A signed-in buyer can create API tokens under Your account → Security → API tokens to reach their own account from a script. The token (ct_…) is shown once, works on that store only, and is sent as Authorization: Bearer ct_… to the account endpoints, for example GET /v1/public/stores/{storeId}/account/orders. A buyer can hold up to 10 tokens and revoke any of them; a revoked token stops working at once. Tokens cannot create more tokens or change the password or two-factor settings; those need the browser login.
Balance currency
Credit and top-ups use the store currency. Older balances in other currencies appear separately and are never added together. Credit can pay only an invoice in the same currency. A buyer who chooses another display currency sees an approximate value of the primary balance; this does not exchange their credit. Test transactions stay out of live balance statements.
Cashback expiry waits for an open credit reservation to settle or release, then checks the unused reward again. Cancelling a checkout does not extend the reward’s expiry.