Reaching the loan ledger and Stash balances inside Tendo by Tonik

Every Tendo by Tonik login sits on top of a running credit ledger: an assigned credit limit, the amount drawn against it, an installment plan that can stretch to eighteen months, and a repayment status that moves on a semi-monthly cycle rather than a single monthly date. Alongside it is a savings “Tendo Stash”, a bill-payment record, and installment purchases made at partner merchants. That bundle behind one authenticated account is what a lender, an aggregator, or a payroll partner actually wants to read — and there is a defined, consented way to read it.

The data behind a Tendo account

Each row below is a real surface a Tendo user sees in the app, not a generic finance checklist.

Authorized routes to that data

Three routes genuinely apply to Tendo. They differ in durability and in what we set up to run them.

Consented open-finance access

The Philippine Open Finance Framework (BSP Circular No. 1122) is built for exactly this: customer-permissioned sharing of account and transaction data with third-party providers through APIs, with the customer keeping ownership and an opt-out. The pilot moved into post-production in early 2024 and a further Open Finance for PERA pilot launched in 2025, so the rails are real but still widening. Reachable today depends on which participants are onboarded; durability is high because the model is regulated and standardized. We handle the consent flow and participant onboarding with you.

Authorized interface integration of the app session

Tendo runs a web app at app.tendopay.ph and the Android and iOS clients. With the account holder’s authorization we analyze that session — the login, the second-factor step, the token or cookie chain, the refresh — and read the same ledger, schedule, Stash and bill views the user sees. Effort is moderate, durability is medium because front-end changes happen, and the studio sets up the consenting account or sandbox during onboarding.

User-consented credential access and document parsing

Where an account holder consents to credential-based aggregation, the same surfaces are reachable per user. As a fallback, the disclosure statement and repayment schedule the app issues can be parsed into structured records. This is the lowest-effort path and a useful supplement, not the spine.

For a build starting now, the second route carries the project: it reaches everything the user can see and does not wait on ecosystem maturity. We design it so the consent and data model line up with Circular 1122, so the work moves onto the regulated route later without a rewrite.

On the wire

An illustrative shape of the authenticated flow. Field and path names are confirmed during the build against a consenting account; treat the structure, not the literals, as the contract.

POST /api/auth/token            # session start
  body  { identifier, secret, device_id }
  -> 200 { access_token, refresh_token, expires_in, otp_required: true }

POST /api/auth/otp/verify       # semi-step 2FA
  body  { txn_id, otp }
  -> 200 { access_token, refresh_token, expires_in }

GET  /api/credit/summary        # the ledger
  auth  Bearer <access_token>
  -> 200 { credit_limit, available, drawn,
           currency: "PHP", as_of }

GET  /api/loans/{loan_id}/schedule
  -> 200 { loan_id, principal, monthly_rate, term_months, apr,
           installments: [ { seq, due_date, amount,
                             status: PAID|DUE|LATE } ] }   # semi-monthly cadence

GET  /api/stash                 # savings side
  -> 200 [ { stash_id, type: OPEN|LOCK, balance,
             accrued_interest, currency: "PHP" } ]

# 401 -> refresh with refresh_token; honor expires_in,
# back off on 429, and re-validate the schedule after any
# front-end version bump (handled in maintenance).

What lands in your hands

Everything below is scoped to Tendo’s actual surfaces, not a generic kit.

• An OpenAPI 3 specification covering the auth exchange, the credit summary, per-loan schedule, Stash, bill and merchant-order reads.
• A protocol and auth-flow report: the login and OTP step, bearer or cookie chain, refresh behavior and session lifetime as they actually run.
• Runnable source in Python and Node.js for each endpoint, with pagination, retry, and PHP currency handling wired in.
• Automated tests, including fixtures for the semi-monthly schedule and for loans priced at 0% at selected merchants.
• A normalized model that folds loan, installment, Stash, bill and order records into one schema, with the Templetech vs. Tonik entity ownership made explicit.
• Interface documentation plus data-retention and consent-record guidance aligned to the Data Privacy Act and NPC expectations.

Consent under Circular 1122 and the Data Privacy Act

Two regimes sit over a Tendo integration. BSP Circular No. 1122 defines the Open Finance model: data is shared on customer permission, the customer keeps ownership of their customer and transaction data, and consent can be modified or withdrawn through opt-in and opt-out mechanisms, with the Open Finance Oversight Committee setting ecosystem standards. Separately, Republic Act No. 10173, the Data Privacy Act of 2012, and the National Privacy Commission govern how that personal data is collected, stored and minimized — Templetech states its own processing is run to that Act. We operate the same way: access is authorized or user-consented, every pull is logged against a consent record with a defined scope and expiry, data is minimized to the fields the use case needs, and an NDA covers the engagement where the client needs one. Lending here also sits under SEC oversight and SEC Circular No. 3, series of 2022 on rate and fee ceilings, which is why the terms fields matter and are carried through faithfully rather than flattened.

Engineering notes we plan around

Specific things about Tendo that shape the build, each handled on our side:

• Two entities, one app. The platform is operated by Templetech Finance Corp. while loans are funded by Tonik Digital Bank from June 2025 (per the app’s disclosure). We map record ownership to the correct entity so loan ledger data and Stash deposit data reconcile and audit cleanly.
• Semi-monthly, not monthly. Installments fall twice a month, with semi-monthly amounts that differ from a naive monthly split. We model the schedule on the real cadence so repayment-status syncs and arrears flags do not drift by a fortnight.
• Per-loan pricing. Rate, term and APR move with the borrower’s risk profile and the merchant context, including 0% at selected merchants. We capture terms per loan instead of assuming one product, so analytics stay accurate across a mixed book.
• Front-end drift. A consumer app ships often. A version-change watch is part of how we maintain the integration, so a portal refresh is caught and re-validated rather than silently breaking a downstream sync.

Where integrators put this to work

• A payroll or employer partner reconciling salary-deduction loans against Tendo’s employer-channel repayment schedule each pay cycle.
• A lender pulling a consenting applicant’s credit limit, utilization and arrears status into its own underwriting model.
• A personal-finance app aggregating the Tendo Stash balance and bill history into a user’s full cash-flow picture.
• A merchant settlement tool matching partner-merchant installment orders back to the credit draw that funded them.

Cost and cycle for this build

A Tendo build — token and OTP capture, the credit-summary, schedule, Stash and bill reads, a normalized model and tests — runs a one-to-two-week cycle. You can take it as runnable source code from $300, delivered with the spec, tests and documentation, and paid only after delivery once you are satisfied with it. Or run it as a hosted API where you call our endpoints and pay per call, with no upfront fee. You bring the app name and what you need from its data; access, sandbox and compliance arrangements are sorted with you as part of the work. To start or ask about a specific surface, tell us what you need on the contact page.

App screens

Reference screenshots from the public listing, used to confirm the surfaces above.

What was checked, and when

This mapping was put together in May 2026 from the app’s own Play and App Store listing and loan-terms text, the Tendo privacy policy, BSP’s Open Finance materials including Circular No. 1122, and reporting on Tonik Digital Bank’s lending and the Open Finance PERA pilot. Primary sources opened: BSP Circular No. 1122 (Open Finance Framework, PDF), BSP Open Finance PH, BusinessWorld on the Open Finance for PERA pilot, and the Tendo privacy policy.

Mapped by the OpenBanking Studio integration desk, May 2026.

Similar apps in the Philippine credit and wallet space

Same-category apps an integrator often unifies alongside Tendo. Named for ecosystem context only, with no ranking implied.

• Tonik — the Tonik Digital Bank app itself, holding deposits, time deposits and loan accounts; closely related since it now funds Tendo loans.
• Cashalo — a credit and BNPL app with loan balances and repayment schedules comparable to Tendo’s ledger.
• Tala — short-term cash loans with per-user limit and repayment data.
• Home Credit Philippines — point-of-sale installment financing with order-level and repayment records.
• Digido — online cash loans with limit, due-date and status fields.
• BillEase — BNPL with merchant-linked installment plans and a payment history.
• GCash (GLoan) — wallet-embedded lending with balances, loan limits and transaction history.
• Maya — a digital bank and wallet with deposits, credit and a transaction ledger.
• JuanHand — an SEC-registered online lending app with loan and repayment records.

Questions integrators ask about Tendo

Does the integration cover both the loan side and the Tendo Stash savings side?

Yes. The credit ledger and the Tendo Stash both sit behind one login, so a single authenticated session reaches them together. Because the platform is operated by Templetech Finance Corp. while loans are funded by Tonik Digital Bank from June 2025 (per the app’s own disclosure), we map which entity owns which record so loan balances and stash balances reconcile cleanly.

How does BSP Circular 1122 shape a Tendo by Tonik integration?

BSP Circular No. 1122 frames the Philippine Open Finance approach: customer-permissioned data sharing among banks, financial institutions and third-party providers, with the customer retaining ownership of the data and an opt-out at any time. We build the consent capture and revocation handling to that model, and treat the regulated route as the durable target as ecosystem participants onboard.

Can you return the semi-monthly repayment schedule and the APR per loan?

Yes. Tendo bills on a semi-monthly cadence rather than a single monthly date, and rate, term and APR vary per loan (0.00%-4.00% monthly, 2-18 month terms, APR up to 48.00% per the app’s loan terms). We capture the schedule per installment and the terms per loan rather than assuming one fixed product.

We already hold consent from our own Tendo by Tonik users — what is the path from there?

That shortens things. With the account holder’s consent in hand we build the integration directly against the consented session, normalize the ledger, schedule, stash and bill records, and hand back runnable clients plus tests. Access details are arranged with you during onboarding.