Skip to content

Contact us

We’re here to help

Paycux is reached by email. There is no contact form and no support channel inside the console; write to the address that fits and a person answers in business hours.

Request a demo

Talk to sales

Ask what exists today, what is planned, and which workspace plan fits your product. We answer in writing and say plainly when something is not built.

[email protected]

Request support

Open a support request

Workspace owners reach the support team by email. Send the workspace slug, project, environment, connection or request and a timestamp — never include an API key or secret.

[email protected]

Report a vulnerability

Contact security

Found a security issue? Write to the security team with reproducible details and follow the responsible disclosure guidance.

[email protected]

Write to us

Tell us what you are building

A couple of sentences about your app, which provider you use and what you want the control plane to do is enough. We answer in business hours, in writing, from a human.

What to include

  • Sales and product questions — [email protected]. Your provider (Stripe or Paddle), roughly how you sell today, and the question you need answered before you build.
  • Help with a beta workspace — [email protected]. Workspace slug, project and environment, the request or connection involved and a timestamp. Never send API keys or webhook secrets by email.
  • Vulnerabilities — [email protected], following the responsible disclosure guidelines.

There is no web form or in-console support channel. Email is the support route; do not include API keys, webhook secrets or payment details.

For more information

Answers you can read right now

What exists today

The implemented API contracts: identities, dashboard routes, end-user routes and error codes.

Plans and pricing

Compare the published Starter, Growth and Scale workspace limits and billing periods.

Changelog

What changed in the product and when.

Reporting a security issue?

Do not open a normal support ticket. Write to [email protected] and read the responsible disclosure guidelines first — they explain what to include and what happens next.

Or skip the conversation and start building

Create a workspace, connect a provider, and write to us when you hit something worth talking about.