Contacting PayCanvas Support

Send a useful, privacy-safe support request and know what information to include or leave out.

Contact options

Current boundary — review required: The help icon in the payroll workspace does not currently open an in-app support workflow. Use email or the public setup-review form.

Prerequisites

Collect only privacy-safe context:

  • account or tenant name;
  • payroll period dates;
  • page or workflow step;
  • safe error code or audit/reference hash;
  • approximate timestamp and timezone;
  • whether the issue is repeatable;
  • MCP client name, if applicable.

Send a support request

  1. Use a subject such as Source collection failed — Aug 1–14 — Acme Tours.
  2. Describe what you expected and what happened.
  3. Include the safe context above.
  4. State whether you already retried and which offered action you used.
  5. For access issues, include the affected user's email and intended tenant role.
  6. For suspected security or cross-tenant exposure, put Security in the subject and stop interacting with the affected data.

Do not send

  • passwords, MFA codes, access tokens, authorization codes, API keys, or provider credentials;
  • full payroll reports or provider payloads;
  • customer or employee personal information;
  • private employee mappings or compensation details;
  • screenshots that show identifiable payroll amounts unless support provides an approved secure transfer path.

Redact screenshots and files before attaching them. Prefer a safe reference code over a raw record.

Expected result

The public form confirms receipt and says follow-up will come from hello@paycanvas.io. Email requests provide support enough safe context to locate the tenant-scoped audit or job evidence without asking you to expose source data.

No response-time or resolution-time SLA is currently published in the product. Do not delay an internal payroll contingency solely because a support request was sent.

Troubleshooting

  • Public form fails: email hello@paycanvas.io and include the form error without resubmitting sensitive content.
  • You received a request for a password or token: do not provide it; start a new email to hello@paycanvas.io to verify the request.
  • Immediate MCP revocation is needed: disconnect locally, then ask support to revoke the server-side operator grant. Include the client name and connection time, never the token.
  • Payroll deadline is near: follow your organization's approved downstream payroll contingency while PayCanvas investigates; PayCanvas does not submit or pay payroll.
SOLVING THIS WITH CHATGPT?

Share this article URL and describe what happened.

Include the step you are on, what you expected, and a safe error code. Do not share employee pay, raw reports, credentials, MFA codes, or access tokens.