PUMB API integration & OpenBanking services (FUIB · Ukraine)

1. Account binding & consent

Mirror the FUIB AISP consent flow: third-party providers issue a consent token, the user authorizes via PUMB mobile-bank, and a refreshable session is bound to a customer ID. Used to onboard accounting platforms or PFM dashboards without exposing PUMB credentials.

2. Balance & product inventory

Pull current balance, hold amounts, and product type (vseKARTA hryvnia debit, vseMOZHU credit line up to 500,000 UAH, MoneyBox deposit at 5% p.a.). Powers daily sync for finance teams and credit-risk dashboards.

3. Statement & transaction history

Fetch paginated transactions with from-date/to-date, channel (UPI-equivalent IBAN, Google Pay, ATM, POS), MCC, counterparty IBAN, and FX details on currency exchange operations. Output formats: JSON, CSV, Excel, PDF.

4. UAH payment initiation (PISP)

Submit instant credit transfers (≤ 100,000 UAH) and regular SEP-style credit transfers (≤ 400,000 UAH) inside Ukraine, with idempotency keys, signed digests, and webhook callbacks for status updates.

5. Cashback & benefits data

Read connected cashback categories and partner activations from the PUMB Benefits section — useful for loyalty platforms, retail co-marketing, and personalized-offer engines.

6. Credit, installment & deposit

Capture vseMOZHU Online credit decisions (limit, APR up to 83.25%, term up to 24 months), Splachuite chastynamy installments, and MoneyBox accruals — feed into underwriting models or treasury reporting.

Scenario A — SME accounting sync

An SME running 1C or BAS in Ukraine connects PUMB through our AISP wrapper. Each night, statement entries from vseKARTA are pulled (date range, IBAN, MCC, counterparty) and posted into the GL. Reconciliation handles UAH IBAN transfers and Splachuite chastynamy installment payments separately, so VAT input is recognized correctly.

Scenario B — Cross-border remittance dashboard

A Ukrainian diaspora-focused fintech needs visibility into Western Union, Payoneer, Ria, and MoneyGram inflows landing on PUMB cards. The integration tags each settled UAH credit, exposes sender currency and FX margin, and powers a remittance dashboard with weekly cohort retention.

Scenario C — Personal finance management

A PFM app maps PUMB transactions to its category taxonomy via MCC, calculates spending velocity, and surfaces cashback-category recommendations — for example, advising the user to activate a partner cashback in the PUMB Benefits section before an upcoming purchase. Weekly insights are pushed via webhook.

Scenario D — B2B payout automation

A marketplace settles UAH payouts to merchants holding PUMB IBANs. PISP-style payment initiation is used for instant credit transfers up to 100,000 UAH (and batched regular transfers up to 400,000 UAH), with idempotency keys and signed digests. Status webhooks trigger order-state transitions.

Scenario E — Credit risk & underwriting

An NBFI requests authorized read-only access to a borrower’s PUMB transaction history and vseMOZHU credit-line utilization. Features (income regularity, IBAN inflows, FX exposure, cashback engagement) are computed and fed to an underwriting model — replacing manual paystub uploads.

Consent / authorization (AISP)

POST /api/v1/pumb/consents
Content-Type: application/json
Authorization: Bearer <CLIENT_TOKEN>
X-Request-ID: 8a1f-4b...

{
  "permissions": [
    "ReadAccountsBasic",
    "ReadBalances",
    "ReadTransactionsDetail"
  ],
  "expirationDateTime": "2026-12-31T23:59:59+02:00",
  "transactionFromDateTime": "2025-01-01T00:00:00+02:00"
}

200 OK
{
  "consentId": "c-7af3...",
  "status": "AwaitingAuthorisation",
  "authUrl": "https://auth.pumb.ua/.../authorize?consent=c-7af3..."
}

Statement / transaction query

POST /api/v1/pumb/statement
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "accountId": "UA213223130000026007233566001",
  "fromDate": "2026-03-01",
  "toDate":   "2026-03-31",
  "channel":  ["CARD","IBAN","GPAY"],
  "page":     1,
  "pageSize": 200
}

200 OK
{
  "items": [
    {
      "id":"tx_991...",
      "ts":"2026-03-14T10:21:08+02:00",
      "amount":-249.50,
      "ccy":"UAH",
      "mcc":"5411",
      "merchant":"ATB-Market",
      "counterparty":{"iban":"UA80...","name":"ATB"},
      "channel":"CARD"
    }
  ],
  "page":1,"hasMore":true
}

UAH payment initiation (PISP)

POST /api/v1/pumb/payments
Content-Type: application/json
Authorization: Bearer <PISP_TOKEN>
X-Idempotency-Key: 9f12-aa...
Digest: SHA-256=...
Signature: keyId="...",algorithm="rsa-sha256",...

{
  "type": "InstantCreditTransfer",
  "amount": { "value": 4500.00, "ccy": "UAH" },
  "debtor":   { "iban": "UA213223...001" },
  "creditor": { "iban": "UA903052...777", "name": "TOV Postachalnyk" },
  "remittance": "Invoice 2026-04-119"
}

201 Created
{ "paymentId":"p-771...", "status":"AcceptedSettlementInProcess" }
// Webhook: POST {your_url}  { paymentId, status:"Settled", ... }

Deliverables checklist

• Protocol & auth flow report (FUIB Open API mapping, consent/SCA handling)
• OpenAPI 3.1 specification for our wrapper endpoints
• Runnable source code (Python / Node.js / Go) for AISP and PISP flows
• Postman / Bruno collection and curl recipes
• Automated tests (pytest / vitest) and a synthetic-data sandbox
• Compliance notes: NBU Resolution No.80, PSD2 mapping, retention defaults
• Optional hosted gateway with pay-per-call billing

Engagement workflow

1. Scope confirmation — list of FUIB endpoints (consent, balance, statement, payment) and target environments.
2. Protocol analysis & API design (2–5 business days).
3. Build & internal validation against PUMB sandbox / authorized test accounts (3–8 business days).
4. Documentation, samples, and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; NBU-related approvals may extend timelines.

Pricing models

• Source code delivery from $300 — receive runnable API source code and full documentation; pay after delivery upon satisfaction.
• Pay-per-call API billing — call our hosted PUMB gateway and pay only per successful call, with no upfront cost.

Who we are

We are an independent technical studio focused on App interface integration and authorized API integration. Our engineers come from banks, payment gateways, mobile-protocol research, and cloud platforms, with hands-on delivery experience across Ukrainian and EU OpenBanking projects.

• Financial & banking apps: transaction history, statement queries, balance sync
• E-commerce, food delivery, retail apps: order & payment integration
• Hotel, travel, mobility apps: booking, itinerary, and payment verification
• Social, OTT, dating apps: authentication, messaging, profile management

Core strengths

• Familiar with mainstream apps’ interface standards across countries — including FUIB Open API and Ukrainian NBU norms.
• Compliant, lawful interface implementations only — no credential cracking, no scraping behind paywalls without consent.
• Both Android and iOS coverage; deliver runnable source code, OpenAPI documentation, and test plans.
• Two engagement models: source code delivery from $300, or hosted pay-per-call API billing.

What do you need from me?

The target app (PUMB / FUIB), your concrete needs (statements, balance, payment initiation, cashback data), and any sandbox / OAuth client credentials you already hold with PUMB Open API. We sign an NDA on request.

How long does delivery take?

5–15 business days for a first AISP / PISP drop with documentation. Multi-account or treasury-grade payment flows can extend to 3–4 weeks.

How do you handle compliance?

Authorized FUIB Open API or explicit user consent only. Strong customer authentication, signed requests, and minimum-retention defaults aligned with NBU Resolution No.80 and PSD2.

Can you cover Monobank, Privat24, Sense, and others too?

Yes — we frequently bundle PUMB integration with Monobank, Privat24, Sense SuperApp, Raiffeisen, Oschadbank, Sportbank, Izibank, A-Bank, and Neobank under a single normalized OpenData layer.