Getting a borrower's Starpresta loan record out, with consent

Starpresta advertises loans of $500 to $30,000 MXN deposited in about five minutes, with terms quoted at 91 to 180 days, per its Play Store listing. Behind that pitch sits a per-borrower credit record: an active loan, a peso-level amortization plan, a stream of repayments, and a standing that the app says it reports to credit agencies. That record is the thing worth wiring into a lending desk, a collections tool, or a personal-finance product — and the borrower can authorize you to read it.

The clean way to reach it is a client that signs in with the borrower's consent and reads the same screens they see. We build that client, wrap the loan and repayment surfaces, and hand you code you can run. The sections below name what is behind a Starpresta account, the route we would take, and what ships.

What sits behind a Starpresta account

These are the surfaces the app exposes to a signed-in borrower, mapped to where they originate and what an integrator does with each.

Authorized ways in

Three routes are realistic for this app. They differ in what they reach and how much we maintain them.

Borrower-consented interface integration

With the borrower's authorization, we capture and re-implement the app's authenticated traffic — the login and OTP step, the session token, and the calls behind the loan, schedule and repayment screens. This reaches everything the borrower can see. Effort is medium; durability depends on the app's release cadence, so we add a re-check step that flags a changed surface before it breaks your sync. This is the one we would build first, because it is the only route that is live today and it covers the whole record.

Regulated open-finance read

Mexico legislated open finance in 2018, but the transactional tier that would let a third party read a borrower's loan data through a sanctioned channel has no secondary regulation yet (more in the consent section). We track this so a client can move onto it once it exists; for now it is not a path you can ship on.

Borrower-authorized account & native channels

Where a borrower wants to share their own data directly, we can work from authorized account access plus anything the app or its support desk exports. Narrower than route one, useful as a supplement or a fallback.

What lands in your repo

The deliverable is code that runs, not a slide deck. For Starpresta that means:

• A runnable Python client (Node.js on request) wrapping sign-in, active_loan(), the amortization schedule, repayments, and bureau standing.
• A sync worker that pulls on a schedule and accepts a webhook on payment or disbursement events, keying each installment by contract and due date so the same row is not written twice.
• An automated test harness seeded with the app's own worked example loan, so a changed field shows up under test rather than in your dashboard.
• An OpenAPI description of the surfaces we implement, plus an auth-flow report covering the OTP login and token chain.
• Interface documentation and a short data-retention and consent note for the PII involved.

The runnable client and the sync worker are the headline; the spec, the auth-flow report and the compliance note travel with them.

A worked example: the loan-summary call

Illustrative shape of the Python client. Exact paths and field names are confirmed against captured traffic during the build, not asserted from this page.

from starpresta import Client, ConsentExpired

# consent_token comes from the borrower's own login + OTP step
cli = Client(consent_token=BORROWER_CONSENT)

loan = cli.active_loan()              # the borrower's current credit
print(loan.principal_mxn)            # e.g. 10000
print(loan.apr_pct)                  # APR disclosed for this contract
print(loan.term_days)                # e.g. 120

for cuota in loan.schedule:          # one row per installment
    print(cuota.due_date, cuota.amount_mxn, cuota.status)

try:
    standing = cli.bureau_status()   # what gets reported to the credit agency
except ConsentExpired:
    cli.refresh_consent()            # re-prompt the borrower before the token lapses
    standing = cli.bureau_status()

One record, normalized

We flatten the loan, its fees and its schedule into one object your services can consume. Numbers below follow the app's own example — a 10,000 MXN loan over 120 days.

{
  "loan": {
    "principal_mxn": 10000,
    "term_days": 120,
    "apr_pct": 182.5,
    "fees": { "commission_pct": 6, "vat_pct": 16 },
    "schedule": [
      { "due_date": "2026-07-02", "amount_mxn": 2824, "status": "pending" }
    ],
    "bureau_reported": true
  }
}

What we handle on this build

A few things about Starpresta specifically that we account for, so you do not have to:

• We reproduce the fee math the borrower sees — interest, commission, and 16% VAT layered onto principal — so the amortization we expose reconciles to the in-app total rather than drifting from it.
• The listing quotes 91 to 180 days, but third-party reviews report much shorter real-world cycles of roughly one to two weeks. We design the sync to read the actual due dates on the contract instead of trusting the headline term, so reminders fire on the right day.
• The flow collects an INE/IFE identity and links a bank account the borrower has held for at least a year. We scope the consent record to cover that linkage and keep the PII data-minimized, holding only the identity fields a given use actually needs.

Consent and the Mexican rulebook

Starpresta is described in public listings as a SOFOM E.N.R. — a non-bank lender that registers with CONDUSEF and reports payment behavior to the credit bureau, rather than one supervised directly by the CNBV. That shapes the data: there is a reported credit standing to capture, and disbursement runs over SPEI.

On access, the honest position is that the borrower's own authorization is the dependable basis. Ley Fintech Article 76 set up an open-finance framework and Banxico and the CNBV are the named authorities, but only the open-data tier — public product and rate information — is actually in force. The secondary rules for sharing aggregate and transactional data were never published; entrepreneurs reportedly filed an amparo against the regulators over that delay in early 2026. So a sanctioned open-finance read of a borrower's Starpresta loan is not something you can build on today. We work from consented, logged access to the borrower's own records, under Mexico's personal-data law (LFPDPPP), with consent records kept and an NDA in place where the engagement needs one.

What the app screens show

Store screenshots of the borrower-facing flow. Open one to view it full size.

The Mexican lending-app neighborhood

Apps in the same short-term-credit space, each holding a comparable per-borrower record that a unified integration could read side by side. Listed for context, not ranked.

• Kueski — installment loans and buy-now-pay-later in Mexico; holds repayment plans and a per-user credit line.
• Baubap — a Mexican fintech offering small online loans without a bureau check, with loan and repayment history per user.
• Creditea — a revolving credit line where the user draws as needed; balance and draw history live behind the account.
• YoTePresto — a peer-to-peer lending platform with larger personal loans and amortization schedules per borrower.
• DiDi Préstamos — short-term loans inside the DiDi app, with disbursement and repayment records tied to the rider/driver account.
• MoneyMan — online micro-loans in Mexico with per-loan terms and a payment ledger.
• Cozmo — a consumer micro-loan app (formerly Dina Joy) holding loan status and repayment data per user.

How these notes were put together

Checked on 2026-06-02 against the app's Play Store listing and public Mexican fintech and consumer-credit sources. The loan terms, fees and worked example come from the listing; the regulatory picture from the open-finance and SOFOM sources below.

• Starpresta: Crédito Seguro — Google Play listing
• Chambers Fintech 2025 — Mexico (open finance, Art. 76)
• FinTech Futures — CNBV legal action over open-finance rule delays
• CONDUSEF — on SOFOMES E.N.R.

Notes compiled 2026-06-02 by OpenFinance Lab's engineering team.

Questions integrators ask about Starpresta

Can you keep a borrower's outstanding balance and next due date in sync on our side?

Yes. We build a client that reads the active loan and its amortization schedule, then run it on a schedule or trigger it on payment events, so your copy of the balance and the next due date stays current without a person opening the app.

Mexico's open-finance transactional rules still aren't published — so what is the legal basis for reading this data?

The dependable basis is the borrower's own authorization. Ley Fintech Article 76 set up an open-finance regime, but only the open-data tier is in force; the transactional tier's secondary rules remain unpublished. So we work from consented, logged access to the borrower's own records, under Mexico's data-protection law.

Starpresta reports to the credit bureau — does that change what we can read?

It mainly adds a field worth capturing. The app states it shares repayment behavior with credit agencies, so the borrower's reported standing is part of the record we can surface alongside balance and schedule.

What does one row of a Starpresta amortization schedule contain?

Per the app's worked example, an installment carries a due date, the peso amount, and the split behind it — principal, interest, commission and 16% VAT — which is what we normalize into a single schedule object.

Working with us

Most Starpresta builds land in one to two weeks. You can take it as delivered source code — the client, the sync worker, the tests and the docs — from $300, paid only once it is in your hands and working; or skip hosting it yourself and call our endpoints, paying per call with nothing up front. Tell us the app and what you need from its data, and access and compliance get arranged with you from there. Start at our contact page.