Verihubs Logo
HomeBlogE-Wallet KYC Philippines: EMI Rules and Onboarding
13 min read•ID Check•Published on November 22, 2026

E-Wallet KYC Philippines: EMI Rules and Onboarding

E-Wallet KYC Philippines: EMI Rules and Onboarding

E-wallet KYC in the Philippines is how an electronic money issuer verifies each wallet user before their limits grow. EMIs work under AMLA, BSP Circular 1166 on e-money, and Circular 1170 on eKYC, plus AFASA duties against mule accounts. So a sound flow uses account tiers, a government record check, a live selfie, screening, and re-verification at upgrade.

Which BSP Rules Govern E-Wallet KYC in the Philippines

Six instruments shape e-wallet KYC today, and a seventh is still in draft. Because an e-money issuer (EMI) sits under BSP supervision, AMLA treats it as a covered person with full customer due diligence duties. The BSP rules then decide how the EMI meets those duties remotely, how it sets wallet limits, and what it owes scam victims.

RuleWhat it means for an EMIStatus (19 Nov 2026)
AMLA, RA 9160 as amendedCovered person duties: CDD, record keeping, and covered and suspicious transaction reports to the AMLCIn force
BSP Circular 1166 (2023)Current e-money rules; replaced Circular 649 and lets each EMI set limits per client categoryIn force
BSP Circular 1170 (2023)CDD and eKYC guidelines: tiered or risk-based eKYC, assurance levels, PhilSys eKYC acceptedIn force
BSP Memorandum M-2024-026Accept every National ID format, digital ID included, as proof of identity, subject to authenticationIn force; BSP repeated it in M-2025-012
AFASA, RA 12010 with Circulars 1213, 1214, 1215 (2025)Mule offences, account protection controls, fraud monitoring, and holds on disputed fundsIn force
Data Privacy Act, RA 10173Lawful basis, notice, and security for ID numbers and selfiesIn force
Draft BSP memo on NIDAS (Aug 2026)Mandatory National ID authentication, with EMIs in phase 1Draft only

For the wider framework across banks and lenders, see our guide to BSP eKYC rules.

What Changed When Circular 1166 Replaced Circular 649

Circular 649 dated from 2009 and capped e-money loads with a regulator-set monthly limit. According to a Legal 500 summary of the 2023 rules, Circular 1166 removed the PHP 100,000 aggregate monthly load limit. Instead, EMIs now set predefined limits and thresholds per client category, based on their own risk assessment and CDD. The same summary notes that non-bank EMIs must apply enhanced due diligence to single pay-outs above PHP 500,000.

That shift matters more than it looks. Your wallet limit is now a compliance decision your team must defend to examiners, not a number you copy from a circular. So tiers, limits, and the KYC behind each tier belong in one documented policy.

Fintechs that launch a wallet through a licensed partner face one more rule. BSP Memorandum M-2026-030, issued in June 2026, reminds supervised institutions that only the BSP-approved entity holds e-money authority. It also covers co-branding, wallet provisioning, platform access, and outsourcing. In short, the licensed EMI stays accountable for KYC, even when a partner app runs the front end.

How Tiered E-Wallet Accounts and Wallet Limits Work

Most Philippine wallets run at least two tiers. A basic account opens with a mobile number and a few personal details, while a verified account has passed ID and selfie checks. Circular 1170 supports this design, since it asks for tiered or risk-based eKYC with onboarding requirements that match the assurance level.

In practice, wallets publish their own limits per tier, and the gap shows quickly. A basic account usually carries a lower monthly cap and may not send bank transfers, while a fully verified account gets a higher cap and the full feature set. Still, each wallet sets and changes its own figures, so check the provider’s current limit page instead of quoting old numbers.

The table below shows a common tier design. It is a working pattern, not a tier list that the BSP prescribes.

TierWhat the user can doChecks before accessControls after access
BasicReceive funds, pay merchants, hold a small balanceMobile number, device check, name and birth dateLow limits, no bank transfer or cash-out, velocity caps
VerifiedSend to users and banks, cash out, higher limitsID capture, record check, selfie with liveness, face match, screeningDevice binding, transaction monitoring, step-up on a new phone
High-value or businessLimits above the verified ceiling, merchant or reseller useVerified checks plus source of funds and EDD; PEP review on a matchManual review, ongoing monitoring, periodic re-KYC

Here is the trade-off. Strict checks at sign-up cut fraud but lose users, while a loose basic tier invites mule farms. The usual answer is a tight basic tier with no cash-out, and full KYC as the gate to money movement.

E-Wallet KYC Onboarding Flow: Six Steps From Phone to Risk Tier

Six-step e-wallet onboarding flow from phone check to risk tier

A strong e-wallet KYC flow runs six checks in a fixed order, and each check covers a blind spot of the one before. Order matters because the cheapest checks should stop the obvious fraud before you pay for the expensive ones.

  1. Phone number and device check. First, bind the mobile number, then read device signals before the user types a name. Emulators, rooted phones, and one phone feeding many sign-ups are early mule signs.
  2. ID capture with OCR. Next, read the ID to prefill the form and cut typing errors. Accept the PhilID, the digital National ID, a driver’s license, and other valid IDs, because many users carry only one.
  3. Government record check. Then confirm the submitted details match an official record. A clean card photo proves nothing if someone invented the identity behind it.
  4. Selfie, liveness, and face match. Liveness shows that a real person faces the camera. Face match then ties that person to the ID portrait.
  5. Watchlist and PEP screening. Screen the name and birth date against sanctions, PEP, and watchlist data. Also keep AMLC and Anti-Terrorism Council designations in your own screening scope.
  6. Risk tier and limits. Finally, combine the results into a tier, set the limits that tier allows, and log every result for audit.

What Each E-Wallet KYC Check Proves, and What It Cannot

Each layer also has a limit. For example, OCR reads a card, yet it cannot prove the card is genuine. A record check proves an identity exists, but not that the applicant owns it. Liveness proves presence, not identity, so the layers only work together.

Verihubs ID verification against Philippine records covers step three. Specifically, it checks applicant data against official sources covering four Philippine IDs: PhilSys, the LTO driver’s license, SSS, and NBI Clearance, and its product page lists e-wallet onboarding as a use case. Verihubs face recognition with active and passive liveness then handles step four in the same flow. For PhilSys-only options, compare our PhilSys verification API guide.

Screening needs care too. Verihubs Watchlist Screening checks a name, with birth details and country, against PEP, sanctions, and watchlist profiles and returns a similarity score. Your policy still decides which lists you must cover, and our guide to sanctions screening duties explains the AMLC and ATC side.

Privacy runs through all six steps. Under the Data Privacy Act, government-issued ID numbers count as sensitive personal information. So tell users what you check and why, get consent when you rely on it as your legal ground, and keep selfies and ID images only as long as your retention policy allows.

Where E-Wallet Onboarding Loses Users, and How to Keep Them

Most drop-off happens at ID capture and the selfie, not at the record check. Users quit when a blurry photo fails with no hint, or when the app rejects the one ID they have. Still, a few design choices win most of them back.

  • Guide the retake. Tell users what went wrong, such as glare or a cropped edge, instead of showing a generic error.
  • Accept more than one ID. Offer PhilID first, then a fallback list, so users without a National ID can still verify.
  • Defer heavy checks. Open the basic tier fast, then ask for full KYC when the user first tries to send money or cash out.
  • Route grey cases to people. Send partial matches to a review queue with a clear response time, rather than auto-rejecting them.

Mule Account Red Flags and AFASA Duties for E-Wallets

AFASA made mule wallets a crime and made weak controls a business liability. Under Section 4 of RA 12010, money muling includes opening an account under a fictitious name or another person’s identity, and buying, renting, selling, or lending a financial account. The law’s definition of a financial account expressly includes e-wallets.

Section 6 then requires adequate controls, such as multi-factor authentication, fraud management systems, and enrollment and verification processes. Institutions the BSP finds compliant avoid liability for those losses, while others may owe restitution to victims. Section 7 also lets an institution hold disputed funds for up to 30 calendar days, unless a court extends the hold. The BSP issued Circulars 1213, 1214, and 1215 in May 2025 to put these duties into practice.

Red flagWhere it showsControl
Many sign-ups from one phoneOnboardingDevice sharing signal, face deduplication
Emulator, rooted phone, or cloned appOnboarding and loginDevice risk check, block or step-up
Same face under different namesOnboarding1:N face search across users
New wallet takes many small transfers, then cashes out fastTransactionsVelocity rules, temporary hold
New phone, then a large transfer within minutesTakeover or sold walletSelfie step-up before the outflow
Active call or screen share during a transferSocial engineeringCall and screen-share signals, delay

Clearly, device signals carry much of this table. Verihubs device intelligence for wallet sign-ups flags rooted or jailbroken handsets, emulators, hooked or cloned app builds, faked GPS locations, traffic hidden behind a VPN or proxy, live screen-sharing sessions, ongoing phone calls, and a single handset shared across several wallet accounts. For how recruiters find and pay mules, read our breakdown of mule recruitment patterns, and use the AFASA compliance checklist for the full control set.

Account Upgrade and Re-KYC Flow for Wallet Users

Re-KYC is where many wallets leak risk, because a user verified once can sell the wallet later. So treat verification as a recurring event tied to risk, not a one-time gate at sign-up. These triggers should start a fresh check:

  • An upgrade from basic to verified, or a request for limits above the current tier
  • A new phone, a SIM change, or a login from an unusual location
  • A dormant wallet that suddenly receives and forwards funds
  • A change to name, birth date, or ID details
  • A new screening match or a monitoring alert

Keep the upgrade light. Reuse the data you already verified, then run only what the trigger needs: a selfie with liveness against the stored face, a fresh record check when details changed, and a re-screen. Finally, update the tier and log the reason.

Take a common case. A verified user in Cebu logs in from a new phone and tries to send PHP 40,000 to a first-time recipient. A selfie step-up before release costs the real owner a few seconds, but it stops a buyer who holds the SIM and PIN yet not the face.

NIDAS Readiness: What E-Money Issuers Should Prepare

In August 2026, the BSP circulated a draft memorandum on integrating with NIDAS, the National ID Authentication Services run by the PSA. According to press reports on the draft, phase 1 covers e-money issuers, digital banks, VASPs, and retail-facing universal and commercial banks, three months after the memo becomes final. Until an institution joins NIDAS, the draft points it to the National ID Check platform, and it still allows other valid IDs on a risk basis.

The BSP issuances list still showed no final version on 19 November 2026, so the timeline can still change. Even so, the direction is clear, and M-2024-026 already asks institutions to accept every National ID format subject to authentication. EMIs can prepare now:

  • Map every point where a PhilID enters your flows: onboarding, account opening, and profile updates.
  • Plan where National ID authentication sits in step three, beside your other record checks.
  • Keep a fallback path for users without a National ID, as the draft itself allows.
  • Update consent and privacy notices for National ID authentication.
  • Log authentication results per user, so you can show examiners what you checked and when.

Frequently Asked Questions

Do e-wallets in the Philippines need KYC?

Yes. E-money issuers sit under BSP supervision, so AMLA treats them as covered persons with customer due diligence duties. BSP Circular 1170 allows them to run that due diligence remotely through tiered or risk-based eKYC.

What is the difference between a basic and a verified e-wallet account?

A basic account usually opens with a mobile number and a few details, and it carries low limits with no bank transfer or cash-out. A verified account has passed ID, record, and selfie checks, so it unlocks higher limits and money movement.

Does the BSP set a maximum e-wallet limit?

Not a single cap anymore. Circular 1166 replaced the old monthly load limit under Circular 649, so each EMI now sets limits per client category based on its own risk assessment and due diligence.

Can an e-wallet accept the digital National ID for verification?

Yes. BSP Memorandum M-2024-026 tells supervised institutions to treat every format of the National ID, the digital one too, as valid proof of identity, subject to authentication.

Is selling or lending a verified e-wallet account illegal?

Yes. AFASA lists buying, renting, selling, and lending a financial account as money muling, and its definition of a financial account includes e-wallets. Opening a wallet under another person’s identity also counts.

E-Wallet KYC in the Philippines Works Best in Layers

No single check makes a wallet safe. The BSP gives EMIs room to design their own tiers and limits, but AFASA now makes them answer for the mule accounts that slip through. So the winning design keeps sign-up light, puts full KYC in front of money movement, and re-verifies the moment risk changes. Wallets that build this way approve real users faster and give examiners a clean audit trail.

Building or tightening an e-wallet onboarding flow? Talk to Verihubs about e-wallet KYC and test it with your own cases.

facebooktwitterlinkedinwhatsapp
Client Verihubs
Trusted by 400+ clients and experience faster, smarter verification with us
Get FREE Trial
View Blog