Sword of Fire and Ice Top Up Payment Pending or Failed: What's Actually Happening to Your Money
You finally drop some cash on Sword of Fire and Ice and the screen locks on "pending" or spits out "failed." Annoying as hell, especially if you rarely spend. So before you do anything: don't retry. Grab your order ID first, then go read your bank statement and figure out whether that charge is a temporary authorization hold or a genuine deduction. Most pending charges sort themselves out, and bank holds can take up to 30 days to release depending on your bank, per the Steam Help Center. The priciest blunder here isn't the failed payment. It's the panic re-pay right after.
The Mohiztec gateway for cash coupons runs on the same rails as basically every other mobile top-up out there. Same fixes apply. Same traps wait. So let's start at the second the screen locks up and walk forward, because the sequence matters more than any single move.
The frozen screen: pending, failed, and the third state nobody names
Reading your status right is the whole game, and most guides smush three completely different situations into one mushy "it didn't work." They aren't the same animal. The correct move hinges entirely on which one's got you.
Pending means the transaction's still in the air. Your bank might've slapped an authorization hold on the funds, a temporary reservation that looks dead identical to a real charge in your banking app but wears a "pending" tag that drops on its own. This is the hidden gear behind most "I got robbed" posts. The money looks gone, but nothing was ever actually captured. Pending transactions can sit up to 30 days before a bank cuts the funds loose, per Wargaming and Steam support docs, though in real life the overwhelming majority clear way sooner.
Failed means the gateway rejected or bailed on the transaction. And here's the nasty bit: a failed payment can still flash a deduction, because the authorization fired before the capture flopped. Money pulled on a failed payment is almost always a hold that reverses, not cash that vanished into nothing.
Paid-but-not-credited is the sly one. The payment honestly went through, your card got charged, yet no cash coupons show up in your wallet. Don't assume the worst yet. Rewards land via in-game mail after a top-up, and points can take a beat to refresh, per the Sword of Fire and Ice Facebook page. Coupons drop into your mailbox instead of your wallet, so a "missing" balance is usually just an unclaimed mail attachment sitting there. Crack open your mail first and a huge slice of "coupons not received" complaints quietly die before anyone files a ticket.
| Status | What it actually means | Recommended action | Typical resolution |
|---|---|---|---|
| Pending | Transaction in flight; charge is likely an auth hold | Wait, capture order ID, do NOT retry | Often hours; hold release up to 30 days per bank |
| Failed (no deduction) | Gateway rejected before any charge | Diagnose cause, then a single clean retry is safe | Immediate |
| Failed (money deducted) | Auth hold fired, capture failed | Wait for auto-reversal; do NOT retry | Usually within days; hold up to 30 days |
| Paid, no coupons | Payment succeeded, delivery delayed or in mail | Check in-game mail and refresh balance | Minutes to a few hours |
Source: Steam Help Center (2026), Wargaming/Steam support docs (2026), Sword of Fire and Ice Facebook page (2026).
Find your row, then keep reading knowing exactly which problem you're chasing. The causes behind each one differ too.
Why the gateway stalls in the first place
Pending and failed states nearly always trace back to one of four mechanical causes, and pinning yours tells you whether to sit tight, retry, or fix something on your end first.
Bank authorization plus 3D Secure verification is the usual suspect. When your bank shoves you through a 3DS confirmation (that SMS code or app approval step) and the check times out, or you tap away too slow, the gateway gets stranded holding an authorized-but-uncaptured transaction. That's your pending state, born from a handshake that never finished.
Network instability is the quiet assassin. A flaky or weak connection can make the payment page time out, and the documented fix is to flip between Wi-Fi and mobile data or kill any VPN or firewall, per several game support pages including the Arknights Endfield Help Center. But watch this trap nobody flags: switching networks mid-payment (your phone ditches Wi-Fi and jumps to data while the gateway's still chewing) can orphan a transaction that then succeeds silently in the background. You see "failed." The system sees "done." That mismatch is precisely how a retry becomes a double-charge.
Gateway latency on its own eats a chunk of pending cases. The processor's just slow returning a confirmation, and your client throws in the towel before the server does.
Then there's the cause with nothing to do with payments whatsoever: account or server ID mismatch. Top up to the wrong account or server and your coupons simply never surface, a notoriously common mobile-game blunder echoed across SEAGM's Sword of Fire and Ice top-up page comments. Payment clears, money's gone, coupons are parked in some stranger's account on the wrong server. No gateway error trips because nothing technically broke. You just knocked on the wrong door. Verify your ID before you ever point a finger at Mohiztec.
Got your cause? Good. The next half hour is about evidence, not action.
Your first 30 minutes: capture, check, confirm — in that order
Don't ping support in the first minute, and for the love of primos, don't re-pay. Waiting 30 to 60 minutes while you collect proof clears more cases than any panic ticket. Most pending states untangle themselves in that window, and most "missing" coupons show up in your mailbox.
Run the sequence:
-
Capture the order ID and receipt before you touch anything. Screenshot the payment confirmation, the order number, the timestamp. Closing the payment window before you save the order ID is bog-standard e-commerce advice that game support repeats for good reason: it makes refunds way harder. One screenshot rescues more refunds than any agent can.
-
Open in-game mail and refresh your coupon balance. Since rewards arrive by mail and points lag, a delivery you wrote off as failed might already be sitting unclaimed. Refresh the wallet, hit the mailbox, refresh once more.
-
Confirm the charge in your banking app, and read the tag. A "pending" label beside the charge means it's an authorization hold that'll probably drop on its own. A fully posted transaction is a real capture. That one distinction tells you whether you're waiting on a reversal or hunting a delivery.
-
Run the connectivity fixes if you're still stuck mid-failure. For in-app purchases, force stop the app, check your connection, restart the device, and make sure your account's signed in right, per Google Play Help. Routing through a payment page instead? Kill the VPN.
Notice what's missing from that list: retrying. That only comes after you've confirmed status. And getting that part wrong deserves its own breakdown.
The retry trap: when one more attempt costs you twice
Retrying a failed payment before you confirm its status can spawn a double-charge. It's one of the most common self-inflicted wounds across Steam and Google Play top-up headaches, and Mohiztec flows play no differently. The logic's brutal. If your first attempt orphaned a transaction that later succeeds silently, your "second" payment is just a duplicate. Now you're charged twice for coupons you might only ever get once.
So here's the rule I'd actually live by:
- A retry is safe only when the status reads a clean "failed" with zero deduction on your bank statement. No hold, no pending tag, no posted charge. Then trying again, ideally after fixing the underlying network or verification snag, is fine.
- A retry is NOT safe while anything reads pending, or while a deduction shows even on a "failed" screen. Let the status fully resolve. Pending isn't failure, and treating it like one by re-paying is the costliest move players pull.
That popular "just try a different payment method" advice earns a hard side-eye too. Feels productive. It's frequently the exact move that manufactures the double-charge it claims to dodge, because now you've got two live authorizations running through two rails. If your first attempt isn't confirmed dead, a second method doesn't cut risk. It doubles it.
When a payment genuinely won't go through clean, the documented order is to verify your method is valid with enough balance, clear any holds with your bank, then retry after a few minutes, per Hoyoverse Support. That "after a few minutes" earns its keep. It gives the first attempt room to declare itself dead before you fire a new one.
If a duplicate or a real loss does land on you, the next question is how long your money takes to come home.
Getting your money back: timelines and the ticket that actually works
Most "money deducted" situations end in reversal, not refund, and that split sets your expectations. An authorization hold reverses by itself. You file nothing, you wait. The bank frees held funds on its own clock, which support docs put at up to 30 days, though most clear within several business days. Disputing too early (cracking open a bank chargeback while the processor's mid-reversal) can knot the two refund paths together and gum up everything. Treating a hold like a permanent loss is the panic that makes the result worse.
A genuine refund, by contrast, is something you request, and your route depends on how you paid:
- Store billing (Google Play / App Store) carries the cleanest trail. Check the store for purchase status and contact store support if the top-up ran in-app, per that same Arknights Endfield guidance. These flows pack their own documented refund rules plus an auditable history, which makes disputes far simpler than card-direct ones.
- Card-direct through the gateway sends refunds back to the original card, with timing riding on both the processor and your issuing bank.
- E-wallet usually lands between the two on speed, depending on the wallet provider.
When escalation's unavoidable, the quality of your ticket is the single biggest lever on how fast it closes. An evidence-first ticket beats a sob story every time. Lead with:
| What to capture | Why support needs it |
|---|---|
| Order ID | The primary key for tracing the transaction in the processor's system |
| Exact timestamp | Lets support match your attempt to a server-side log |
| Payment receipt / bank screenshot | Proves the charge (and whether it's pending vs posted) |
| Account & server ID | Confirms coupons were routed to the right destination |
| Failure/error screenshot | Identifies the precise state and any error code |
Source: synthesized from Google Play Help (2026), Arknights Endfield Help Center (2026), and general processor dispute practice.
Open with the order ID and timestamp, attach the receipt, state the status flat, and ask the one specific question: reversal status, or re-delivery of paid coupons. That ticket gets worked. A "I paid and got nothing, help!!" message with no reference number just rots in the queue.
What I'd actually do, and how to dodge this entirely next time
My honest read: nine times out of ten the "lost" money isn't lost and the "missing" coupons aren't missing. The pending charge is a hold that drops. The coupons are an unclaimed mail attachment. The players who actually bleed cash are usually the ones who panicked, re-paid into a double-charge, or disputed a hold so hard the reversal jammed.
So the quickest path to your coupons is almost always this: screenshot, check the mailbox, confirm the bank tag, wait an hour, then act. Dull. Works anyway.
To stop tripping this entirely, three habits do most of the heavy lifting. Top up on a stable connection and never switch networks mid-payment. Use a verified payment method with confirmed available balance so 3DS doesn't choke. And triple-check your server and account ID before you confirm, because a mismatch is the one failure no refund timeline can rescue. Technically nothing failed.
If you'd rather just have a smoother run on the next purchase, a transparent top-up route helps. Sword of Fire and Ice Cash Coupons recharge is one option worth weighing next to in-game and store billing, as long as you bring the same discipline a tightwad like me swears by: save the order ID, confirm the server, don't retry blind. The protocol matters more than the channel.
Frequently Asked Questions
How long does a pending Mohiztec payment take to clear?
Most pending states wrap up within hours, but the underlying bank authorization hold can technically linger up to 30 days before the bank releases the funds, per Steam and Wargaming support docs. If your banking app shows a "pending" tag rather than a posted charge, that's the hold. It's built to auto-drop, so chasing it inside the first day rarely does a thing.
I paid successfully but the cash coupons never showed up — where are they?
Open in-game mail before anything else. Rewards land there after a top-up and the balance can lag, per the Sword of Fire and Ice Facebook page, so an unclaimed attachment is the likeliest culprit. Refresh the wallet too. Only if both come up empty after a few hours should you suspect a server/account ID mismatch, which means the coupons went somewhere wrong, not nowhere.
Was I double charged, and what do I do if so?
If you retried before the first attempt confirmed as failed, a duplicate's on the table, especially if your network dropped mid-payment and the original quietly succeeded. Scan your statement for two captures (not one capture plus one pending hold, since the hold reverses on its own). For a real duplicate, store-billing purchases give you the cleanest refund trail. Round up both order IDs and timestamps before you contact support.
Should I dispute with my bank or wait for the processor to refund me?
For a pending hold or a failed-but-deducted charge, wait. These reverse automatically, and filing a bank chargeback mid-reversal can tangle the two refund paths and stall your money. Save the bank dispute for when the charge has fully posted, coupons never arrived, and support hasn't fixed it within the stated window.
Is it ever safe to retry a failed Sword of Fire and Ice top-up?
Only when the status reads a clean failure with zero deduction on your statement: no hold, no pending tag. Fix the likely cause first (stable connection, valid payment method, killed VPN), then make a single attempt, per Hoyoverse's troubleshooting order. While anything still reads pending, a retry is the fastest way to pay twice for one set of coupons.
Comments