Tell us what is wrong and our support team will reply by email. Many answers
are already in Troubleshooting , and the
service status page shows whether
CardOffice itself has a problem.
Thank you. Our support team has your request and will reply by email to
Subject
To add anything, such as another screenshot, reply to our email so it all stays on one ticket.
Report a different problem This form needs JavaScript. You can email support@cardoffice.nz instead.
One problem to a ticket , summed up in a few words.What you were doing and what you saw , with the exact message on screen.
A screenshot is often the quickest way to show it.The record involved , if there is one: an order number, a card serial
number, or a card holder’s ID number.For an integration , the endpoint, the time, the HTTP status and the
code from the error body. For a webhook, the X-IDPortal-Delivery value of
the delivery that went wrong. The error codes page explains
each code. Photos of people, passwords, API keys, webhook signing secrets, or lists of
people’s personal details. Support can see what it needs in CardOffice.
If you think an API key or a webhook secret has been exposed, revoke it
first in Settings → Integrations , then tell us. See
Building a secure integration .
Files go to our help desk with your message and are not kept anywhere else.
Images, PDFs, Word, Excel and PowerPoint files without macros, and plain text
files can be attached, because our staff open them. Anything else is refused.
To report a vulnerability, use the address in
security.txt rather than
this form, and please do not test against other organisations’ data. See
how CardOffice protects your data .
