Plan first, payment second

Plus and Pro are not the same product with a different badge. Allowances, model access and the shape of the usage limits all change between tiers, and those differences determine what you should buy, not the other way round. Read the current comparison on the official plan page instead of trusting a screenshot from a few months ago, then write down what the next term actually needs to cover: ordinary daily use, long-context work, or heavier agent-style runs. Getting the tier wrong is the most expensive mistake in this process, because it is the one mistake a refund will not fix.

Five checks before money moves

• Whose account gets upgraded. Activation on an account you already control and delivery of a ready-made account are different products, with different risk and different handover steps. Know which one you are buying before you pay for it.
• What the quoted total includes. Currency, service fee and term should all be visible before the confirmation screen. A page that only shows a monthly figure has not quoted you anything.
• What happens if activation fails. Look for a written refund process, not a promise that appears in a chat window. A policy with no stated steps is marketing, not a term.
• How the order can be tracked. There should be an order page with visible states, and a way to open a ticket against that specific order. Support that only exists as an inbox address gives you nothing to point at when something goes wrong.
• What data is requested. Passwords and session content are sensitive by definition. Submit them only through a designated order page, never in chat, email or a screenshot. If a stranger asks for your password as a step in the flow, that is the end of the conversation.

None of these checks require technical knowledge. They require someone to slow down for ten minutes before a payment, which is exactly what most people skip when a subscription lapses at an awkward moment.

Separate paid from activated

Payment success and membership activation are two different events, and merging them in your head is how people end up paying twice. A payment confirmation tells you the money moved. Activation is only confirmed by checking the membership on the account itself. If the order is still processing, the right move is to wait or open a ticket on that order, never to start a second purchase. Keep the two states written down separately; the distinction matters most on the day it matters.

Keep a log, the way you keep an incident log

Save the order number, the receipt, the plan and term you selected, the quoted total, and a dated screenshot of the order page at each state change. Three weeks later, that log is the difference between a ticket that gets resolved and an argument that goes in circles. It also hands you the renewal date, which is the one date nobody remembers until it becomes inconvenient.

None of this requires trusting a vendor. It requires reading the terms the way you read a changelog: before the upgrade, not after something breaks.

Source: the subscription terms and order-flow reference used for this checklist — sublynow.com