viaBanking
Schedule a demo

Open banking API · For developers

Open banking API for developers

One open banking orchestration API a developer can use to reach many licensed third-party AIS and PIS providers behind one contract. The endpoints cover the user's payment consent flow, payment initiation and C2B account credit verification, so a developer wires the integration once and any supported bank works on the same code path. Regulated services stay with licensed third-party AIS and PIS providers; viaBanking is the software layer that handles connectivity, routing and normalisation on top.

Read the docs Get sandbox access

What's available

What a developer needs to build

  • 01

    Sandbox

    A free sandbox is available on request. Use it to wire the user's payment consent flow, run PIS calls and test webhooks against realistic fixtures, so a developer validates the full flow before touching production.

    Read the docs
  • 02

    Reference

    The reference covers the user's payment consent endpoints, payment initiation and the C2B account credit-verification endpoint. One open banking API contract sits on top of many licensed third-party AIS and PIS providers, so a developer learns the surface once.

    Open the reference
  • 03

    Fintech example

    Building for a fintech team? See how the same integration ships A2A payment initiation, C2B account credit verification and market expansion by configuration.

    For fintech

Why build on it

One open banking API, many licensed partners

  • One surface, many partners

    One open banking API in front of many licensed third-party AIS and PIS providers, so a developer uses one contract across every supported bank without maintaining a connector per bank.

  • Regulated calls stay licensed

    Payment initiation and account access run through licensed third-party AIS and PIS providers. Strong customer authentication is hosted and verified by the user's account-issuing bank. viaBanking is the software layer.

  • Signed webhooks, stable errors

    Every state change surfaces as a signed webhook event across every licensed provider. Errors map to a stable set of codes with Retry-After hints, so a developer writes retry and reconciliation logic once, not per bank.

Cross-links

Same contract. Many licensed partners behind it.

Wider catalogue: bank API. Fintech workflow: open banking API for fintech. Regulated services are delivered by licensed third-party AIS and PIS providers.

Ready to build

Start building on the open banking API

The sandbox is available on request. Contact us for developer access and use the reference to wire the user's payment consent flow, PIS-initiated payments and C2B account credit verification on one integration.

Get sandbox access Read the docs

viaBanking is a software provider; regulated services are delivered by licensed partner providers.