Philippine Credit Bureaus: The Complete Integration Guide for PH Lenders
Three credit bureaus operate in the Philippines today. Most lenders are connected to only one. That gap costs them approvals on thin-file borrowers who would have looked perfectly creditworthy if a second data source had been queried.
This guide is for credit officers and operations leads at PH fintechs, NBFCs, rural banks, cooperatives, and BNPL providers who need a practitioner-level view of the bureau landscape: what each provider covers, how their APIs behave, what compliance requires, and how to sequence queries so you’re not burning budget unnecessarily.
Three bureaus matter in the Philippines: the Credit Information Corporation (CIC), TransUnion Philippines, and CIBI Information Inc. CIC is mandated by law, TransUnion is strongest on urban consumer profiles, and CIBI carries the deepest SME and provincial coverage. Most lenders should integrate all three and query them in a cost-optimized sequence. We orchestrate queries across all three bureaus inside a single Decisioning Canvas workflow, so you configure the logic once and we handle the routing, fallback, and cost controls automatically.
The credit information landscape in the Philippines
The Philippines formalized its credit information infrastructure with Republic Act 9510, the Credit Information System Act, signed in 2008. RA 9510 created the Credit Information Corporation as the central credit registry for the country, mandated submission from every accredited lending institution, and authorized the CIC to license private credit bureaus to access and redistribute its data.
The Bangko Sentral ng Pilipinas (BSP) oversees lending institutions and has embedded credit bureau reporting into its supervisory framework. BSP Circular 1048 formalized the integration requirements for BSP-supervised financial institutions, making bureau submission a condition of continued accreditation rather than a best-practice recommendation.
The Securities and Exchange Commission of the Philippines also extends bureau submission obligations to financing and lending companies registered under SEC MC 3-2022.
In practical terms, if you’re a registered lender in the Philippines, you are already obligated to submit credit data to CIC. The question is not whether to connect. The question is how to connect efficiently and which private bureaus to layer on top for better decisioning coverage.
The World Bank’s Getting Credit indicators have consistently highlighted the Philippines as a market where credit bureau depth is improving but where thin-file borrowers remain substantially underserved. That gap is the reason multi-bureau orchestration matters more here than in markets with a dominant single bureau.
Understanding the 5 Cs of credit is one thing; having the data to score each C is another. Bureau coverage is the data layer that makes the Character assessment tractable for first-time and returning borrowers alike.
CIC: The Credit Information Corporation
What CIC is and who runs it
CIC is a government-owned and controlled corporation. It was established under RA 9510 to serve as the central repository for credit information across all formal lending in the Philippines. Every bank, financing company, cooperative, and SEC-registered lender with an active lending portfolio must submit data to CIC as a condition of their operating accreditation.
CIC is not a credit bureau in the traditional commercial sense. It’s a public-good infrastructure layer. The private bureaus (TransUnion PH, CIBI) are licensed Special Accessing Entities (SAEs) that draw from CIC’s consolidated dataset and layer their own proprietary data on top.
Data submission requirements
If your institution is an accredited entity under CIC, you are required to:
- Submit credit information on all your active borrowers on a monthly basis (or more frequently, depending on your accreditation tier).
- Report updates on credit status, payment behavior, and loan closure.
- Maintain data accuracy and respond to subject access requests within prescribed timelines.
Failure to submit data, or submission of materially inaccurate data, can result in suspension of your CIC accreditation. Losing accreditation means losing access to CIC credit reports, which cascades into loss of access to the SAEs that draw from CIC. This is the compliance risk that most lenders underestimate until it’s too late.
What you get back from CIC
A CIC credit report contains:
- Consolidated payment history across all CIC-submitting lenders
- Outstanding balances and credit utilization
- Derogatory markers (defaults, charge-offs, court judgments)
- Basic identification verification against PhilSys and other government IDs
API and connectivity model
CIC provides connectivity through its accredited SAEs rather than a direct public API. You reach CIC data by integrating with TransUnion PH or CIBI (both are SAEs), or through a decisioning platform that holds bureau integrations already. Direct accreditation with CIC for query purposes requires a formal application process and typically takes three to six months to complete.
Coverage strengths and gaps
CIC’s coverage is strong for borrowers who have had a formal loan in the last 36 months from any accredited lender. Coverage thins out sharply for:
- First-time borrowers with no prior formal credit
- Borrowers whose only credit relationships have been with informal lenders, cooperatives that haven’t completed CIC enrollment, or remittance-only relationships
- SMEs whose primary financing has been trade credit or supplier terms
TransUnion Philippines
Background and ownership
TransUnion Philippines is a licensed SAE and a subsidiary of TransUnion, the US-headquartered global credit bureau with operations across 30+ markets. TransUnion entered the Philippines through a partnership structure and has been operating as a fully licensed bureau since the mid-2010s. The global parentage means their data science capabilities and API infrastructure are materially more mature than the other local options.
Data sources and coverage profile
TransUnion PH draws from:
- CIC consolidated data (as a licensed SAE)
- A proprietary lender consortium (banks, credit card issuers, auto finance companies)
- Telco payment data (select agreements with major telcos)
- Utility payment history (limited, but growing)
The practical result is that TransUnion PH has the strongest coverage for urban consumers with formal employment and at least one bank or credit card relationship. For Metro Manila, Cebu, Davao, and other Tier 1 urban markets, TransUnion is often the highest-yield first query.
Coverage profile at a glance
| Segment | TransUnion PH Coverage |
|---|---|
| Urban salaried consumer | Strong |
| Credit card holder | Strong |
| Auto loan borrower | Strong |
| Provincial borrower | Moderate |
| SME / sole proprietor | Moderate |
| Thin-file / first-time borrower | Limited |
API model
TransUnion PH offers a REST API with synchronous responses for individual credit queries. Batch processing is available for portfolio review and pre-screening use cases. Response latency is typically under three seconds for single-subject queries in production. Rate limits are governed by your commercial agreement.
Pricing posture
TransUnion does not publish per-query pricing publicly. Rates are negotiated by volume tier and use-case type. Consumer credit report queries are priced differently from employment verification or fraud indicator pulls. Expect per-query pricing to decrease materially as query volume increases.
CIBI Information Inc
Background
CIBI Information Inc is the oldest credit bureau operating in the Philippines, founded in 1982, well before RA 9510 formalized the credit information system. CIBI began as a trade credit reference service for the business community and built its foundational dataset on SME and commercial credit relationships, not consumer credit card data.
That origin matters for how CIBI’s coverage skews today.
Coverage profile
CIBI draws from:
- CIC consolidated data (as a licensed SAE)
- A proprietary SME and cooperative lender network
- Trade credit and supplier payment data
- Provincial and rural lender consortium data
CIBI’s comparative advantage is the borrower segments that TransUnion PH covers less well: small business owners, cooperative members, provincial borrowers, and traders with no formal consumer credit history. For a BNPL provider expanding beyond Metro Manila, or a cooperative lending to its member base, CIBI’s hit rate on profiles that TransUnion PH would return as no-hit is often meaningfully higher.
Coverage profile at a glance
| Segment | CIBI Coverage |
|---|---|
| SME / sole proprietor | Strong |
| Cooperative member | Strong |
| Provincial / rural borrower | Strong |
| Urban salaried consumer | Moderate |
| Credit card holder | Moderate |
| Thin-file / first-time borrower | Limited |
API model
CIBI offers both REST API and batch file-drop connectivity. Their REST API is production-grade but slightly higher latency than TransUnion PH on average. Batch processing is a well-established pathway and often the preferred model for portfolio-level use cases. CIBI also offers a web portal for low-volume manual queries, which can be useful during integration testing.
Pricing posture
CIBI’s pricing is also negotiated rather than published. SME bureau queries are often priced at a different tier from consumer queries. Volume discounts are available. Like TransUnion PH, expect better unit economics at higher query volumes.
Side-by-side: Which bureau does what?
If you’re sizing this up for your own stack, book a 45-minute walkthrough and we’ll run a sample loan through all three bureaus on the Decisioning Canvas in front of you, no slides.
| Dimension | CIC | TransUnion PH | CIBI |
|---|---|---|---|
| Legal basis | Mandated (RA 9510) | Licensed SAE | Licensed SAE |
| Consumer coverage | Broad (all accredited lenders) | Strong urban / formal | Moderate urban |
| SME coverage | Broad (all accredited lenders) | Moderate | Strong |
| Provincial / rural coverage | Broad (where lenders submit) | Moderate | Strong |
| Thin-file coverage | Limited | Limited | Limited |
| Data freshness | Monthly batch from submitters | Near-real-time on consortium | Near-real-time on consortium |
| API model | Via SAEs only | REST + batch | REST + batch + portal |
| Direct query access | Via SAE or accredited entity | Yes (commercial agreement) | Yes (commercial agreement) |
| Pricing posture | Via SAE pricing | Per-query, tiered | Per-query, tiered |
| Best for | Baseline compliance + broad history | Urban consumer, salary, cards | SME, cooperative, provincial |
How do coverage gaps affect your approval rate?
A lender who queries only TransUnion PH and declines on no-hit is implicitly declining every borrower whose credit history is SME-weighted or provincial-weighted. Depending on your target market, that could mean declining 20-40% of creditworthy applicants who simply don’t appear in TransUnion PH’s urban consumer dataset.
For context: the IMF’s financial inclusion research consistently shows that single-bureau reliance in emerging markets is one of the leading structural causes of credit exclusion for otherwise-creditworthy borrowers. Multi-bureau queries aren’t a nice-to-have. They’re a business case.
What are the integration patterns for Philippine credit bureaus?
There are two practical approaches to connecting your lending operation to the Philippine bureau ecosystem.
Pattern 1: Direct integration, bureau by bureau
You build a dedicated integration for each bureau. Each integration requires:
- A commercial agreement with the bureau
- A technical integration against their API (often REST, sometimes SFTP batch)
- Credential and certificate management per bureau
- Internal error handling, retry logic, and fallback behavior
- Ongoing maintenance as bureau APIs version
For a fintech engineering team with available capacity, this is achievable. The build typically takes four to eight weeks per bureau for a clean production integration. Managing three integrations means ongoing maintenance across three separate credential stores, three separate API versioning cycles, and three separate rate-limit regimes.
The operational fragility is the bigger issue. If TransUnion PH’s API goes down during peak decisioning hours and your fallback is manual, you’re declining applications or holding queues. Most lenders discover the cost of that fragility only after it happens.
Pattern 2: Orchestrated integration through a decisioning platform
You connect once to a platform that already holds bureau integrations. The platform manages credentials, rate limits, retry logic, and fallback. You configure the query logic in your decisioning policy: which bureau to query first, under what conditions to query a second bureau, and how to handle a no-hit on all three.
The architecture looks like this:
Application
│
▼
Floowed Decisioning Canvas
│
├──► CIC (via SAE pathway)
├──► TransUnion Philippines (REST)
└──► CIBI Information Inc (REST / batch)
We maintain all three connections as part of the Floowed platform. When you build a loan product policy on the Decisioning Canvas, you configure bureau query logic in plain language: “Query TransUnion PH first. If no-hit or score below 580, query CIBI. If CIBI also returns no-hit, escalate to manual review.” That policy runs against every application automatically, without engineering involvement.
This is meaningfully different from what a loan management system provides. If you’re trying to understand where the boundary sits, our piece on loan management systems vs. decisioning platforms covers the distinction in detail.
See how we connect to all three bureaus in one Canvas. Book a 45-minute walkthrough.
Common mistakes lenders make with Philippine credit bureau integration
Querying only one bureau and misreading no-hit as thin-file
A no-hit from TransUnion PH means “this borrower does not appear in TransUnion PH’s dataset.” It does not mean the borrower has no credit history. For a provincial borrower with a cooperative loan history, CIBI may return a full report on the same subject. Declining on no-hit from a single bureau is expensive: you’re declining borrowers you’d approve if you’d queried further.
Ignoring CIC submission requirements
CIC accreditation is not a one-time onboarding event. It requires ongoing monthly submission of accurate credit data. Lenders who integrate for query purposes but let submission lapse risk losing accreditation. Losing CIC accreditation means losing access to SAE-delivered CIC data. This is a compliance failure, not just a technical one.
If you’re thinking through how compliance considerations integrate with your credit policy more broadly, the 5 Cs of credit guide covers how Character and Capacity assessments interact with bureau data.
Not handling rate limits and API timeouts gracefully
Bureau APIs, like all third-party APIs, have rate limits and occasional downtime. A decisioning system that has no fallback logic will either surface errors to your front-end or silently return null data into a decision that should have been held. Either outcome is bad. Build explicit fallback handling: what happens if bureau query times out, what happens if rate limit is hit, and whether the application should auto-decline, auto-hold, or escalate.
Failing to test with realistic thin-file subjects
Integration testing with test subjects who have rich bureau profiles will tell you almost nothing about how your system behaves at the coverage edge. Test explicitly with thin-file subjects across all three bureaus. Confirm your no-hit handling logic, your fallback sequence, and your manual-review escalation path before you go live.
How we handle bureau orchestration inside Floowed
Bureau connectivity is one of 40+ integrations we maintain on the Floowed platform. You don’t build bureau connections. You configure bureau query logic.
Inside the Decisioning Canvas, you set:
- Query order: Which bureau to call first based on product type or borrower segment.
- Fallback conditions: When to call a second or third bureau (no-hit, score threshold, data staleness).
- Cost controls: Hard caps on bureau spend per application or per product.
- No-hit policy: Whether a no-hit on all three triggers auto-decline, manual review, or an alternative data pathway.
The policy lives in the Canvas. The integrations live in our infrastructure. When a bureau changes its API version, we update the integration. You don’t.
This is the same architecture that makes our loan decisioning approach different from building decisioning logic inside a loan management system or a spreadsheet-based credit memo process. If you’re using spreadsheets for credit memos today, the credit memo template generator is a practical starting point before you move to automated decisioning.
Pricing for the full platform starts at $399/month on an annual plan or $499/month on a monthly plan. Bureau query costs pass through at cost from the bureaus; we don’t mark up bureau fees. See the full pricing breakdown for what’s included at each tier.
We activate new lenders in the same week, with no professional-services engagement required. Most credit officers have their first loan running against a bureau within days of signing up. If you want to walk through the bureau configuration specifically, book a 45-minute session with our team.
Frequently asked questions about Philippine credit bureaus
Which bureau should I start with?
Start with CIC via a licensed SAE. CIC is the broadest baseline because every accredited lender in the Philippines submits to it. Once CIC is live, add TransUnion PH if your primary market is urban salaried consumers. Add CIBI if you serve SMEs, cooperatives, or provincial borrowers. For most lenders, all three should eventually be live.
Do I need to integrate all three?
You are legally required to submit to CIC if you are an accredited lender. Query access to CIC is available through TransUnion PH or CIBI as licensed SAEs, so integrating either one gives you CIC data plus that bureau’s proprietary layer. Integrating both TransUnion PH and CIBI maximizes coverage across borrower segments. For volume-sensitive lenders, the cost of a second bureau query is often recovered in the approval rate improvement on the first month’s cohort.
How long does direct integration take?
Direct integration with a single bureau typically takes four to eight weeks from commercial agreement to production go-live, assuming a capable engineering team and responsive bureau onboarding. Three bureaus sequentially could take four to six months total. Integration through a platform like ours can compress this to days because the bureau connections are already maintained.
What does bureau integration cost?
Bureau pricing is not publicly published by any of the three providers. Per-query pricing is negotiated based on volume and use case. As a rough orientation: consumer credit report queries are typically priced between a fraction of a dollar and a few dollars per query, depending on volume tier and report depth. At any meaningful lending volume, bureau costs are a small fraction of the cost of a bad loan. See the Floowed pricing page for how bureau pass-through costs work within our platform.
What if my institution is not yet a CIC-accredited entity?
Non-accredited lenders cannot legally access CIC credit reports, directly or through SAEs. The accreditation process runs through CIC directly and typically takes three to six months. During that period, you can still query TransUnion PH and CIBI for their proprietary non-CIC data layers, though coverage will be reduced. We recommend starting the CIC accreditation process as early as possible. Our team can walk you through what the accreditation requirements mean for your technical integration plan. Book a session here.
See all three bureaus orchestrated on one canvas
The fastest way to evaluate whether bureau orchestration is right for your stack is to see it run on a real application. We’ll walk you through the Decisioning Canvas, query CIC, TransUnion PH, and CIBI in sequence on a sample loan, and show you how fallback logic, query order, and cost optimization get encoded as policy without engineering tickets.
Forty-five minutes. No slides. We’ll use one of your own document samples if you bring it.
Related reading
If you’re building out your credit policy alongside your bureau integration, these pieces are worth reading in sequence:
- What is loan decisioning? covers the decisioning layer that sits above bureau data.
- Loan management system vs. decisioning platform explains why bureau queries belong in a decisioning layer, not your LMS.
- 5 Cs of credit: a modern underwriter’s guide shows how bureau data maps to each dimension of creditworthiness.
- Mambu alternatives and Encompass alternatives are useful if you’re also evaluating the broader platform stack.
Last updated 2026-05-03 by Kira, Floowed’s AI Flow Architect.