If you have used the external web store for High Seas Hero: Dig & Build, inspect your account immediately and block or freeze any payment card saved on the site. A community security alert highlighted by player Sakura identified an active security risk on the game's official web payment portal, placing stored credit and debit card information at risk of unauthorized access.
How to Remove and Block Saved Cards
To protect your financial accounts from potential compromise, sever any connection between your banking cards and the web storefront right away.
- Log in to the Web Portal: Navigate to the official Century Games top-up site for High Seas Hero: Dig & Build and sign into your account.
- Open Payment Settings: Go to your account profile or checkout management screen where previously used payment methods are stored.
- Delete Stored Cards: Remove every saved credit card, debit card, or linked billing profile. Ensure no payment details remain registered for automatic or one-click checkout.
- Freeze or Block the Card in Your Banking App: Open your bank or credit card mobile application and temporarily lock or freeze the specific card used on the portal. If your card issuer does not support temporary freezing, contact customer service to request a replacement card with a new account number and CVV.
- Clear Browser Cache and Cookies: Clear stored autofill data, cached forms, and cookies from your web browser to remove local session tokens.
Freezing or replacing the card provides the strongest protection because it ensures that even if payment tokens or credentials were recorded externally prior to deletion, future unauthorized charges will be declined by your financial institution.
Web Store Purchases vs. Mobile App Billing
External web shops are commonly set up by publishers to offer bonus incentives, such as discounted packs or extra diamonds, while avoiding mobile platform transaction fees. However, direct browser storefronts involve different security considerations compared to native app store environments.
| Feature / Factor | External Web Storefront | Apple App Store / Google Play Store |
|---|---|---|
| Data Handling | Payment details entered into browser forms; risk of retained tokens | Sandboxed processing; card numbers are not exposed to the publisher |
| Purchase Authorization | Often uses cached session data without re-authentication | Requires biometric verification (fingerprint/face) or password entry |
| Dispute Handling | Managed through publisher support | Processed via platform refund workflows |
| Incentives | Extra diamonds and exclusive web bundle tiers | Standard package rates without web-specific tier bonuses |
If you continue making purchases in High Seas Hero: Dig & Build, using native in-app billing through your device provides sandboxed security at standard pricing. If you choose to use web stores for bonus rewards, avoid saving payment credentials for future use, or pay through intermediate options such as PayPal or single-use virtual cards with strict spending limits.
What to Do if You Spot Unauthorized Charges
Regularly check your recent bank and credit card statements if you have completed transactions on the web storefront.
- Contact Your Bank Immediately: If an unrecognized transaction appears under Century Games or an unfamiliar payment processor, file a dispute with your bank right away to block further charges.
- Submit an In-Game Ticket: Contact High Seas Hero: Dig & Build customer service through the in-game settings menu. Provide the disputed transaction ID and explain that the charge was unauthorized due to the portal security issue. Alerting support helps prevent automatic account suspensions that can occur when banks issue chargebacks.
Free High Seas Hero: Dig & Build Codes
Current active codes and how to redeem them.
COMMUNITY
Player Comments
116 players commented on this guide.
Nice guide. I am checking the other High Seas Hero: Dig & Build articles next.
The explanation is clear, especially for beginners.
This helped me understand heroes much better.
This guide answered the exact question I had.