Plans, subscriptions, seats and the Stripe side of an account.
Find your code below — there are 13 of them. The digit between the letters and the dash says who can act on it: 1 is something you can change, 2 and 9 are Quavern's to fix, 3, 4 and 5 are decisions about access, 6 and 7 mean the service is in maintenance or has moved, and 8 points at the device or the network. STRP uses 1, 2, 3. The shape of a code is explained in How to read a Quavern support code.
Class 1 — Your request or your action
Check what you sent and the state of the account: the request itself, a quota, or the object it names. Correcting that and trying again is normally the whole fix.
STRP1-1001 — invalid_plan
What it means. The plan named is not one Quavern recognises.
What to do. Use one of the values the documentation lists.
STRP1-1002 — minimum_seats
What it means. Quavern has not published what this code means. Its name does not settle it, and this page will not guess — the slug names a quantity, not a failure: it does not say whether the request asked for fewer seats than the minimum, or something else.
What to do. Quote the code to support at [email protected], with the time and what you were doing, and you will be told what it means.
STRP1-1402 — card_verification_required
Retired. Nothing raises this any more. It stays published because a code is never recycled and never changes meaning: a ticket quoting it from before it was withdrawn still resolves to what it meant then.
What it means. The request cannot go ahead without the card check.
*From the registry:* Retired: the free Stripe card check (docs/ACCOUNT_ACCESS.md §7) Removed on 2026-09-18 when a verified telephone number replaced the card authorisation. Nothing raises these any more. They stay listed because a code is never recycled and never changes meaning after publication (docs/ERROR_CODE_POLICY.md, stability rule 4): a support ticket quoting STRP1-1402 from last month must still resolve to what it meant then.
STRP1-1403 — contact_sales_required
What it means. The request cannot go ahead without an agreement made with Quavern sales.
STRP1-1409 — billing_account_missing
What it means. The billing account behind this one does not exist yet, and Quavern needs it before it can go any further.
STRP1-2402 — card_verification_failed
Retired. Nothing raises this any more. It stays published because a code is never recycled and never changes meaning: a ticket quoting it from before it was withdrawn still resolves to what it meant then.
What it means. The card check did not pass. Quavern refused the request before anything changed.
*From the registry:* Retired: the free Stripe card check (docs/ACCOUNT_ACCESS.md §7) Removed on 2026-09-18 when a verified telephone number replaced the card authorisation. Nothing raises these any more. They stay listed because a code is never recycled and never changes meaning after publication (docs/ERROR_CODE_POLICY.md, stability rule 4): a support ticket quoting STRP1-1402 from last month must still resolve to what it meant then.
STRP1-2409 — subscription_exists
What it means. The subscription is already in the state the request asked for, so Quavern did nothing rather than do it twice.
What to do. Nothing is broken. Read the current state before repeating the step.
STRP1-3409 — card_already_verified
Retired. Nothing raises this any more. It stays published because a code is never recycled and never changes meaning: a ticket quoting it from before it was withdrawn still resolves to what it meant then.
What it means. The payment card check is already in the state the request asked for, so Quavern did nothing rather than do it twice.
What to do. Nothing is broken. Read the current state before repeating the step.
*From the registry:* Retired: the free Stripe card check (docs/ACCOUNT_ACCESS.md §7) Removed on 2026-09-18 when a verified telephone number replaced the card authorisation. Nothing raises these any more. They stay listed because a code is never recycled and never changes meaning after publication (docs/ERROR_CODE_POLICY.md, stability rule 4): a support ticket quoting STRP1-1402 from last month must still resolve to what it meant then.
STRP1-4404 — invalid_card_ticket
Retired. Nothing raises this any more. It stays published because a code is never recycled and never changes meaning: a ticket quoting it from before it was withdrawn still resolves to what it meant then.
What it means. Quavern refused the card-check ticket: the value received is not in the expected form, or it is not one Quavern issued.
What to do. Send the value exactly as it was given to you, with nothing added, trimmed or re-encoded.
*From the registry:* Retired: the free Stripe card check (docs/ACCOUNT_ACCESS.md §7) Removed on 2026-09-18 when a verified telephone number replaced the card authorisation. Nothing raises these any more. They stay listed because a code is never recycled and never changes meaning after publication (docs/ERROR_CODE_POLICY.md, stability rule 4): a support ticket quoting STRP1-1402 from last month must still resolve to what it meant then.
Class 2 — Quavern's server or one of its dependencies
Nothing you did caused it. Wait a moment and try again. If it keeps happening, send support the code and the time — that is what lets the incident be found in the logs.
STRP2-1502 — billing_error
What it means. The billing system failed. The failure is on Quavern's side, not in what you sent.
STRP2-1503 — billing_unavailable
What it means. The billing system did not answer, and this route cannot be served without it.
STRP2-2500 — webhook_processing_failed
What it means. Processing of the Stripe webhook failed. The failure is on Quavern's side, not in what you sent.
Class 3 — Authentication, authorisation or security
Sign in again, or ask whoever administers your organisation for the access this needs. Support will never work around an access control on your behalf.
STRP3-1400 — invalid_webhook_signature
What it means. Quavern refused the Stripe webhook signature: what arrived is not in the form this route accepts.
Still stuck
Write to [email protected] with the code, the reason, the time with its time zone, and the route you called. Never send a password, a token, an API key or full card details — support will never ask for any of them.
Quavern help reference: support-codes-strp/en