Zepeto Charged But Zems Not Received? Check These First

Zepeto Charged But Zems Not Received? Check These First

Most of the "Zepeto took my money" panics I see boil down to three things, and only one of them is an actual failure. First, confirm the charge is completed and not a pending authorization hold that frees itself in a few business days. Then make sure you're logged into the exact account you paid on. A guest account is the number-one reason Zems seem to evaporate. Last, hit Restore Purchases and reopen the app to force a sync. Credits usually land inside a few minutes to a couple of hours.

What bugs me is that nearly every guide on this jumps straight to "contact support." That's the worst possible opening move when your money is sitting in a hold that hasn't even settled. The triage that comes before the ticket is the bit nobody writes down. So I'll start there.

A pending hold and a settled charge look identical in your banking app

The authorization hold is the most misread alert in this entire mess. Your bank pings you, the amount looks gone, and you decide Zepeto stiffed you. But a hold reserves funds, it doesn't take them. The line item can sit there looking final, then quietly disappear on its own.

Per Google Store, payment authorizations usually stick around for 1–21 business days depending on your card provider. Their wording is blunt: "Payment authorizations typically stay on a user's account for 1–21 business days." For pre-authorization holds specifically, a Google Play community thread (2026) notes most clear within 1–5 business days, occasionally stretching to 7.

So here's the split that decides everything. Open your bank or card statement and check whether the line reads pending or posted/settled. A pending entry that hasn't cleared is very likely a hold, which means the purchase may have failed on the store side and the money's already on its way back without you lifting a finger. A settled charge with no Zems? Different animal entirely. That one's worth chasing.

When I'm staring at one of these, the tell I trust is the word "pending" plus the absence of a Zepeto order confirmation. No confirmation receipt usually means the transaction never fully went through, and escalating a hold like it was theft just burns days you'll want later if it turns into a genuine case. Treating the hold as a real charge and firing off a furious ticket on the spot is a documented misstep in that same Google guidance. Don't be that ticket.

Check the receipt status first. Everything after it depends on knowing which problem you've actually got.

The guest-account trap that orphans your Zems

The biggest source of "lost" Zems isn't a billing bug at all. It's buying on an unlinked guest account. Zepeto's own support is explicit that purchasing Zems on a guest account risks losing them after a data clear or re-login, per ZEPETO Support. The mechanic underneath is the quiet part: a guest session is welded to that device install. Clear app data, switch logins, or reinstall, and the entitlement can get cut loose from the profile you're now looking at.

That's why "Will reinstalling bring my Zems back?" has such an annoying answer. Only if the account was linked. On a linked account (Google, Apple, Kakao, and so on), your purchase history travels with you and a reinstall does nothing harmful. On a guest account, the reinstall can be the exact thing that severs the Zems from view.

So before anything else, confirm you're on the account you paid on. Two checks:

• Which profile is active — open Profile settings and verify the ZEPETO ID matches the one you bought on. If you've ever spun up multiple profiles, the Zems might simply be parked on a different one.
• Whether that account is linked — if it still says "guest," link it to Google/Apple now, before you touch anything else. Zepeto's guidance for guest users is direct: link immediately to avoid loss.

Linking before buying is non-negotiable for me. It takes thirty seconds and pulls the single most common failure mode clean off the board. If a first-time buyer asked me one thing to do before spending a cent, it'd be that, not memorizing a support email.

Once you've confirmed the right account and that it's linked, force-close the app fully, reopen, and recheck the balance after the sync runs. Account sync is what actually drags a freshly-granted entitlement into your visible balance, and a stale session is a legit reason Zems "don't show up" when they already exist on the server.

Restore Purchases is the fix more people should try before support

Restore Purchases clears up more of these cases than support tickets do, and it's the most ignored button in the whole flow. Zepeto's troubleshooting lists it plainly: use Restore Purchases or re-launch the app to trigger a delayed credit. And the reason it works is mechanical. Restore re-queries the store's purchase ledger (Google Play Billing or Apple's IAP system) and can re-deliver an entitlement the app whiffed on if your network dropped mid-transaction.

That network drop is exactly where credits get stuck. The payment clears on the store side, but the "deliver Zems" callback to Zepeto's servers never lands cleanly. Restore reconciles the two ledgers. If the money left your account and the store logged the purchase, this is frequently the whole repair.

While you're in there, rule out the dumbest-but-real culprit: you're reading the wrong number. Zems are the premium, paid currency. Coins are the free, earned currency. They live in separate counters. More than a few "missing Zems" posts are people watching their Coin total and wondering why it won't budge. Make sure you're looking at the Zems line specifically.

If Restore comes back empty, gather your proof now, while it's fresh:

• On Android: your Order ID lives in your Google Play receipt (the purchase confirmation email, or Play Store → Profile → Payments & subscriptions → Budget & history).
• On iOS: your receipt comes from Apple — check the email receipt from the App Store, or your purchase history in Settings.

Screenshot that Order ID the second you see it. It's the best habit for a fast resolution, because a ticket carrying a clean Order ID plus your ZEPETO ID gets handled. A ticket that says "I paid, trust me" doesn't.

One hard rule before you go further: do not request a store refund yet. Zepeto's own guidance warns that asking for a store refund before trying Restore Purchases may void a pending credit. A refund can reverse a delivery that was seconds from arriving, and then you've cancelled your own purchase and still have no Zems. Restore first. Always.

Where the money actually sits between your card and your balance

Three ledgers have to agree before Zems appear, and your panic usually lives in the gaps between them. The chain runs: your card/bank → the app store (Google Play Billing or Apple) → Zepeto's servers. A charge can clear that first link and stall before the third.

Here's the triage I'd run, matched to what each symptom usually signals:

Source: ZEPETO Support – I paid but didn't receive Coins/ZEMs (2023); Google Store – Authorization hold (2026)

Two timing windows are worth keeping in your head. Regular Zems purchases should reconcile within minutes to a few hours once the charge settles. Premium subscription benefits run slower by design. Zepeto states they may take 1 to 2 days to provide after payment. So if you bought a subscription instead of a Zems pack, a one-day wait isn't a bug. It's the stated behavior.

That hold mechanic is the one I'd staple to every billing FAQ. It can read as "charged" in your banking app and never actually settle, expiring quietly so the funds free up. If your line item is still pending and there's no order confirmation, the calm move is to wait out the release window before treating the cash as lost.

Filing a ticket that gets resolved — and when to refund instead

A support ticket only works if it's complete on the first send, so build it once and build it right. Zepeto's help center is clear on the escalation point: "If the problem is not resolved after re-opening the app, please contact ZEPETO Team." That "after re-opening" carries weight. They expect you to have tried the sync and Restore already.

Put all of this in one ticket:

1. Your Order ID / receipt number (Google Play receipt for Android, Apple receipt for iOS)
2. Your ZEPETO ID / Code
3. The store receipt itself (screenshot)
4. What you've already tried (reopen, Restore Purchases)

Charged more than once? Don't open three tickets. The guidance for double-charged repeat buyers is to provide multiple Order IDs in a single ticket. That keeps your case in one thread and stops it ricocheting between agents.

Now the refund question, because the route bends entirely on your store:

• Google Play: Zepeto can handle its own crediting, and Google refunds run separately. Google Play IAP refunds are usually requested within 48 hours of purchase, per Google Play. If Zepeto can credit you, that's cleaner than a refund, but the 48-hour window is your backstop if it can't.
• Apple: This is the one to know cold. ZEPETO cannot refund Apple in-app purchases. You request the refund directly from Apple. Per Apple Support, expect to wait 24 to 48 hours for an update on a submitted request. So on iOS the path forks: Zepeto for delivery problems, Apple for the money back.

My read on the whole "refund or wait?" argument: wait and ticket first, unless the purchase has clearly failed (settled charge, correct linked account, Restore returns nothing after several hours). A premature refund is how folks accidentally cancel a credit that was about to arrive. The refund window is a safety net, not the opening move.

If you're a first-timer mid-panic: breathe, check the receipt status, reopen the app. Most of you are looking at a hold or a sync lag, not a loss. If you're a repeat buyer staring down a true settled-charge failure with proof in hand, the ticket route moves fast precisely because you showed up prepared.

If you're planning to top up again and want a clean receipt and order trail to lean on when something goes sideways, disclosure: this piece is published by VGTopup, one transparent option for ZEPETO Zems & Coins top up. Whatever channel you use, keep that Order ID screenshot. It's the thing that resolves cases.

Frequently Asked Questions

How long should I wait before assuming my Zems are really gone?

For a standard Zems pack on a correct, linked account, give it a few hours. Credits usually reconcile within minutes once the charge settles. If you bought a subscription, Zepeto says benefits can take 1 to 2 days. And if your bank line still reads "pending," that's a hold that can take 1–21 business days to release per Google Store, so it isn't gone yet.

Why did Zepeto charge me twice but I only got Zems once?

Often one of the two isn't a real charge. It's an authorization hold sitting next to the settled purchase, and the duplicate releases on its own. Check whether one line reads "pending" versus "posted." If both genuinely settled and only one delivered, file a single ticket listing both Order IDs instead of separate ones.

Will reinstalling the app recover my missing Zems?

On a linked account, yes. Your purchase history follows the account, and reinstalling then running Restore Purchases can re-deliver a missed credit. On an unlinked guest account, reinstalling can do the opposite and orphan the Zems, since a guest session is tied to that device install. Link before you reinstall.

What if Restore Purchases does nothing on iOS?

Restore only re-delivers entitlements the store actually recorded, so if Apple has no record, the button stays empty. Confirm the charge truly settled (not a hold), then split into two routes: contact Zepeto for a delivery fix using your Apple receipt, and if needed, request the refund directly from Apple. Zepeto can't refund Apple IAPs, and Apple takes 24–48 hours to update a request.

I bought Zems on a guest account and they're gone — can I get them back?

This is the rough one, because guest purchases can detach after a data clear or login switch. Don't clear app data or swap accounts again. Open a ticket with your store Order ID, receipt, and any ZEPETO Code you've got, and link the account immediately to prevent further loss while support digs in.