Sovereign Data Beneficiary Program

How protocol identity becomes per-user royalty.

FIDNT operates as the user's agent under Civil Code 1868. Platforms license user-consented data through the agency rail; the platform pays the user directly. FIDNT issues the signed mandate + receipt + ledger entry, and invoices its disclosed admin fee to the platform separately as service revenue. Money never enters or transits a FIDNT account. It runs on the same real engine as the rest of Fidnt: passkey login, post-quantum-signed evidence on every call (NIST FIPS 204), and a PPSR-registered creditworthiness the user can take to any lender. Below: the economic model, what each user segment earns, the three-tier subscription, and the order in which platform buyers come on.

Illustrative. All amounts in Philippine pesos (₱), all projections illustrative pending market validation. For institutional discussion only — not an offer of securities, not an investment instrument, not a financial promise.

Six revenue streams. Eighty percent to the user.

Every stream is consent-governed. Every payment produces a receipt. The platform pays the user directly; FIDNT issues the proof and invoices its disclosed admin fee separately.

Stream What it is User share Legal basis
Data Licensing Direct consent-governed data licensed to banks, fintechs, research firms. 82% RA 10173 + BSP Circular 1122
Credit Enhancement PPSR-registered creditworthiness licensed to lenders for pre-approval. 80% RA 11057 + IAS 38 ¶ 88
Identity Verification Layer 0 Genesis Record licensed to platforms requiring KYC. 80% RA 11055 + W3C DID v1.0
Data Portability Open Finance portability managed on the user's behalf. 75% BSP Circular 1122 + RA 10173 §18
Aggregate Dataset Anonymized pooled data licensed to academic, government, market research. 70% RA 10173 + GDPR Art. 89
NPC Enforcement Recovery Penalty recovery when a third party misuses data. 85% RA 10173 §§25–32 + RA 11765

The five-step program

1

Register

Mandate signed. Layer 0 Genesis Record created. Data assets registered (PPSR where applicable).

2

Verify

KYC via PhilSys. Cryptographic key bound to the bearer. Tier assigned. Consent receipt issued.

3

License

FIDNT (as agent) licenses user data to buyers on stated terms. Every event logged on the receipts ledger.

4

Receipt

Buyer pays the user directly via the buyer's own rail. FIDNT issues the receipt + ledger entry. FIDNT invoices its disclosed admin fee to the buyer separately as service revenue.

5

Enforce

Any misuse triggers an NPC complaint envelope. Recovery proceeds returned to the user at 85%.

Operating discipline

Pure online operation. No office, no physical staff. Costs are infrastructure, AI, regulatory licensing, legal, and platform support — sized to revenue, not to fundraised capital.

What each user segment earns from the rail.

The same protocol primitives produce different per-user economics depending on the user's data assets and registered IP. Income tier is a side-effect; the protocol is the same.

Segment Profile Data assets IP activities Monthly user payout
T0 Unbanked · informal economy Basic identity · location · device none illustrative ₱0.3K–0.5K
T1 Informal worker · ₱5K–15K/mo income Wallet history · social commerce · basic credit behavioral none illustrative ₱1K–2K
T1+ Employed · ₱20K–40K/mo Payroll · bank · credit history · Open Finance none illustrative ₱2K–3K
T2 Freelancer / creator · ₱50K–100K/mo Multi-source income · platform behavioral · audience copyright · brand illustrative ₱4K–6K
T2+ SME owner / professional · ₱100K–300K/mo Business revenue · multi-bank · investment portfolio trade · copyright · trademark · software illustrative ₱8K–12K
T3 High value · enterprise principal · ₱500K+/mo Complex multi-institution · international · investment framework · copyright · patent · software · trademark illustrative ₱18K–24K

Per-user amounts are illustrative pending market validation. Real per-stream rates vary by buyer category, contract, and PPSR status. The 80% user share is structural — it is the agency model under Civil Code 1868, not a marketing claim.

Three tiers.

Individuals never pay. Businesses pay because the law requires them to be data-privacy compliant. And the AI agents acting on your behalf pay per action. That is how your free stays free — forever, not as a trial.

Power tools

Individuals · pay only when you use one
Pay-per-use
à la carte · no subscription · illustrative
  • IP filing helper (RA 8293 — IPOPHL guided)
  • Done-for-you NPC / credit-dispute concierge
  • Notarized SPA & signed instruments
  • Open Finance multi-account aggregation
  • Full data portfolio (all consented streams)
  • Full signed ledger export
Notify me at launch

Business & developers

Platforms · SMEs · apps · illustrative
Free to start
then ~₱1,499/mo flat — or pay-per-call
  • Free dev tier — sandbox + production keys, capped volume
  • “Sign in with fID” — DPA & AFASA compliance built in
  • Pay-per-call: verifications · sign-ins · consent checks · webhooks
  • Audit-grade ledger exports (signed JSON · CSV)
  • Dedicated technical contact
  • Per-period accounting reconciliation & roadmap reviews
Talk to us
AI agents — metered per action
Every AI agent that acts on a person's behalf must use the FIDNT agency layer — and pays per mandated, signed action. This is metered revenue from machines, never from the people they serve. The agency layer is in development.
For developers

Tax framing

Business subscriptions, per-call usage and individual pay-per-use are all service fees — VAT-eligible above threshold; no securities, no custody, no employment relationship. Royalty distribution to the user is passive income to the principal, taxed at the 20% final rate for PH residents under the agency relationship (Civil Code 1868). FIDNT issues no Form 2316; the user reports income on their ITR.

Eight buyer categories, ranked by reaction.

Some buyers come within thirty days. Some require regulatory pressure to take a meeting. The order matters: build revenue with the willing first, let regulation work on the rest.

Buyer category Initial reaction Final outcome Timeline Risk
Market research / academia Immediate interest Earliest buyer 1–3 months very low
Fintech / e-wallets Strategic interest Willing partner 1–6 months low
Insurance Eager evaluator Committed buyer 6–18 months low
Banks (PH) Cautious interest Early adopter (selected) 3–12 months low–medium
Telecommunications Commercial evaluation Selective buyer 6–18 months low–medium
E-commerce platforms Indifferent to resistant Eventual buyer 1–3 years medium
Government agencies Regulatory alignment Institutional partner 6–24 months low
Global big tech Hostile Forced compliance 2–4 years high

Engagement sequence

Approach now · 0–6 months

Willing buyers

Market research firms · IRB-compliant verified consumer data. Fintechs · Open Finance compliance acceleration + premium data quality. Insurance actuarial teams · improved loss ratio. Approach directly.

Approach next · 6–18 months

Selective buyers

Bank trust departments · charter-aligned transactions. Telcos · SIM registration compliance + churn analytics. Government sandboxes · Open Finance proof of concept.

Let regulation work · 2–4 years

Forced compliance

Big tech platforms (Meta, Google, TikTok, X) and large e-commerce (Shopee, Lazada) will not engage voluntarily. NPC enforcement and ASEAN regulatory pressure converge over the cycle. They come to FIDNT once they need a compliant licensing pathway.

The core dynamic

Push

Regulation

RA 10173 penalties up to ₱5M per violation. NPC enforcement actions accumulating. ASEAN data sovereignty frameworks tightening.

Pull

Data quality

FIDNT's verified, consented, PPSR-registered data is more valuable than scraped or assumed behavioral data. Every credit model, actuarial table, and recommendation algorithm improves with verified data.

Lock-in

Architecture

The receipts ledger creates platform stickiness. Once a user grants a mandate through FIDNT, that consent is portable, auditable, revocable. Platforms that integrate early become the standard.

§ Constants & citation

loading…

Every fiduciary numeric on this page is read from /iset_legal_constants.js at runtime — citations migrate to specific document sections once ceremonial documents are anchored at /instruments.