Nova API integration services — Open Finance Brasil & Pix installment flows

Authorized protocol analysis and production-ready API implementations for Nova (com.novapaytech.nova_mobile_app), built around Brazil's Open Finance standards.

From $300 · Pay-per-call available
OpenData · Open Finance Brasil · Pix parcelado · Card aggregation

Turn Nova's aggregated card limits and installment rails into a machine-readable API layer

Nova is a Brazilian fintech regulated by the Banco Central that lets users combine the limits of multiple credit cards via Open Finance, then spend them on Pix transfers, Boleto payments, and in-app purchases in up to 12 installments. Our studio delivers the API layer you need to extract, sync, and reuse that data inside your own back office, ERP, or financial product.

Card & limit aggregation API — Mirror Nova's Open Finance card linking flow: return linked issuers, available limits per card, combined purchasing power, and rotation of the generated virtual card.
Pix & Boleto on credit API — Initiate a Pix or Boleto payment funded by aggregated credit; receive installment plan, CET (effective total cost), due dates, and transaction status webhooks.
Statement & installment timeline API — Query historical operations, remaining installments per purchase, outstanding balance across linked cards, and export to JSON / CSV / Excel.
Compliance-aware session handling — Work entirely under user consent following Open Finance Brasil's consent object model; consent IDs, expiry, and revocation are surfaced as first-class fields.

Why Nova is interesting from an OpenData perspective

Nova ("Use melhor seu crédito") is a Pix and Boleto payment intermediation platform that sits directly on top of Brazil's Open Finance rails. Instead of issuing a new credit line, it borrows the limits that users already have on cards from Nubank, Itaú, Bradesco, Banco do Brasil, Caixa, Santander, C6 Bank, BTG+, Inter and others, and re-expresses them as a unified "power to pay" that can be spent on any Pix key or Boleto. That architecture produces several layers of structured data that external systems frequently need: consent records, per-card available limits, merged purchasing power, generated bridge-card metadata, individual Pix/Boleto operations, and the installment schedule created for each operation.

In 2024 and 2025 the platform advertised some of the lowest Pix installment rates on the Brazilian market (starting around 2.9% per month in public materials) and extended its scope from Pix-on-credit to full Boleto-on-credit and in-app purchases. In parallel, the Banco Central has been pushing a native Pix Parcelado rollout scheduled for late 2025, which makes Nova's earlier, Open-Finance-based implementation an especially interesting reference for any team building installment-aware payment flows.

For accounting tools, ERPs, BNPL risk engines, consumer-finance dashboards, and compliance platforms, this means Nova contains exactly the kind of transaction and installment data that Open Finance was designed to make portable. Our job is to package that data as a clean, versioned API you can call from your own stack.

What we deliver

Deliverables checklist

  • API specification (OpenAPI 3.1 / Swagger) for Nova-flavored endpoints
  • Protocol and authentication flow report (device bind, token, signature chain)
  • Runnable source code for card aggregation, Pix-on-credit, and statement export (Python / Node.js / Go)
  • Automated test suite with sandbox fixtures and CI-friendly harness
  • Compliance guidance aligned to Banco Central, Open Finance Brasil, and LGPD
  • Observability kit: structured logging, trace IDs, and consent-state metrics

Engagement models

Two ways to work with us, depending on your volume and how much of the stack you want to own:

  • Source code delivery from $300 — we hand over runnable API source code, documentation, and test plans; pay after delivery upon satisfaction.
  • Pay-per-call API billing — call our hosted endpoints and pay only for successful requests; no upfront fee, ideal for early integrations or spiky usage.

Key integration scenarios

Card aggregation at onboarding, Pix parcelado initiation, Boleto parcelado initiation, installment-aware statement export, webhook-driven reconciliation, and consolidated dashboards for users holding Nova plus traditional banking apps. Enterprise clients can layer multi-account support on top of the same API.

Data available for integration

The table below summarises the structured data our Nova integration surfaces. Each row maps the data type to the screen or feature that holds it in the app and to a concrete downstream use.

Data typeSource screen / featureGranularityTypical use
Linked card inventory"My cards" / Open Finance consent flowPer-card: issuer, brand, masked PAN, statusOnboarding dashboards, duplicate-card detection
Available limitsHome / combined limit widgetPer-card + aggregated, updated at consent refreshCredit risk scoring, buy-now-pay-later underwriting
Pix-on-credit operationsPix tab / transaction historyPer-operation: key, amount, fee, CET, statusExpense management, reconciliation, anti-fraud
Boleto-on-credit operationsPay Boleto tabPer-operation: barcode, payer, amount, due dateAccounts payable automation, tax receipts
Installment schedulePurchase detail / Minhas parcelasPer-installment: index, due date, amount, interestCash-flow forecasting, collections forecasting
Bridge card metadataVirtual card screenToken, BIN, expiry, rotation eventsToken provisioning, merchant diagnostics
Consent lifecycleOpen Finance consent centerConsent ID, scopes, status, expiry, revocation tsCompliance reporting, audit trails

Typical integration scenarios

1. BNPL risk engine using combined card limits

A Brazilian BNPL provider wants to underwrite new loans without waiting for credit-bureau delays. At checkout, it calls GET /nova/users/{id}/limits to read the user's aggregated available limit across all linked cards and the last 90 days of Pix-on-credit activity. Those figures feed directly into the scoring model and reduce fraud on first-time borrowers. Mapping to Open Finance: the data is derived from phase-2 credit-card sharing and is re-exposed as a single consent-gated endpoint.

2. Accounts-payable automation for small merchants

A Brazilian SaaS ERP lets merchants pay suppliers via Boleto. It uses POST /nova/boletos/pay-on-credit to fund each payment with Nova's aggregated limit and receives a webhook carrying the installment plan. The ERP books the full Boleto in accounts payable and the installments as short-term financial liabilities, keeping the general ledger consistent with Brazilian accounting standards.

3. Installment-aware personal finance dashboard

A PFM app aggregates banks over Open Finance but needs Nova's installment timeline, which is not part of the default standard. It calls GET /nova/installments?status=open and merges the plan with statements from Nubank, Itaú and Inter. Users see their real month-by-month obligation across all channels instead of a single blended number. Mapping to Open Finance: consent coverage is extended to include Nova-created installment plans.

4. Compliance monitoring for regulated intermediaries

A payment institution must keep auditable logs of consent. It subscribes to the consent.updated webhook and stores every change (AUTHORISED, REJECTED, REVOKED, CONSUMED) with a signed hash. On audit, the integration proves that every Pix-on-credit call had a valid consent at the moment of execution and respected the Open Finance Brasil retention rules.

5. Reconciliation between virtual card and merchant acquirer

An e-commerce platform that accepts Nova's bridge card wants to match each authorisation on the acquirer side with the underlying Pix or installment plan on Nova. A reconciliation job pulls GET /nova/card-operations?from=... daily and joins by virtual_card_token + amount + timestamp, flagging mismatches to a queue for manual review.

Technical implementation

Example 1 — Pix on credit initiation

POST /api/v1/nova/pix/pay-on-credit Content-Type: application/json Authorization: Bearer <ACCESS_TOKEN> X-Consent-Id: urn:bancocentral:consent:v1:8a7b... { "pix_key": "supplier@example.com", "amount": 1299.90, "installments": 6, "description": "Invoice 2026-04-17", "idempotency_key": "a3e8..." } // 200 OK { "operation_id": "nv_op_01HX...", "end_to_end_id": "E18236120202604181200s1", "status": "AUTHORISED", "cet_monthly": 0.029, "installment_plan": [ {"i": 1, "due": "2026-05-18", "amount": 222.40}, {"i": 2, "due": "2026-06-18", "amount": 222.40} ] }

Example 2 — Statement and installment export

GET /api/v1/nova/statements ?from=2026-01-01&to=2026-04-30 &type=PIX,BOLETO,CARD &format=json Authorization: Bearer <ACCESS_TOKEN> // 200 OK (truncated) { "items": [ { "operation_id": "nv_op_01HX...", "type": "PIX", "amount": 1299.90, "fee": 12.99, "installments_total": 6, "installments_remaining": 4, "created_at": "2026-04-18T13:12:44Z" } ], "page": {"cursor": "eyJvcCI6...", "has_more": true} }

Example 3 — Webhook for consent and operation state

POST https://your-app.example.com/webhooks/nova X-Nova-Signature: sha256=9bd... Content-Type: application/json { "event": "operation.updated", "operation_id": "nv_op_01HX...", "status": "SETTLED", "consent_id": "urn:bancocentral:consent:v1:8a7b...", "timestamp": "2026-04-18T13:14:02Z" } // Verify: hmac_sha256(body, WEBHOOK_SECRET) == signature // Retry policy: exponential backoff, 24h window, dedup by operation_id

Compliance & privacy

Nova is regulated by Banco Central do Brasil and participates in the Open Finance Brasil ecosystem, which is governed by Resolução Conjunta BCB/CMN nº 1/2020 and the related roadmap overseen by the Open Finance Brasil Governance Structure. Any integration we deliver therefore operates under three overlapping regimes: the Banco Central's payments regulation, the Open Finance Brasil technical and security specifications, and Lei Geral de Proteção de Dados Pessoais (LGPD, Lei nº 13.709/2018).

In practice this means: (a) every data call is tied to a valid consent ID with an explicit scope and expiry; (b) personal and financial data is minimised, encrypted in transit and at rest, and retained only for the period declared in the consent; (c) consent revocation is propagated in near real time and reflected in the consent.updated webhook; (d) audit logs include the consent ID, scopes, purpose, and the operator that triggered the call, so the integration is defensible in an LGPD or Banco Central audit. International clients can additionally request alignment to GDPR and PSD2-style strong customer authentication on the calling side.

Data flow & architecture

The reference pipeline is intentionally simple so it can be dropped into any existing stack:

  • Client app / back office — calls our authenticated API (REST or gRPC) with the user's consent ID.
  • Integration gateway — handles authentication, rate limiting, request signing, and idempotency.
  • Nova protocol adapter — speaks Nova's mobile protocol and Open Finance Brasil APIs on behalf of the authorised user.
  • Normalisation & storage — stores normalised operations, installments, and consent state in Postgres; raw payloads in object storage for forensics.
  • Analytics / webhook fan-out — pushes events to your data warehouse, BI tool, or internal services.

The same topology supports pay-per-call clients (who consume the hosted endpoints directly) and source-code clients (who run the adapter and storage in their own VPC).

Market positioning & user profile

Nova targets Brazilian consumers who already hold one or several credit cards and want to use the unused limit more flexibly — either to pay a Pix they would otherwise pay in cash, or to break a big Boleto into installments without contracting a separate loan. The primary market is Brazil, on Android and iOS, with users skewing towards mid-income urban professionals and small-business owners looking for working-capital smoothing. From an integration point of view this makes Nova attractive to PFM apps, BNPL providers, small-business ERPs, accounting platforms, and compliance vendors serving the Brazilian market.

Screenshots

Click any thumbnail to enlarge. These images come from Nova's official app store listing and illustrate the product surfaces our integration covers: onboarding, card linking via Open Finance, Pix and Boleto-on-credit flows, installment plans, and the combined limit view.

Nova screenshot 1 Nova screenshot 2 Nova screenshot 3 Nova screenshot 4 Nova screenshot 5 Nova screenshot 6 Nova screenshot 7 Nova screenshot 8 Nova screenshot 9 Nova screenshot 10

Similar apps & integration landscape

Teams that integrate Nova often need to cover adjacent apps in the Brazilian payments ecosystem. We have shipped or researched integrations for all of the following, and they share significant overlap with Nova in terms of data model and Open Finance Brasil coverage:

  • PicPay — A wallet and super-app that offers PicPay Parcela for installment-style payments on Pix, Boleto, P2P transfers, and PicPay Shop purchases. Users who work with PicPay frequently need unified transaction exports across Nova and PicPay.
  • Pagaleve — A Pix-parcelado specialist offering 4x interest-free Pix installments without a credit card. Relevant whenever a merchant wants to compare BNPL funnels that include Nova and Pagaleve side by side.
  • Z1 / NG.CASH — A digital account originally focused on teenagers and young adults, now operating as a payment institution. Their Pix-via-Open-Finance product shares the same consent model we use for Nova.
  • Mercado Pago — Offers Open-Finance-based Pix payments and installment plans inside Mercado Libre's checkout; often sits next to Nova as an alternative funding source in merchant stacks.
  • Nubank — One of the most commonly linked issuers inside Nova; its credit-card statement and installment data is typically consolidated alongside Nova activity.
  • Itaú — Offers Pix parcelado in up to 12x on credit cards directly, making it a useful benchmark for Nova's installment terms and a common link target.
  • Banco do Brasil (BB Pay) — Provides fee-free Pix acquiring and Pix parcelado flows; an important reference point when modelling issuer-side settlement for Nova operations.
  • Bradesco — Launched Pix parcelado not tied to the credit card limit; integrations often need to reconcile Nova-funded Pix with Bradesco's own installment lines.
  • OpenPix — A merchant-side Pix platform; frequently combined with Nova-style installment funding to power longer-tail e-commerce checkouts.
  • Belvo — A Latin American Open Finance aggregator; useful when a client wants Nova data alongside data from banks not natively supported by a single aggregator.

We do not rank or criticise these apps — they are part of the same ecosystem and many of our clients operate across several of them at once.

About us

We are an independent studio focused on fintech and open-data API integration, with a strong Brazilian-market practice. Our engineers have built systems for acquirers, Pix-parcelado fintechs, and Open Finance aggregators, and we work daily with the technical specifications published by the Open Finance Brasil Governance Structure.

  • Payments, digital banking, BNPL, and cross-border settlement
  • Enterprise API gateways and security reviews aligned to Banco Central guidance
  • Custom Python / Node.js / Go / Kotlin SDKs and reproducible test harnesses
  • Full pipeline: protocol analysis → reverse engineering → build → validation → compliance hand-off
  • Source code delivery from $300 — runnable API source code and documentation; pay after delivery upon satisfaction.
  • Pay-per-call API billing — access our hosted endpoints and pay only for successful calls, no upfront cost.

Contact

Share the target app (Nova or others) and the exact integration scope you need — card aggregation, Pix on credit, Boleto on credit, installment export, webhooks, or a full pipeline. We reply with a scoped quote, a timeline, and a list of questions we need answered before starting.

Go to contact page

Engagement workflow

  1. Scope confirmation: which Nova flows are in scope (aggregation, Pix, Boleto, installments, webhooks).
  2. Protocol analysis and API design (2–5 business days, depending on complexity).
  3. Build and internal validation against sandbox and staged traffic (3–8 business days).
  4. Documentation, sample clients, and regression tests (1–2 business days).
  5. Typical first delivery: 5–15 business days. Banco Central or Open Finance approvals on your side may extend the timeline.

FAQ

What do you need from me?

The target app name (already given: Nova), a concrete list of flows you want covered, any existing sandbox credentials, and the platforms you will consume the API from.

How long does delivery take?

Usually 5–12 business days for a first drop covering card aggregation and one payment flow. Full installment-aware coverage with webhooks typically takes 2–3 weeks.

How do you handle compliance?

We work only under authorised user consent or documented public/partner APIs, with consent IDs, audit logs, data minimisation, and LGPD-aligned retention policies. NDAs are available on request.

Do you cover other Brazilian apps?

Yes — PicPay, Pagaleve, Nubank, Itaú, Banco do Brasil, Bradesco, Mercado Pago, OpenPix, Z1/NG.CASH, and several others are part of our regular scope.
📱 Original app overview (appendix)

Nova ("Use melhor seu crédito", package com.novapaytech.nova_mobile_app) is a Brazilian payments app from Nova Pagamentos. It lets users combine the limits of multiple credit cards via Open Finance Brasil, then use that combined purchasing power to pay Pix, Boleto, and regular card purchases in up to 12 installments.

  • All linked cards in one place via Open Finance ("Connect your cards with the convenience and security of Open Finance").
  • Pix and Boleto payments funded by credit, with some of the lowest advertised installment rates on the Brazilian market.
  • Flexible repayment: pay in full on the card invoice, or split into up to 12 installments.
  • Security standards aligned with major banks, including strong authentication and data privacy controls.
  • Regulated by Banco Central do Brasil and integrated into the Open Finance ecosystem.
  • Available for Android and iOS in Brazil (Google Play package com.novapaytech.nova_mobile_app; App Store ID 6670275494).
  • Publisher: Nova Pagamentos — web presence at explorenova.com.br.

This section describes the third-party app Nova for reference only. Our studio is not affiliated with Nova Pagamentos; we provide integration services on behalf of clients who hold the necessary authorisation.