viaBanking
Schedule a demo

Docs · v1

Docs

Guides and concepts: auth & consent, account data, payments, webhooks and going live. Full endpoint spec in the API Reference.

Get sandbox access Schedule a demo

01 · How-to

Guides & concepts

Start with the Quickstart, then move through auth, data, payments and going live. Every concept links inline to its field-level entry in the API Reference.

  • Start here

    Quickstart

    Get a sandbox key, create a consent and make your first call. No card needed to start.

    Jump to Quickstart
  • AIS + PIS

    Auth & consent

    How user consent works and how viaBanking orchestrates the login at each bank through one consent flow.

  • AIS

    Account data

    Read balances and transactions from any C2B account across Europe through one data model.

  • PIS

    Payments

    Initiate account-to-account payments from a single connection and track each step in real time.

  • Async

    Webhooks & statuses

    Subscribe to signed events so you learn about payment settlement instead of polling. Verify signatures and acknowledge fast.

  • Reliability

    Errors & retries

    Match on stable error codes, respect Retry-After, and use Idempotency-Key so retried writes never double-charge.

  • Sandbox

    Testing

    Drive AIS and PIS against realistic fixtures. Simulate consent expiry, payment rejection and rate-limit responses.

  • Go live

    Go-live checklist

    Swap sandbox for live keys, register production webhook URLs, enable idempotency in writes and turn on alerting.

02 · Quickstart

Three steps to a live response

Grab a key, set consent, and call the API. Most teams reach a live sandbox call the same day.

  1. Get a key

    Contact sales to open your workspace. Sandbox and live keys land in the dashboard — pick sandbox to start.

  2. Create a consent

    POST /v1/consents with the bank id, redirect the user to auth_url, and store the returned consent id.

  3. Call the API

    GET /v1/accounts for AIS or POST /v1/payments for PIS with the same Bearer token. Full field-level spec in the API Reference.

03 · Go-live checklist

Ship without surprises

Six items separate a working sandbox from a safe production. Field-level shapes live in the API Reference.

  1. Swap sk_sandbox_… for sk_live_… in the deployed environment only.
  2. Register the production webhook URL and verify HMAC signatures on every event.
  3. Send an Idempotency-Key on every POST /v1/payments so retries stay safe.
  4. Handle 429 with the returned Retry-After header instead of a fixed sleep.
  5. Alert on payment.failed and consent.revoked events, not on 2xx polling.
  6. Route around banks in /v1/status = degraded before you retry.

04 · At a glance

One integration. Clear specs.

  • AIS + PIS

    Account data and payments in one connection

  • 2,500+

    Banks & EMIs in one layer

  • REST + JSON

    One data model across every C2B account

  • < 1 day

    From sandbox key to your first live call

Free sandbox · No card needed

Ready to build? Get sandbox access.

Start with the Quickstart above, then keep the API Reference open beside it.

Get sandbox access Schedule a demo