Security tool · Information, not advice
The lock-down check
Money sent home moves through an e-wallet, a bank app, and the email that can reset both. This walks the protection layers GCash, your bank, Google, Microsoft and BSP publish on their own pages — eleven yes/no checks, a score, and a plain list of what each source says about the gaps. It runs in your browser; nothing you tap is sent or stored.
Self-check · 11 questions
Where your accounts stand
Eleven yes/no checks on the security layers that GCash, your bank, Google, Microsoft and BSP describe in their own pages. You get a score and a plain list of what each source says about the gaps. This is sourced information, not advice — and no setup makes any account fully secure.
Runs entirely in your browser. Nothing is sent, stored, or seen by anyone.
The interactive scorer needs JavaScript. Below is the full sourced check as a static list.
Pick one to continue.
A score is a snapshot of the layers these sources describe — it is not a guarantee. No configuration makes any account 100% secure.
Documented layers not yet in place
-
Finance email
A dedicated finance mailbox limits what one breached everyday inbox can reach (per Google Account Help). Google Account Help — 2-Step Verification
-
MPIN / OTP
GCash’s Help Center states GCash never asks for your MPIN or OTP; a request for either identifies the sender as not GCash. Confirm with GCash Help Center — How can I protect my GCash account?
-
DoubleSafe
GCash describes DoubleSafe + single-device registration as the layer that blocks a new device even when MPIN and OTP are known. Confirm with GCash Help Center — What is GCash DoubleSafe?
-
Wallet/bank 2FA
Maya, BPI and BDO each document an on-by-choice second factor or device approval in their own help pages. Confirm with Maya Help — Set up Two-factor Authentication (2FA)
-
Email 2-Step
Google and Microsoft both document a sign-in second step so a leaked password alone cannot open the inbox. Google Account Help — Turn on 2-Step Verification
-
Recovery set
Recovery contact info and backup codes are how Google/Microsoft document regaining — and being alerted about — an account. Google Account Help — App passwords & recovery
-
Unique pwds
A reused password turns one site’s leak into access to the rest; unique passwords + a manager is the standard mitigation cited by CISA. CISA — Use Strong Passwords / Recognize and Report Phishing
-
Device review
Google documents a devices / recent-activity view for spotting and removing sessions you do not recognise. Google Account Help — 2-Step Verification (devices & activity)
-
Screen lock
A device passcode is the baseline barrier between a lost phone and the apps holding your money and OTPs. CISA — Secure Our World (device basics)
-
Not all in one
A single daily-use wallet holding the full balance is the largest single point of loss if it is compromised (BSP “Check, Protect, Report”). PIA / BSP — “Check, Protect, Report”
-
SIM / swap
RA 11934 registration is a deterrence measure and does not by itself stop SIM-swap OTP interception — the app-based factors above are what limit it. Confirm with NTC — FAQs on the SIM Registration Act (RA 11934)
Every layer these sources describe was marked “Yes”. Re-check when a provider changes its options — and read the caveat above.
Marked already set
- Finance email
- MPIN / OTP
- DoubleSafe
- Wallet/bank 2FA
- Email 2-Step
- Recovery set
- Unique pwds
- Device review
- Screen lock
- Not all in one
- SIM / swap
- None marked set yet.
Sources — checked, dated
Check these on the official page
Security settings change, and only the provider can show what’s true for your account today. For anything marked “Confirm with …”, open its official page below and check the current setting yourself — especially if it looks different from what’s described here.
Sources checked
Sourced & dated information — not financial or immigration advice. Our sources & ranking policy.