The operational goal
Track due date, requested duration, payment verification and confirmed expiry as different fields. Sending a reminder does not renew an account.
A record that supports the decision
| Field | Purpose |
|---|---|
| Current account | Use a stable private reference, not only a customer’s display name. |
| Current expiry | Record the account’s confirmed starting state. |
| Requested extension | Keep the proposed duration and connection scope. |
| Payment review | Record the verification state and private reference. |
| Confirmed operation | Keep the actual panel action and confirmation date. |
| New expiry | Compare the result with the agreed extension rule. |
Start from an identified account
Customers can have an old inactive profile beside a current account. Identify the one being renewed and ask how the intended extension is applied. Do not invent a rule for carrying unused time or assume the new term always begins on the reminder date.
Use states that can be reconciled
Useful states include enquiry received, payment pending, payment verified, operation requested and operation confirmed. An email sent or a calendar tick does not establish the last state. Keep the evidence for a transition with the private record.
Resolve exceptions before another charge
If a payment or panel action is uncertain, review its reference before repeating it. After confirmation, check the resulting expiry and intended player route. A source-specific playback problem after renewal should not automatically become another renewal request.
Worked situation
Illustrative case: a reminder is sent on Monday and a payment remains pending on Tuesday. The account should still be tracked as awaiting verification, rather than counted among completed renewals.
Open the relevant Golden OTT guidance or send a specific private enquiry.

























