BSP National ID Integration: NIDAS Readiness Guide

BSP national ID integration is moving from encouraged to required. A draft BSP memorandum released in August 2026 would have banks, digital banks, e-money issuers and VASPs use the PSA’s National ID Authentication Services (NIDAS) when they onboard customers, open accounts and update records. For the first group, the deadline would fall three months after the final memo comes out.
One point matters before anything else. As of 19 November 2026, the rule is still a draft. We found no final NIDAS memorandum in the BSP issuances list, so no compliance clock has started. Still, Phase 1 institutions would get only three months once BSP signs it, and the PSA application alone can take much of that window. So this guide covers what the draft would require, which phase you fall in, and what to prepare now.
What the Draft BSP NIDAS Rule Would Require
The draft would make NIDAS part of customer due diligence for BSP-supervised institutions (BSIs). NIDAS is the real-time authentication service that the Philippine Statistics Authority (PSA) built with the Department of Information and Communications Technology. Specifically, it checks a person against the National ID registry through biometric and database matching. Institutions then reach it through National ID eVerify.
According to BusinessWorld’s report on the draft, the main obligations are these:
- Use NIDAS at three points. These are digital or in-person onboarding, account opening, and account updating.
- Use National ID Check in the meantime. Until NIDAS onboarding is complete, verify presented National IDs through the free National ID Check page.
- Pick a tier by risk. The authentication tier should follow the risk of the customer, product, service or transaction.
- Keep other IDs as a fallback. A risk-based path for other valid IDs stays open when the customer shows no National ID or NIDAS is down.
- Accept the confirmation as ID. For first-time customers, a NIDAS authentication confirmation would replace a physical or printed National ID.
- Keep the controls around it. AML and counter-terrorism financing controls, cybersecurity and data protection still apply.
One detail changes how teams plan. Based on the same report, BSP would treat a BSI as compliant once it submits a complete application, with all documentary and regulatory onboarding requirements, to the PSA. So the deadline covers the application, not a finished integration. However, Philstar reported that BSP would track onboarding status through the PSA and may take supervisory action against institutions that stall. The same report adds customer consent mechanisms to the list of required controls.
Which NIDAS Phase Your Institution Falls In

The draft splits BSIs into two waves. Retail exposure decides the order more than asset size does, so institutions that onboard at volume, especially through apps, go first.
| Phase | Who is covered | Deadline |
|---|---|---|
| Phase 1 | Universal and commercial banks with retail banking services, digital banks, electronic money issuers (EMIs), and virtual asset service providers (VASPs) | Three months after BSP issues the memorandum |
| Phase 2 | All other universal and commercial banks, thrift banks, rural and cooperative banks, payment system operators with KYC or know-your-merchant functions, and other BSIs | Six months after the memorandum takes effect |
| New registrants | Institutions that register with BSP after the rule starts | The same three or six months, counted from registration |
Two practical notes follow from the reports. First, Philstar reported that a BSI wanting to move from Phase 1 to Phase 2 would need approval from its BSP supervising sector. Second, a group with several licences can land in both phases. Take a thrift bank with an e-money subsidiary: the bank sits in Phase 2, but the EMI would run on the shorter Phase 1 clock.
How the Draft Changes BSP Rules Since M-2024-026
BSP has pushed the National ID for more than two years, but always as acceptance first and authentication second. The draft flips that order.
| Issuance | What it required | Where NIDAS stood |
|---|---|---|
| M-2024-026 (9 August 2024) | Accept all National ID formats, including the Digital National ID, subject to authentication; use National ID Check | Encouraged |
| M-2025-012 (6 April 2025) | Accept all formats as primary proof of identity; use National ID Check; list the National ID first among acceptable IDs in every branch | BSIs “enjoined” to onboard through National ID eVerify |
| Draft memorandum (August 2026) | Use NIDAS for onboarding, account opening and account updating, with risk-based tiers and phase deadlines | Required, with possible enforcement |
The 2024 memo also carried a PSA caveat that many teams missed. It said National ID Check suits low-risk transactions, while NIDAS gives higher assurance. That caveat explains the draft. A QR check proves the card data is genuine, but it cannot tell you the person holding the card owns it. For format-level checks at the counter, see how to verify a Digital National ID. And if your institution read M-2025-012 as optional, that gap now has a deadline.
Choosing a NIDAS Authentication Tier by Risk
The draft does not set one tier for everyone. Instead, it asks each BSI to match the tier to the risk of the customer, product, service or transaction. BusinessWorld, citing the PhilSys framework, describes three tiers.
| Tier | What it does | Status |
|---|---|---|
| Tier 1: basic online authentication | Returns a yes or no answer, with back-end verification of the PhilSys number (PSN) token | Available |
| Tier 2: e-KYC | Shares pre-agreed demographic data fields between the relying party and the PSA | Available |
| Tier 3: interoperability | Matches back-end PSN tokens across relying parties, where the law allows it | Not yet operational |
The tier mapping is a policy call, and the final text may shape it. Still, a sensible starting point looks like this. A basic wallet with low limits may only need the Tier 1 yes or no answer. By contrast, a loan, a deposit account or a wallet upgrade to higher limits benefits from Tier 2, because the returned fields let you prefill and compare data instead of trusting what the customer typed.
Write the mapping into your AML risk assessment, so examiners can see why each product sits where it does. Also, outlets describe the tiers slightly differently. Confirm the exact definitions against the final memorandum and PSA’s relying-party documents before you lock the policy.
What NIDAS Confirms, and What It Leaves to You
NIDAS answers one question very well: does this person match a real National ID record? That is a big step up from reading a card photo. But it covers identity only, and the rest of the existing BSP KYC requirements still apply.
| NIDAS authentication does | It does not |
|---|---|
| Confirm the person matches a PhilSys record | Explain why the customer wants the account |
| Remove the need for an ID photo for first-time customers | Cover customers with no National ID, or NIDAS downtime |
| Produce an authentication confirmation you can keep | Screen the person against sanctions or PEP lists |
| Support risk-based tiering | Monitor transactions after onboarding |
Above all, mule accounts worry fraud teams. A real person can pass authentication and still open the account for someone else, often for a fee. Authentication proves identity, not intent. So keep transaction monitoring and your money mule red flags in place, and watch for the same face behind many accounts.
Liveness still matters too, mainly in flows NIDAS does not cover. Your fallback path for customers without a National ID still relies on an ID image and a selfie. Yet that selfie can be a replayed video or a deepfake. Even inside the NIDAS flow, ask PSA and your integrator which party runs presentation-attack checks on the face capture, rather than assuming someone does.
NIDAS Readiness Checklist for BSP-Supervised Institutions
Use the draft period for work that does not depend on the final wording. Here is the checklist we would run, in this order.
1. Map every onboarding and updating touchpoint
First, list each channel where you collect or change identity data. That means app onboarding, branch account opening, agent or partner channels, and re-KYC triggers such as a change of name or address. Account updating is the step teams tend to forget, because it sits in servicing rather than in the onboarding funnel.
2. Close the gaps against M-2025-012 first
BSP already requires National ID Check, and it would be the interim tool under the draft. So confirm that every branch accepts all three National ID formats and runs the QR check. Staff should also know that a Digital National ID shown on a phone is valid.
3. Prepare the PSA application package
Under the draft, a complete application is what makes you compliant on day one. Name an owner, then gather the documents PSA asks of relying parties. Next, open the conversation with PSA’s Use Case Development and Managed Services unit, which BSP named as the contact point in M-2025-012. Start early, since Phase 1 would have only three months.
4. Write a tier policy for each product
For every product, record the tier, the reason, and who approved it. Then revisit the table when limits or risk ratings change.
5. Design the fallback flow

Decide what happens when the customer has no National ID, when NIDAS times out, or when authentication fails. The draft allows other valid IDs in the Philippines on a risk-based basis. So define which IDs you accept, which record checks back them, and when a case goes to manual review. Meanwhile, make the switch painless: a customer who fails eVerify should move to ID upload without starting over.
6. Update consent and privacy notices
Tell customers that you will authenticate them against PSA records, and get consent where it is your lawful basis. Then set a retention period for NIDAS confirmation records. Philstar reported that the draft lets BSIs keep these records, subject to data privacy and security rules. Your Data Privacy Act duties for KYC still apply in full.
7. Log every decision for audit
In particular, store the tier used, the confirmation reference, the timestamp, and the reason for any fallback. BSP plans to track onboarding status through the PSA, yet that only shows you applied. Your own logs show the rule works at branch and app level.
8. Test the integration path with your vendors
Decide whether you connect to National ID eVerify directly or through your existing eKYC stack. Then test downtime handling before go-live. A NIDAS outage should queue cases or route them to fallback, never approve them unchecked.
Where an eKYC Provider Fits Next to NIDAS
In short, NIDAS onboarding is a relationship between your institution and the PSA. An eKYC provider does not replace it. Instead, it covers the parts NIDAS leaves open, especially fallback and selfie checks.
For example, Verihubs runs ID verification against official records for the PhilSys National ID, LTO driver’s licenses, SSS and NBI Clearance. That gives your fallback flow a record check when a customer brings a driver’s license instead of a National ID. Pair it with liveness detection against spoofed selfies, which uses active or passive checks to reject photos, videos and masks before a face match. For the request and response detail, our guide to the PhilSys verification API walks through the flow.
In fact, banks are not waiting for the final text. BPI signed a subscription contract with the PSA for NIDAS, and PhilID holders can now open an account in its app without uploading an ID photo, according to BPI’s press release. Similarly, Maya says it integrated National ID eVerify and finishes verification with a video selfie. Both show the pattern the draft expects: authentication first, with a selfie check and a fallback around it.
Frequently Asked Questions
Is the BSP NIDAS memorandum final?
Not as of 19 November 2026. BSP released it as a draft in August 2026, and no final memorandum appears in the BSP issuances list yet. The three- and six-month windows start only once BSP issues the final text.
Who must integrate with NIDAS first?
Under the draft, Phase 1 covers universal and commercial banks with retail banking services, digital banks, e-money issuers and VASPs, with three months from issuance. Everyone else follows in Phase 2, with six months.
Can banks still accept other IDs after NIDAS integration?
Yes. The draft keeps a risk-based path for other valid IDs when a customer has no National ID or when NIDAS is unavailable.
What is the difference between National ID Check and National ID eVerify?
National ID Check, at everify.gov.ph/check, confirms that a presented National ID is genuine by scanning its QR code. National ID eVerify is the gateway to NIDAS, which authenticates the person against PhilSys records.
Does NIDAS replace liveness detection and face matching?
Not fully. NIDAS confirms the identity record, but fallback flows still rely on ID images and selfies. Fraud teams also still need defences against mule accounts and replayed or deepfake selfies.
BSP National ID Integration Starts With the PSA Application
The draft NIDAS rule is short, but its lead time is tight. Phase 1 institutions would get three months, and the clock measures a complete PSA application, not a polished integration. So finish the work that survives any final wording now: the touchpoint map, National ID Check in every branch, a tier policy, the fallback flow, consent wording and audit logs. Then, when BSP signs the memo, you file and build instead of starting from zero.
Planning your NIDAS fallback and selfie checks? Talk to Verihubs about your onboarding flow.

and experience faster,
smarter verification with us