If Lvcha VPN still shows expired after a successful payment, copy the order id, charge time, and the in-app expiry onto one line. Wait 10–30 minutes for the billing callback, then sign out and back in—do not uninstall. Store purchases and website purchases are not the same ledger. Paying again, swapping nodes, or reinstalling will not write the entitlement faster.
This collides with a full device list: the upgrade says “5 devices” on marketing, the account page still says 2. Slots: device cap. Actual packet loss: no traffic. Builds: download page.
Processor, account, client cache
Processor: card SMS, Apple purchase history, PayPal. Account: plan name, expiry, device cap on the web/app account page. Client cache: the giant “0 days left” on the home screen. When they disagree, the processor is your proof; you chase the other two. You do not open a second checkout.
A browser refresh after a web payment does not refresh a phone that still holds an old token. Sign-out forces a fetch; swiping the app away does not. Windows auto-start can keep a process alive with the stale token—quit the tray icon. Boot-time races are autostart drop, not billing.
| Sighting | Likely | Wait / do |
|---|---|---|
| Paid, account page unchanged | Callback lag | 10–30 min, do not double-pay |
| Account updated, app still expired | Local cache | Sign out / in |
| Store charged, website stale | Two ledgers | Restore purchases |
| Expiry off by 8 hours or a day | Timezone | Receipt timestamp |
Do not mix Store, web, and gift codes into a second purchase
A year on the website plus an iOS subscription is two entitlements that may never meet. Restore purchases only talks to the Store. Redeem codes in the official field; a chat message is not redemption. Order-id formats differ—one wrong character and support cannot see the callback.
A charge that later shows “refund pending” will roll the account back. The client may flip expired/valid for a few hours. Sit on your hands. A Family Sharing payer is not always the Lvcha account on the device in your bag—that looks like “money left, status did not.”
Upgrades, downgrades, grace, node lists
After a higher tier, extra regions can lag the permission bit. URL-test going all-red in that window is not every node dead. Wait until the plan name on the account page changes. A downgrade will kick the extra device on the next heartbeat; warn whoever has Kill Switch on that PC.
Some plans limp in a grace window: connected, throttled, banner still says expired. People buy a second copy. Read the status enum (expired / grace / active), not the marketing headline on the home card.
Minimum packet for support: order id, charge time to the minute, account handle, client version (2026.07 from the download page), which of your machines still shows expired. Node-latency screenshots are noise here.
Stop before you “fix” billing with a reinstall
Two hours, account page still frozen: confirm the merchant name on the processor matches the purchase you intended. Unknown merchant → stop, phishing, only use this site’s download and guides. Correct merchant → keep the receipt, official support, no “renewal patch” EXE.
Done when: account expiry is in the future, device cap moved if you paid for it, the in-app banner is gone, 1.1.1.1/help loads. Still kicking devices? Back to the cap article, not another checkout. Else FAQ.