Getting structured loan data out of Easybuy

A single Easybuy account carries a phone-financing loan from NGN 20,000 up to NGN 1,000,000, a down payment of at least 30 percent, and a repayment plan running 91 to 365 days — figures the app states in its own Play Store listing. That is the shape of the data worth integrating: not a balance, but a structured installment ledger tied to a specific device, an approval decision, and a Nigerian borrower's identity. The app runs an in-store, agent-mediated flow across a network the operator describes as more than 2,000 stores, with a Jumia checkout tie-in noted in market coverage. Reaching that data cleanly is what this page is about.

Easybuy is operated by Newedge Finance Limited, per the app's own listing. The records sit behind an authenticated account and a backend the app talks to over its API. We map that interface and hand back a documented, runnable feed.

Bottom line: the valuable surface is the loan record and its installment schedule, both held inside Easybuy's own backend. We read those through authorized interface integration of the app traffic, and bring in Nigeria's open-banking consent route for the linked bank account when you need the repayment debits reconciled against the schedule. For most integrators the first route is the one that does the real work, because the schedule, the device record, and the approval state only exist inside Easybuy — the bank only sees a debit. We recommend building on the app-traffic integration and layering the bank-side consent feed on top where reconciliation matters.

What an Easybuy account holds

Each surface below is something a logged-in account exposes through the app. The granularity column is what an integrator actually gets per record.

Authorized routes to the data

1 — Interface integration of the app's traffic

This is where the loan ledger, the schedule, and the device record live. Working under your authorization, we capture and document the Easybuy client's calls — login and token refresh, the active-loans query, the installment detail — and turn them into a stable interface. Reach: the full per-user loan picture. Effort: moderate, dominated by mapping the auth chain and the loan state machine. Durability: good, with a small parser touch-up when the app ships a new build. Setup is arranged with you during onboarding; the build runs against a consenting account.

2 — Open-banking consent for the bank leg

Repayments are debited from a linked Nigerian bank account. Under the CBN Operational Guidelines for Open Banking, that account's movements can be read through a registered API provider with the customer's recorded consent. Reach: the money side — debits, balances, settlement timing — not the loan terms. We handle provider onboarding and the consent flow as part of the project, and pair this feed with route 1 so a payment can be matched to the installment it clears.

3 — User-consented credential access

Where you act for the borrower directly, a consumer can authorize access to their own Easybuy view. We build the session handling and read the same loan surfaces on the user's behalf, with consent recorded and revocable. This suits consumer-facing tools that aggregate a person's own credit obligations.

A look at the loan-list call

Illustrative shapes — field names and the exact auth chain are confirmed during the build against a consenting account, not taken from any published document.

# Illustrative only — confirmed during the build, not a published spec.

POST /api/v1/auth/login
  { "phone": "+234XXXXXXXXXX", "otp": "######" }
  -> 200 { "access_token": "...", "refresh_token": "...", "expires_in": 3600 }

GET /api/v1/loans?status=active
  Authorization: Bearer <access_token>
  -> 200 {
       "loans": [
         {
           "loan_id": "LN-...",
           "principal_ngn": 100000,
           "down_payment_pct": 30,
           "tenor_days": 365,
           "apr_band": "12-36",
           "device": "Tecno / Infinix / iPhone ...",
           "schedule": [
             { "due": "2026-07-01", "amount_ngn": 9583.33, "paid": false },
             { "due": "2026-08-01", "amount_ngn": 9583.33, "paid": false }
           ]
         }
       ]
     }

# 401 on an expired access_token -> refresh, then replay the request.
# We wrap token refresh and back-off so a long export doesn't stall.

What lands in your repo

The deliverable is a working integration, not a report. For Easybuy that means:

• An OpenAPI/Swagger specification covering the loan-list, loan-detail, repayment-schedule and auth endpoints as we map them.
• A protocol and auth-flow report — the OTP login, the bearer token, the refresh chain, and how errors surface.
• Runnable source for the key reads (Python and Node.js), including token refresh and paging over a borrower's loans.
• Automated tests against the documented responses, so a future app build that breaks a field is caught early.
• Interface documentation a second engineer can pick up without re-deriving the flow.
• Data-retention and consent guidance scoped to NDPA handling of the BVN and other identity fields.

Consent and the Nigerian rulebook

Two instruments apply here, and they apply to different parts of the picture. Identity and financial records pulled from Easybuy fall under the Nigeria Data Protection Act 2023, enforced by the NDPC; the Act requires consent that is informed, specific and revocable, and recorded consent logs. Financial and biometric data — the BVN sits close to both — gets stricter handling under the NDPC's guidance, so we minimize what the integration touches and store identity by reference where we can. The bank-account leg, when you use it, runs under the CBN Operational Guidelines for Open Banking, which mandate a standardized, recorded consent step before any account data is shared and a tiered model that limits sensitive-data access to qualified participants. We operate authorized and logged, with NDAs where a project needs them, and consent records kept for both legs.

What we account for on this build

Two things shape an Easybuy integration that a generic balance-reader would miss:

• The flow is an in-store, agent-mediated loan lifecycle — down payment, approval, disbursement, then a fixed installment run. We model that state machine so the feed reflects where a loan actually is, not just a snapshot number.
• Repayment debits run against a linked bank account, on a CBN consent that can expire. We design the sync around the consent-refresh window and the token refresh so the repayment feed doesn't quietly stop the day a consent lapses.
• The app front end changes with promotions and partner tie-ins. When Easybuy ships a new build we re-capture the traffic and patch the parser, which we plan into maintenance rather than treat as a surprise.

Access — a consenting account, or a sponsor sandbox — is arranged with you during onboarding. It is part of the engagement, handled by us, not a hoop to clear before we start.

App screens

The store screenshots below show the surfaces we map. Select one to enlarge.

Other Nigerian BNPL apps in the same data picture

If you're aggregating consumer credit across Nigeria, Easybuy sits among several apps holding comparable installment and repayment records. Named here for context, not ranked.

• CredPal — card-and-installment BNPL holding per-user credit limits, 30-day and multi-month plans, and repayment ledgers.
• Carbon (Carbon Zero) — income-qualified installment plans alongside a broader lending and wallet history.
• Klump — installment checkout focused on education, travel and laptop financing, with partner-merchant order records.
• PayWithSpecta — Sterling Bank's BVN-linked consumer credit product, carrying application and repayment data.
• CDcare — a save-then-receive model where users pay in small installments before delivery, tracked per item.
• PayFlexi — gadget financing over 3 to 12 months with a down payment, debits via USSD or bank app.
• PayQart — merchant-side BNPL with weekly or monthly repayment over 2 to 6 months per approved shopper.
• Motito — point-of-sale device financing, another scaling player named in Nigeria's BNPL market coverage.

Questions integrators ask about Easybuy

Can the repayment schedule be read separately from the bank-account debits that fund it?

Yes. The installment plan lives inside the Easybuy loan record — due dates, per-installment amount, paid/unpaid flags — and we read it from the app's own loan surface. The actual debits hit a linked Nigerian bank account, which is a separate leg; if you need both sides reconciled we map the loan schedule from Easybuy and pair it with bank-side movement through a consented account feed.

Onboarding asks for a BVN. How is that identity data handled?

Identity capture during register-and-apply is sensitive personal data under the Nigeria Data Protection Act 2023, so we data-minimize: the integration carries only the identifiers your use case needs, BVN and phone are stored masked or referenced by token rather than copied in clear, and access is logged. Where a field isn't needed for your workflow we drop it at the parser rather than warehouse it.

Does Nigeria's open-banking registry cover an app like Easybuy?

The CBN Operational Guidelines for Open Banking (March 2023) govern permissioned data sharing between banks and registered third parties, and they reach the bank account that funds repayments. The loan ledger held inside Easybuy itself sits outside that scheme, so we reach it through authorized interface integration under your authorization, and use the open-banking consent route for the bank-side leg when you need it.

If Easybuy ships a new app build mid-project, does that reset delivery?

No. A new build usually changes screen layout or a few request fields, not the underlying loan model. We re-capture the traffic and patch the parser, which is a small task inside the one-to-two-week cycle rather than a restart. Ongoing UI churn from promotions is something we plan maintenance around.

Source for the working integration is delivered for a flat fee from $300, billed only after you've reviewed it and you're satisfied; if you'd rather not host anything, the same Easybuy endpoints are available as a pay-per-call hosted API with nothing upfront. Either way the cycle is one to two weeks. Tell us the app and the data you want from it on the contact page and we'll scope it.

How this mapping was put together

Checked in June 2026 against the app's own listing and the relevant Nigerian regulators. The loan terms, down payment and tenor come from Easybuy's Play Store description and Newedge Finance's product page; the regulatory framing is read from the CBN's published open-banking guidelines and the Nigeria Data Protection Act; market and peer context is from a 2025 Nigeria BNPL report. Endpoint shapes here are illustrative and are confirmed during the build, not lifted from any document.

• Easybuy on Google Play
• Newedge Finance — Easybuy product page
• CBN Operational Guidelines for Open Banking in Nigeria (PDF)
• Nigeria Data Protection Act, 2023 (PDF)

Mapped by the OpenBanking Studio integration desk · June 2026.