Waiting on a decision, not on writing time
What is missing before this page can be written
- Missing
- The confirmed statement descriptors for every payment route, the billing cycle facts, and what a customer is told when a payment fails.
- Who can answer it
- Business or policy owner via Ivo, plus the billing/backend answer in AR-005
- Recorded as
- AR-005 · AR-017 decision 2 · manifest v3 gap register
- Planned release
- Wave 3, target 2027-01-31
Nothing on this page is invented. The structure, the customer questions, and the routes are real; the answers stay blank until the owner above supplies the fact.
The questions this page has to answer
Taken from the FAQ export and the gap register. The questions are known; the approved answers are what is waiting.
- What is this charge on my statement?
- Why did my payment fail?
- I was charged an amount I did not expect. What do I do?
The shape it will take
The eleven-part article template from blueprint v3, section 9. Every launch article uses it, so the structure can be reviewed and designed now.
Action-oriented, in the customer's words.
One sentence, outcome first.
Product, account state, device, region, or route this applies to.
The short checklist that prevents a failed attempt.
Numbered steps, one action per step.
What the customer should see when it worked.
The exception paths, in the order customers hit them.
The details to gather first, so the first support reply can resolve it.
Liss, human, processor, shop, or safety, whichever fits the problem.
The parent heading and the neighbouring articles.
Source, owner, last-updated date, review cadence, internal tags.
If you need help with this right now
While this page is being written, the working routes are unchanged. Ask Liss from the Help Hub, or contact VOD support with the account email, what happened, when, and what you already tried.
Never send a password or a full payment-card number.