Pivdenny Online API integration services (OpenBanking · Ukraine)

Deliverables checklist

• OpenAPI 3.1 specification covering accounts, cards, statements, deposits, transfers, FX
• Protocol report — login chain, BankID handoff, token refresh, push-message verification
• Runnable Python and Node.js source for the most-used endpoints
• Postman collection plus pytest / Jest suites
• Compliance pack — consent template, retention guidance, NBU Open Banking checklist

Engagement models

• Source-code delivery from $300 — runnable API source plus documentation, paid after you confirm it works in your own environment
• Pay-per-call — hit our hosted gateway, no upfront cost, ideal for low-volume reconciliation jobs
• Optional retainer for new endpoints when the bank ships changes (e.g. new deposit product, FX pair, push schema)

1 · UAH bookkeeping for SMEs holding Pivdenny cards

Context: a Ukrainian SME pays contractors with Pivdenny cards and wants entries posted to its accounting system every morning. We pull card-account transaction history and statement export, normalise to a chart-of-accounts mapping, and emit IFRS-aligned rows. Maps to the OpenBanking AIS profile of Berlin Group NextGenPSD2.

2 · Deposit-laddering dashboard for HNW clients

Context: a wealth advisor manages clients holding multiple Premium / Profitable Plus / Mobile Deposit positions. We expose deposit catalogue, balance, rate and auto-prolongation flags, and stream early-termination events through a webhook so the advisor can react before maturity gaps open.

3 · Multi-currency treasury with FX-on-deposit

Context: a cross-border importer wants to buy USD or EUR at the in-app rate and immediately place the proceeds on a deposit. We script the two-step flow (FX quote → deposit booking) behind a single idempotent endpoint, with the realised rate logged for treasury attribution and the resulting position visible alongside UAH balances.

4 · Virtual-card issuance for online subscriptions

Context: a SaaS reseller needs a fresh virtual Mastercard for each end-customer. We wrap the in-app re-issue flow into a card-create endpoint, return the masked PAN plus expiry to a vault provider, and publish lifecycle events (activation, block, limit change) on a webhook so finance and ops stay in sync.

5 · Real-time AFU donation receipts

Context: a charity processing donations to the special NBU account for the Armed Forces of Ukraine wants tamper-evident receipts. We hook the Pivdenny push-message stream and the corresponding statement row into a signed-receipt service that writes a hash trail and emails or messages the donor on Telegram, Viber or Messenger.

Login & token refresh (BankID-aware)

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

{
  "phone": "+380XXXXXXXXX",
  "device_id": "uuid-v4",
  "factor": "FACE_ID|TOUCH_ID|PIN",
  "bankid_token": "<optional NBU BankID payload>"
}

200 OK
{
  "access_token": "...",
  "refresh_token": "...",
  "expires_in": 1800,
  "consent_id": "cs_01HFY...",
  "scope": ["accounts","statements","deposits","fx"]
}

Statement export (PDF / CSV / JSON)

POST /api/v1/pivdenny/statement
Authorization: Bearer <ACCESS_TOKEN>
Idempotency-Key: stm_2026-04_acc-001

{
  "account_iban": "UA9133...",
  "from_date": "2026-04-01",
  "to_date":   "2026-04-30",
  "format":    "json"   // "csv" | "pdf"
}

200 OK
{
  "account_iban": "UA9133...",
  "currency": "UAH",
  "rows": [
    {
      "ts": "2026-04-12T09:24:11+03:00",
      "amount": -428.50,
      "mcc": "5411",
      "merchant": "ATB",
      "ref": "auth_1029384",
      "fx": null
    }
  ],
  "next_cursor": null
}

Push-notification webhook (transaction event)

POST https://your-app.example/webhooks/pivdenny
X-Pivdenny-Signature: t=1714560000,v1=...

{
  "event": "transaction.posted",
  "consent_id": "cs_01HFY...",
  "card_id": "vc_01HEX...",
  "amount": 12000.00,
  "currency": "UAH",
  "merchant": "AFU NBU 380...",
  "channel": "deposit_topup|fx|p2p|merchant",
  "ts": "2026-04-12T09:24:11+03:00"
}

// On non-2xx response we retry with exponential backoff (60s, 5m, 30m).

Ukrainian Open Banking framework

Pivdenny Bank already publishes Open Banking interfaces aligned with the Berlin Group NextGenPSD2 AIS/PIS classification through the Ukrainian Processing Centre. The wider regulatory layer was set on 25 July 2025 by NBU Board Resolution No. 80, transposing the spirit of EU PSD2 for Ukraine, with a phased compliance window for payment service providers running into early 2026. Our integrations enforce explicit consent, decoupled SCA, and the right of revocation that the framework requires.

Data protection & controls

• Authorized or documented public APIs only — no scraping of restricted surfaces
• Consent records stored with the access and refresh tokens; revocation propagates to the gateway
• Data minimisation — only the fields named in the consent reach your storage
• Logs retained per the Law of Ukraine "On Personal Data Protection" and GDPR for EU-resident users
• NDAs and signed DPA on request; deployable inside your VPC if data residency is in scope

Privat24

The PrivatBank super-app and the largest finance app in Ukraine, with around 38 million installs. Holds card balances, UAH and FX statements, utility-bill history and LiqPay flows that often need to be unified with Pivdenny statements.

monobank

Fully digital, app-only neobank from Universal Bank with 10M+ active clients. Strong public APIs for personal accounts and a rich category-tagged transaction stream that pairs well with Pivdenny deposit data.

MyRaif (Raiffeisen Bank Aval)

Mobile bank for one of Ukraine's largest universal banks. Cards, deposits, and corporate light flows; common companion when a treasury team holds liquidity in both Pivdenny and Raiffeisen accounts.

PUMB Mobile Banking

FUIB / PUMB's mobile channel covering retail and SME. Statement export and instalment plans frequently appear alongside Pivdenny in cross-bank reconciliation jobs.

Sense SuperApp (Alfa-Bank Ukraine)

Combines current accounts, deposits, lending and loyalty in a single app. Useful counterpart for SME clients who keep working capital across multiple banks including Pivdenny.

Oschad (Oschadbank)

State-owned Oschadbank's mobile app, common for pension and government-related transfers. Often integrated alongside Pivdenny when consolidating personal-finance views.

ProCredit m-banking Ukraine

Mobile channel for SME and trade-finance customers of ProCredit Bank Ukraine. Complementary to Pivdenny when an exporter holds USD/EUR working accounts at multiple banks.

NovaPay

Payment app from the Nova Poshta group with 1.1M+ installs, focused on remittances and merchant payments. Frequently appears in statement-aggregation projects together with traditional bank apps.

About us

OpenFinance Lab is an independent studio specialising in mobile-app protocol analysis and authorized API integration for fintech clients worldwide. Our engineers come from banking, payment processors, mobile-app reverse engineering and cloud platforms, and we ship under signed NDAs and aligned with local regulators.

• Retail and SME banking, deposits, FX, and cross-border payments
• Enterprise API gateways, consent management, and security reviews
• Custom Python / Node.js / Go SDKs, Postman collections, automated test suites
• Full pipeline: protocol report → build → validation → compliance hand-off
• Source code delivery from $300 — runnable API source plus full documentation; pay after you confirm it works on your side
• Pay-per-call API billing — hosted endpoints with usage-based pricing, no upfront fee

Contact

For quotes, sandbox access, or to submit your target requirements for Pivdenny Online or any of the related Ukrainian banking apps, open our contact page:

Contact page

We respond within one business day across CET / EET working hours.

Engagement workflow

1. Scope confirmation — pick the endpoints (statements, deposits, FX, virtual cards, push events) and authorisation route
2. Protocol analysis & API design — 2 to 5 business days, depending on the number of currencies and event types
3. Build and internal validation — 3 to 8 business days, including a sandbox account where Pivdenny exposes one
4. Docs, samples and test suites — 1 to 2 business days, hand-off through Git or your preferred channel
5. First delivery typically lands in 5 to 15 business days; bank-side approvals or BankID onboarding may extend the schedule

FAQ

What inputs do you need to start a Pivdenny Online integration?

How long does a first delivery take?

How do you stay compliant with Ukrainian Open Banking rules?

Can you deliver Pivdenny Online APIs without us building backend infrastructure?