CreditKasa API integration services (Ukraine OpenFinance)

1. Loan application orchestration

End-to-end coverage of the CreditKasa application path: calculator inputs (term, amount), personal data, passport and identification code photos, selfie verification and contract acceptance. Outputs: application_id, decision, approved_amount, tariff_code, contract_pdf_url. Used for lead-routing, BNPL underwriting and white-label onboarding.

2. Repayment schedule API

Returns each installment with due_date, principal, interest, extension_flag, paid_at and channel (Privat24, EasyPay, City24, bank cash). Used by accounting tools and personal-finance dashboards to reconcile borrower cash flow against bank-card statements.

3. KYC & BankID handover

Wraps BankID NBU "one-button" verification: redirect URL, consent receipt, signed payload of passport, ITN (tax ID) and address. Used for downstream credit bureaus, anti-fraud engines and sanctions screening without re-asking the user for documents.

4. Card binding & payout webhook

Captures the bound card token (Visa / Mastercard), issuing bank, masked PAN and payout status. Webhook events payout.created / payout.failed drive ledger entries on your side. Used for treasury reconciliation across Privat, Monobank, Pumb and Abank.

5. Loan ledger & statement export

Paged statement query with date range and product filter (MiniKasa or MaxiKasa). Export to JSON, CSV or branded PDF. Used for tax filings, household-finance apps and SME bookkeeping where microloan obligations have to be aggregated alongside bank transactions.

6. Promo & tariff lookup

Surfaces the active promotional APR (advertised maximum 3.65%) versus the standard schedule (up to 331.9% APR), discount eligibility for repeat customers and current loyalty offers. Used by loan aggregators that compare CreditKasa against Moneyveo, Miloan and CreditPlus on a daily basis.

Scenario A — Consumer credit aggregator

A loan-comparison portal pulls daily promo APR, minimum and maximum amount, and term ranges for MiniKasa and MaxiKasa via our /v1/creditkasa/products endpoint and writes them to its product catalogue alongside Moneyveo, Miloan, CreditPlus and Credit7. The same back-end signs the borrower in via BankID NBU, then redirects to the CreditKasa contract step. Maps to OpenFinance "Account Information Service" (AIS) patterns published by the NBU on 1 August 2025.

Scenario B — Personal-finance dashboard

An end-user PFM app fetches the borrower's repayment schedule and paid installments and merges them with Privat24 / Monobank statement data. Each row carries loan_id, due_date, principal, interest_paid and days_overdue so the dashboard can show one consolidated cash-flow view of monthly obligations.

Scenario C — SME bookkeeping & tax reporting

Self-employed users in Ukraine often take MiniKasa for working capital. Our statement export pushes each loan, fee and repayment into 1C, BAS or QuickBooks via CSV/JSON so accountants can match every CreditKasa cash-out against the borrower's FOP turnover and produce annual reports.

Scenario D — Credit-scoring & risk engine

A scoring platform listens to application.decided and repayment.observed webhooks. Behaviour features (number of MaxiKasa renewals, average days late, channel mix) feed gradient-boosted models that score new applicants. Maps to OpenData "outcome data" pattern: lender shares decision and repayment outcomes back to the model.

Scenario E — Compliance & audit log delivery

Internal compliance teams query our /v1/creditkasa/audit endpoint to receive a tamper-evident log of consent events, KYC checks and contract signatures. Designed for NBU on-site reviews and for legal teams responding to client data-subject requests under Ukrainian personal-data law.

Authentication & BankID handover

POST /v1/creditkasa/auth/bankid
Content-Type: application/json
Authorization: Bearer <CLIENT_TOKEN>

{
  "redirect_uri": "https://partner.example/cb",
  "scope": ["loan.read", "repayment.read", "identity.read"],
  "consent_ttl_seconds": 1800
}

200 OK
{
  "auth_url": "https://id.bank.gov.ua/auth/...",
  "state": "ck_8f2a...",
  "expires_at": "2026-04-29T14:32:00Z"
}

Statement & repayment query

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

{
  "user_id": "ck_user_2031",
  "product": "minikasa",
  "from_date": "2026-01-01",
  "to_date": "2026-04-29",
  "page": 1,
  "page_size": 100
}

200 OK
{
  "loan_id": "L-552113",
  "currency": "UAH",
  "principal": 12000,
  "schedule": [
    {"due_date": "2026-05-15", "principal": 1000,
     "interest": 360, "status": "due"},
    {"due_date": "2026-04-15", "principal": 1000,
     "interest": 360, "status": "paid",
     "paid_at": "2026-04-14T10:11:00Z",
     "channel": "privat24"}
  ]
}

Repayment webhook (push)

POST https://partner.example/hooks/creditkasa
X-CK-Signature: sha256=...
Content-Type: application/json

{
  "event": "repayment.observed",
  "loan_id": "L-552113",
  "amount": 1360,
  "currency": "UAH",
  "channel": "easypay",
  "observed_at": "2026-04-29T08:21:14Z",
  "remaining_principal": 9000
}

// Signature is HMAC-SHA256 of body with shared secret.
// Retries: 5 attempts, exponential backoff (1m, 5m, 30m, 2h, 12h).

Error handling & idempotency

Every write call accepts an Idempotency-Key header so retries during BankID redirect timeouts or NBU Open Banking rate limits do not produce duplicate loan applications. Errors follow a stable shape: {"error":{"code":"ck.bankid_consent_expired","message":"...","trace_id":"..."}}. Common codes include ck.kyc_required, ck.card_blocked_by_issuer and ck.tariff_unavailable.

Deliverables checklist

• OpenAPI / Swagger spec for loan, statement, KYC, payout endpoints
• Protocol & auth flow report (BankID handover, token refresh, signature scheme)
• Runnable source code in Python and Node.js (login, statement, webhooks)
• Postman collection and end-to-end test cases
• Compliance pack: consent receipts, NBU Open Banking checklist, retention guidance
• Optional: hosted API endpoints with usage-based billing

Engagement models

• Source-code delivery from $300 — Full runnable API source plus documentation; you pay after delivery upon satisfaction.
• Pay-per-call hosted API — Use our managed CreditKasa adapter and pay only for the calls you actually make. No upfront fee.

Workflow

1. Scope confirmation: target endpoints (loan, statement, BankID, payout).
2. Protocol analysis & API design — 2–5 business days.
3. Build & internal validation — 3–8 business days.
4. Docs, samples, test cases — 1–2 business days.
5. Typical first delivery: 5–15 business days.

About our studio

We are an independent technical studio specializing in App interface integration and authorized API integration. Our engineers come from Ukrainian and CEE banks, payment gateways, anti-fraud teams and protocol-analysis backgrounds. We have shipped integrations across financial, e-commerce, mobility and social verticals, and we are familiar with NBU Open Banking, BankID NBU, GDPR and adjacent EU data-protection regimes.

• Fintech: microloans, BNPL, neobanks, cross-border payouts
• Protocol analysis: TLS pinning, signed payloads, webhook signing
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance

Contact

Tell us your target app and your concrete data needs (loan history, repayment schedule, KYC, payouts). We come back with a scope, a price and an indicative timeline.

Open contact page

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Can you cover Moneyveo, Miloan and CreditPlus too?

Long-tail topics covered

• CreditKasa API integration and statement export
• Ukraine microloan OpenBanking adapter
• BankID NBU consent flow for third-party fintech
• MiniKasa / MaxiKasa product catalogue sync
• UAH repayment schedule export to Excel / JSON / PDF
• Open Banking Ukraine 1 August 2025 alignment