Integrating SAVii: salary loans and Netbank deposits

Every active SAVii loan is repaid by deduction from the borrower's next payroll cycle, not from the borrower's bank account — which is the first thing that shapes how its data is reached. The app sits between a sponsoring employer and that employer's staff, so the "account" the data hangs off is a salary-linked one, with the employer footing onboarding and the employee getting funds inside 24 working hours after approval (per the app's own description). Anything an integrator wants out of SAVii — loan balance, salary advance, repayment schedule, time-deposit, employer linkage — needs a route that respects that triangle.

Data that lives behind a SAVii login

The surfaces below are the ones a SAVii integrator most often needs to model. Names follow how the app itself frames them.

Domain	Where it originates in the app	Granularity	What an integrator does with it
Active loans	Loans module, employee dashboard	Per loan: principal in PHP, term in months (3–60), monthly interest (0.5–3.5%), service fee, bank fee	Reconcile against payroll deductions; feed APR/total-cost panels
Salary advance	Advance module — separate product from term loans	Per advance: amount, sponsor, status, payback on next payroll cycle, 0% interest	Track zero-interest 30-day advances against next salary
Repayment schedule	Loan ledger	Per scheduled deduction: amount, payroll date, status (pending/posted)	Pre-warn HR/payroll of upcoming deductions; arrears handling
Time deposits	Savings module — held on partner Netbank's books, PDIC-insured up to ₱500,000 per the app's savings page	Per deposit: principal, 6% per annum, 180-day fixed term, maturity date	Model deposits as a Netbank-side asset, not a SAVii liability
Employer linkage	Profile / onboarding	Employer name, company ID, plan tier	Scope eligibility and pricing per sponsor — see build notes
KYC artefacts	Onboarding	Government ID, two most recent payslips, company ID	Feed downstream identity / lending-policy checks
Disbursement instruction	Approval flow	Target bank account or e-wallet, disbursed amount net of fees	Mirror the disbursement leg in the integrating system

A sample call against the loan ledger

Pseudo-code below — request shapes and field names are illustrative and are confirmed during the build against a consenting account. Auth is established via the OAuth / token / cookie chain documented in the auth-flow report shipped alongside the source.

# Python — illustrative SAVii integration. Verified against a
# consenting account during build; do not assume field names are
# stable across portal releases (re-validation is part of maintenance).

import requests

session = requests.Session()
session.headers.update(get_auth_headers())   # see auth-flow report

# 1. Active loans for the signed-in employee
loans = session.get(
    "https://api.savii.io/v1/me/loans",
    params={"status": "active"},
).json()

for loan in loans.get("loans", []):
    principal     = loan["principal_php"]
    term_months   = loan["term_months"]               # 3 .. 60
    monthly_rate  = loan["monthly_interest_rate"]     # 0.005 .. 0.035
    next_due      = loan["next_deduction"]
    print(principal, term_months, monthly_rate,
          next_due["amount_php"], next_due["payroll_cycle"])

# 2. Salary advances live on a separate resource: 0% interest, 1 month.
advances = session.get("https://api.savii.io/v1/me/advances").json()

# 3. Time deposits are held on partner Netbank's books and surfaced
#    via SAVii; we keep the linkage explicit in the response.
deposits = session.get("https://api.savii.io/v1/me/deposits").json()
for d in deposits.get("deposits", []):
    assert d["custodian"] == "Netbank"
    assert d["pdic_insured"] is True

What you get from us

The build is shipped as a working integration, not a feasibility memo. For SAVii, that has five parts.

An OpenAPI 3 specification for the loan, advance, repayment-schedule, deposit, and employer-linkage resources — typed and annotated for downstream code generation.
An auth-flow report covering the actual OAuth / token / cookie chain SAVii's session uses, the refresh path, and how the Salesforce-backed help center (savii.my.site.com) interacts with the main app's session, where relevant.
Runnable source — Python and Node.js — for the read endpoints above plus the disbursement-status read and KYC-artefact upload (where the buyer needs it).
Automated tests pinned to a consenting account: golden-path runs against the live portal plus a recorded-response suite that does not require credentials, so the build does not silently rot.
Interface documentation aimed at a maintainer who was not on the build: known portal quirks, plan-tier matrix, the Netbank-deposit boundary, error shapes, retry guidance.

Authorized routes into SAVii data

Three routes apply here in practice. The first is the spine; the others are a forward path and a fallback.

Authorized interface integration under user or sponsor consent

The signed-in SAVii session — employee-facing app, employer dashboard — is where the live data lives. With explicit authorization from the buyer (the employee for their own data, or the sponsoring employer with NDA for population-level data), we analyze the traffic, model the resources, and ship the integration. Effort is in the range of one to two weeks; durability is high so long as a re-validation step is wired into maintenance.

BSP Open Finance — kept warm for the longer run

BSP Circular 1122 (2021) sets a tiered, voluntary Open Finance Framework; the Open Finance Pilot supervised by the Open Finance Oversight Committee Transition Group went live in late 2023, focused on payments and savings use cases with participating banks and a small set of fintechs. SAVii is a SEC-registered financing company, so this route is not the present-day path — but the deposit and payment surfaces are the ones the framework is expected to widen into, and the integration we ship is built so a future Open Finance link can replace the interface read without rewriting the rest of the system.

Native export from the employee dashboard

The in-app dashboard shows the borrower their schedule and balances. For one-shot reporting that does not need to refresh, a screen-scrape or a CSV pull from the dashboard can be the lowest-friction path. We use it as a fallback and as a cross-check against the integration's outputs, never as the primary read for a recurring sync.

The recommendation, for SAVii: lead with the interface integration; cross-check with the dashboard during build; design the schema so Open Finance can slot in later without a re-platform.

SAVii operates as a SEC-registered financing company — the app itself cites PSEC registration number CS201628816 and Certificate of Authority number 1288, and points to BSP Circular 1133 and SEC Memorandum Circular No. 03 s. 2022 as its loan-terms and interest-rate authorities. We treat both as binding on the integration: rate ceilings, disclosure obligations, and the requirement that consumers see all transaction details before agreeing to a loan flow through into how we surface fields.

On data, the Philippine Data Privacy Act of 2012 (Republic Act 10173), administered by the National Privacy Commission, is the dependable basis for any consumer-side pull — combined with the consumer's or sponsor's own explicit authorization. We log consent, scope it tightly (which resources, for how long, with which refresh), and the integration honours revocation. Population-level work for an employer-buyer runs under NDA with a documented purpose, and data is minimized to what the agreed use case actually needs.

Build notes specific to SAVii

Plan-tier dispersion. SAVii's monthly interest sits anywhere from 0.5% to 3.5% and APR from 6% to 24% (per the app's own description), and which band a borrower lands in depends on the sponsoring employer and the employee profile. We map the per-sponsor plan rules during the build so two participants on different employers get correctly scoped responses, instead of a single average that hides the dispersion.
Netbank-held deposit boundary. Time deposits are not on SAVii's own books — they are PDIC-insured deposits held on partner Netbank's books, surfaced through SAVii. We model the deposit as its own resource with the custodian field explicit, so downstream code never folds a Netbank-side asset into a SAVii-side liability or vice versa.
Advance vs term loan. The 30-day, 0%-interest salary advance and the 3–60 month interest-bearing term loan share a borrower but are distinct products. We ship them as separate object types in the OpenAPI spec so amortization, fee model, and repayment cadence stay clean.
Salesforce help-center surface. The borrower support flow runs on a Salesforce site (savii.my.site.com) that is a separate origin from the main app. When the integration needs ticket / case state — for instance, to know a loan is in dispute — we factor that surface into discovery rather than assuming the main app exposes it.
Two-cycle audit fits this portal well. Because deductions are payroll-cycle bound, scheduling a re-validation pass at roughly one cycle out catches portal changes before they show up as a missed deduction post; we wire that into maintenance at delivery.

What we checked

This page was put together from primary sources: the SAVii Play Store listing and the company's own savings, loans, and employer pages; the BSP's Open Finance framework material and its 2023 pilot announcements; and the SEC's financing-company memorandum cited by the app. The integration shape recommended above reflects routine work the studio runs against employer-payroll-linked credit apps in Southeast Asia — not desk speculation.

Same-shape Philippine apps in the integration landscape

Apps in roughly the same Philippine consumer-credit and salary-finance space. Each holds the kind of authenticated, per-user records an integrator usually wants to unify. Names listed as ecosystem reference, not ranking.

Tala — short-tenor unsecured cash loans with an in-app ledger of disbursements and repayments.
Cashalo — installment and cash-loan products with a per-user repayment schedule and KYC documents.
Home Credit Philippines — point-of-sale financing and cash loans with detailed amortization data per contract.
Robocash — short-term lending with an authenticated borrower portal and repayment history.
Pera247 — quick-cash lending with per-loan status and document submission.
Digido — short-term credit with a customer dashboard showing approved limit, drawn balance, and due date.
Tonik — a Philippine digital bank with deposit, time-deposit, and lending records behind one login.
RFC (Radiowealth Finance Corporation) — consumer financing with per-customer account-level data accessible to the borrower.
JuanHand — mobile loans with an in-app borrower record of loans and payments.
Moneycat — small-ticket consumer lending with a per-user repayment ledger.

Questions integrators usually ask about SAVii

Can SAVii data be reached without going through the partner employer?

Yes, when the integration is for the employee themselves. With the employee's own credentials and explicit consent we can pull their loans, advances, repayment schedule, and time-deposit data directly. When the buyer is an HR or finance team that needs population-level data, the sponsoring employer is brought in during onboarding — that step is part of our work, not a wall the client has to clear first.

How is the Netbank-held time deposit handled separately from the loan balance?

SAVii's savings product is held on partner Netbank's books and is PDIC-insured to the regulator's standard cap, as the app states on its savings page. We model the deposit as its own resource with the Netbank linkage explicit, so the 6% per-annum 180-day deposit never gets summed with — or confused with — the SAVii-side loan ledger in downstream systems.

Does the BSP Open Finance pilot give us a direct API into SAVii today?

Not directly. BSP Circular 1122 (2021) sets the Open Finance Framework on a tiered, voluntary basis and the pilot — supervised by the Open Finance Oversight Committee Transition Group — went live in late 2023 with banks and a small set of fintechs. SAVii is a SEC-registered financing company; its primary path today is authorized interface integration under user or sponsor consent, with Open Finance kept warm as a longer-run option as the framework expands.

How do you keep the 0% salary advance and the interest-bearing loan from colliding in one schema?

They live on separate object types. The 30-day salary advance carries a zero monthly interest rate and a single deduction; the term loan carries a 0.5–3.5% monthly rate (per the app's own description) and a full amortization schedule with service and bank fees. We surface both under one borrower identity but never under one resource — that distinction is in the OpenAPI spec we ship.

What happens when SAVii changes its portal or app and our integration breaks?

A re-validation pass is part of the maintenance plan we set up at delivery: a small recurring check that the auth flow, the loan ledger fields, and the deposit response shape still match. When a portal release moves a field or changes an endpoint, we adjust the source we shipped, re-run the tests, and re-publish. That sits on top of the build, not as a separate engagement.

Source-code delivery for the SAVii integration starts at $300 and is invoiced after the build runs cleanly against your account; the hosted-API model bills only per call with no upfront fee. The cycle for either is one to two weeks against a consenting employee account, with the sponsoring employer brought in during onboarding when population-level data is in scope. To start, send the data shape you need and any sponsor constraints via /contact.html.

App profile — SAVii - Salary Finance App

SAVii (package id io.savii.android, per its Play Store listing) is a Philippine salary-linked credit, salary-advance, and employee-savings app published by New Cross Credit and Financing Gate PH, Inc., with the SAVii word mark a registered trademark of Uploan Asia PTE Ltd. The platform serves partner employers in the Philippines — the app describes itself as supporting nearly half a million partner employees — with term loans of 3 to 60 months at 0.5–3.5% monthly interest, 30-day salary advances at 0% interest, and time deposits held on partner Netbank's books at 6% per annum on a 180-day term, PDIC-insured up to ₱500,000 per the app's own description. Loan repayments are made by deduction from the borrower's salary; the app cites BSP Circular 1133 and SEC Memorandum Circular No. 03 s. 2022 as its loan-terms and interest-rate authorities. SAVii is a third-party app referenced here strictly for integration-engineering purposes.