Pynova API integration & OpenFinance data export

Deliverables checklist

• API specification (OpenAPI / Swagger) for every Pynova endpoint in scope
• Protocol & authentication report: login flow, token refresh, cookie/header chain, device-binding notes
• Runnable source for login, balance, statement and referral-export APIs (Python and Node.js reference clients)
• Automated integration tests plus a Postman / cURL collection
• Compliance notes: consent capture, data-minimization, retention guidance, KYC field handling

Two engagement models

Pick whichever matches your team's procurement style:

• Source-code delivery from $300 — we hand over runnable API source and full documentation; you pay after delivery once you are satisfied.
• Pay-per-call hosted API — call our managed Pynova endpoints and pay only for the requests you make, no upfront cost; good for teams that prefer usage-based pricing or a quick pilot.

Market positioning & user profile

Pynova is a consumer (B2C) earning / micro-investment app whose review chatter and walkthroughs skew toward South and Southeast Asian audiences on Android, alongside a wider international footprint thanks to its multi-language UI. The people most likely to need a Pynova integration are different: affiliate networks tracking referral payouts, fintech aggregators building a unified "all my balances" view, accountants reconciling withdrawals, and risk teams screening reward-farming patterns — a B2B layer sitting on top of B2C accounts.

1. Unified balance & portfolio aggregation

Context: a personal-finance dashboard wants to show a user's Pynova wallet and investment positions next to their bank and brokerage accounts. Data/API: GET /v1/account/balance and GET /v1/investments. OpenFinance mapping: account-information access — read-only, consent-scoped, refreshed on a schedule, exactly like an AISP pulling account balances.

2. Withdrawal reconciliation & payout monitoring

Context: a finance team needs every Pynova withdrawal matched against bank settlements, with alerts on stuck payouts. Data/API: GET /v1/transactions?type=WITHDRAWAL plus a withdrawal.status_changed webhook. OpenFinance mapping: transaction-data sharing for accounting/reconciliation, the most common open-banking use case translated to an app wallet.

3. Referral / affiliate accounting

Context: a growth team running Pynova's "invite contacts and earn rewards" program must audit who earned what and whether bonuses were actually paid. Data/API: GET /v1/referrals/ledger with referrer, referee, trigger event and payout state. OpenFinance mapping: structured ledger export — treat the rewards ledger as a sub-account statement that downstream systems can ingest.

4. Risk & anti-fraud screening

Context: a risk function wants to flag self-referral rings and abnormal withdrawal velocity on Pynova accounts. Data/API: combine the referral tree, device/login metadata from the auth report, and withdrawal timestamps. OpenFinance mapping: consented data feeding a risk engine — the same pipeline open-banking fraud tools use, scoped to one app.

5. Compliance archive & data-subject requests

Context: an operator needs a complete, exportable record per user to answer GDPR-style access or deletion requests. Data/API: a batch export job calling profile, transactions, withdrawals and referral endpoints, written to object storage as JSON. OpenFinance mapping: portability of personal financial data — the API is the mechanism that makes the right to data portability practical.

1) Authenticate & obtain a session token

POST /v1/auth/login
Content-Type: application/json

{
  "principal": "user@example.com",
  "credential": "<password-or-otp>",
  "device_id": "a1b2c3d4"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8f3a...",
  "expires_in": 3600,
  "account_id": "acc_91827"
}
# refresh: POST /v1/auth/refresh { "refresh_token": "rt_8f3a..." }

2) Pull a transaction / withdrawal statement

GET /v1/transactions?from=2026-04-01&to=2026-04-30&type=WITHDRAWAL&cursor=
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "items": [
    {
      "id": "txn_55021",
      "ts": "2026-04-18T09:42:11Z",
      "type": "WITHDRAWAL",
      "amount": "1500.00",
      "currency": "INR",
      "status": "PROCESSING",
      "channel": "bank_transfer",
      "fee": "15.00",
      "reference": "WD-2026-55021"
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjUwfQ=="
}

3) Webhook: withdrawal status changed

# You register an HTTPS endpoint; we POST signed events.
POST https://your-app.example/webhooks/pynova
X-Signature: sha256=9c1f...   # HMAC over the raw body

{
  "event": "withdrawal.status_changed",
  "account_id": "acc_91827",
  "txn_id": "txn_55021",
  "old_status": "PROCESSING",
  "new_status": "PAID",
  "ts": "2026-04-19T03:12:00Z"
}

# Verify X-Signature, return 2xx within 5s, otherwise we retry
# with exponential backoff (max 24h). Errors: 4xx = drop, 5xx = retry.

4) Referral rewards ledger export

GET /v1/referrals/ledger?account_id=acc_91827&status=accrued
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "referrer": "acc_91827",
  "entries": [
    { "referee": "acc_77310", "trigger": "first_deposit",
      "reward": "50.00", "currency": "INR", "payout_state": "pending" }
  ],
  "total_accrued": "50.00"
}
# Error envelope (all endpoints):
# { "error": { "code": "rate_limited", "message": "...", "retry_after": 30 } }

How we keep it lawful

We integrate only under explicit client authorization or via documented, publicly available endpoints — never around access controls. Personal and financial data is minimized to what the use case needs, transfers are encrypted, and consent plus access events are logged so an audit can reconstruct who saw what. Because Pynova handles money movement and referral payouts, we align designs with open banking data-sharing norms, GDPR principles (lawful basis, data-subject rights, retention limits), PSD2-style strong customer authentication for any write operations, and, where the deployment is India-facing, current RBI digital-payment and SEBI investor-protection guidance. NDAs are signed on request.

Typical modules

• Account login, token refresh and device-session handling
• Balance, holdings and investment-position snapshots
• Transactions, deposits, withdrawals and statement exports
• Referral rewards ledger and invite-tree export
• Webhook fan-out for withdrawal and reward events
• Batch data-subject export for access/deletion requests

• Robinhood — commission-free stock, ETF, options and crypto trading; holds positions, order history and cash balances that users often want unified with other accounts.
• Webull — stocks, ETFs, options, fractional shares and more; rich market data plus account statements that feed portfolio dashboards.
• Wealthfront — automated portfolios and cash accounts; balances and allocation data are typical aggregation targets.
• Betterment — robo-advisor with goal-based portfolios; holdings and transaction history map cleanly onto OpenFinance account-information flows.
• Fundrise — real-estate and alternative investments with low minimums; position values and distributions are useful in consolidated reporting.

• Public — multi-asset investing app; portfolio and activity data sit alongside Pynova balances in a unified view.
• Swagbucks — rewards/earning platform; its points ledger and referral structure resemble the data model behind Pynova's invite-and-earn feature.
• FundNova — a fintech app in the same naming neighbourhood; account and transaction exports are the recurring integration need.
• Phillip Nova — multi-market trading app from Phillip Capital; trade and statement data is frequently reconciled against other brokers.
• Koyfin — financial-data and analytics platform; often the destination where exported balances and positions are charted and tracked.

About our studio

We are an independent technical-services studio focused on mobile app interface integration and authorized API integration, with hands-on backgrounds in fintech, payments and protocol analysis. Customers give us a target app name and concrete requirements; we deliver runnable API or protocol-implementation source code grounded in OpenData / OpenFinance / OpenBanking practice.

• Financial & banking apps: transaction records, statements, balance and payment integration
• E-commerce, delivery and retail: orders, payment integration, data sync
• Travel & mobility: bookings, itinerary queries, payment verification
• Social, OTT and dating: authentication/login, messaging, profile management
• Android and iOS; deliverables include API source, documentation and test plans

Contact

To request a quote or submit your target app and requirements, open our contact page. Tell us which Pynova data you need (balance, transactions, withdrawals, referral ledger), your regions and currencies, and whether you prefer source-code delivery or pay-per-call.

Go to contact page

Engagement workflow

1. Scope confirmation — which Pynova endpoints and data fields, which regions, push vs pull (about 1 business day).
2. Protocol analysis & API design — auth flow, signing, pagination, error model (2–5 business days).
3. Build & internal validation — reference clients, tests against a sandbox or test account (3–8 business days).
4. Documentation, samples and handover — OpenAPI spec, Postman collection, compliance notes (1–2 business days).
5. First delivery typically lands in 5–15 business days; third-party approvals or anti-bot complexity can extend it.

FAQ

What do you need from me to start a Pynova integration?

How long does a Pynova API delivery take?

How do you handle compliance and user privacy for Pynova data?

Can I pay per API call instead of buying source code?