Your account operator is the support contact identified in the portal. Do not use a demonstration business's sample details for a real account.
Start with the symptom
| Problem | First check |
|---|---|
| Missing screen | Business, role in Settings, and enabled capability. |
| Empty list | Dates, source/type filters, search text, and load errors. |
| Missing payment | Terminal Recent activity and Transactions, including amount, time, and masked method. |
| Payment timeout | Treat as uncertain until history or support confirms the result. |
| Deposit mismatch | Source, net amount, deductions, date boundaries, and estimate status. |
| Missing statement | Month, whether it closed, and whether its statement posted. |
| Unavailable button | Capability notice; the demo intentionally blocks external actions. |
| Change not saved | Saved confirmation or error, then reopen to verify. |
For a report error, use Retry where offered or reload. For an action that could already have processed, check its record before retrying.
Prepare a support request
Include business, screen, date/time and timezone, steps, exact error, and transaction, invoice, subscription, or dispute reference. For funding, include payout date and net amount. State expected and actual results.
Use masked digits only. Keep full card and bank numbers, authenticator keys, sign-in codes, and credentials out of messages or screenshots. Redact supporting bank or statement images.
For account-specific permission, fee, deadline, or funding questions, ask the operator to verify the actual account record. A demo example is not your configuration. See payment statuses for handling uncertain results.