viaBanking
Schedule a demo

Open banking · Fintech

One open banking connection for every fintech product

The viaBanking fintech platform connects finance and financial services teams to open banking, licensed PIS providers, C2B account credit verification, and the management tooling a regulated fintech financial services product needs. Every bank, every account, every payment flow on one connectivity API. AIS account information reads on the roadmap.

Talk to sales Explore the API
  • OneConnectivity API
  • 2.5k+Banks & EMIs reachable
  • PISvia licensed providers
  • C2BAccount credit verification
  • SVCCustomer support included

Definition

What open banking for fintech means on viaBanking

In business terms, open banking for fintech is the connectivity layer a modern financial services product uses to reach every bank a customer holds an account with. The fintech team writes to one open banking API; the customer authenticates with their own bank; the licensed PIS partner performs the regulated payment step; and the fintech product pays into any bank account through the same open banking service.

Technically, viaBanking is the software and orchestration layer. The platform routes bank payment initiation to licensed PIS providers, verifies C2B account credit on the receiving account, and logs user's payment consent, SCA and payment audit trails for the fintech compliance team. The consent is captured on the customer's own bank and later referenced by the platform. On-demand AIS balance and transaction queries are on the product roadmap, delivered later through licensed AIS providers. Read the connectivity primer on the Banking API page or the platform overview on the Open banking API page.

Bundled with the connectivity API

One contract for connectivity, evidence logging and management tooling

  • Payment initiation routing
  • C2B account credit verification
  • User's payment consent capture & logs
  • Payment audit trail
  • Reconciliation feed
  • Sandbox & docs
  • On-demand AIS balance queries · roadmap

Why fintech is different

Fintech teams need more than a bank API

A regulated fintech is not a bank engineering department. Speed to market matters. Compliance evidence matters. Financial data quality matters. The four differences below are what a fintech gets on viaBanking that a bare bank API does not deliver.

  • 01

    Speed to market on every bank

    A fintech that wires banks one at a time takes quarters to launch. On viaBanking the fintech ships against one open banking API on day one. The fintech pays out a sandbox payment before the first stand-up meeting.

  • 02

    Provider licensing stays with providers

    PIS bank payment initiation is performed by our licensed PIS partners. AIS account information reads will come later through licensed AIS partners. The fintech does not have to hold a PIS or AIS licence to launch on open banking; regulated services stay with the provider.

  • 03

    Logs your compliance team can use

    Every user's payment consent capture, SCA reference and payment audit event is logged and surfaced continuously. Your compliance team uses that data to satisfy the regulator. viaBanking is the software layer; regulatory compliance stays with your team and your provider partners.

  • 04

    Finance-grade payment reconciliation

    A fintech financial team needs one payment reconciliation feed across every bank. viaBanking surfaces C2B account credit against the initiated payment, so financial teams read real settlement, not just the bank's first status. On-demand AIS financial data queries will follow on the roadmap.

For whom

Every fintech vertical, one open banking service

Six fintech segments ship on the same open banking API. Same connectivity, same compliance evidence, same management tooling, different financial services product.

  1. Neobank

    Neobanks & digital banks

    Fintech neobanks collect customer funds via bank payment initiation on the open banking API; the transfer moves bank-to-bank into the neobank's C2B account. viaBanking then confirms the credit landed with the C2B account credit verification service before the neobank activates the customer account.

  2. Payments

    Payment fintechs

    Payment fintechs initiate customer bank payments via licensed PIS partners; funds move bank-to-bank into the merchant's C2B account. viaBanking surfaces status callbacks and confirms real credit against every initiated payment on one connectivity API.

  3. Lending Partly on roadmap

    Lending fintechs

    Lending fintechs collect loan repayments via customer bank payment initiation; funds move bank-to-bank into the lender's C2B account, and viaBanking confirms each repayment credit with the C2B account credit verification service. On-demand AIS balance queries via licensed AIS partners sit on the roadmap.

  4. Wealth Partly on roadmap

    Wealth & investment

    Wealth platforms collect customer top-ups via bank payment initiation; funds move bank-to-bank into the platform's C2B account. viaBanking confirms each credit with the C2B account credit verification service. On-demand balance queries via licensed AIS partners sit on the roadmap.

  5. BaaS

    BaaS & embedded finance

    Banking-as-a-service teams embed the open banking API inside their client products. Every downstream financial services brand gets bank payment initiation routing and C2B account credit verification on one contract.

  6. Insurtech

    Insurtech & claims

    Insurtech fintechs collect premiums via bank payment initiation; funds move bank-to-bank into the insurer's C2B account, and viaBanking confirms each credit with the C2B account credit verification service. Claim pay-out initiation runs on the same open banking API via licensed PIS partners.

What we ship

Eight capabilities on one open banking API

Every fintech capability below is an endpoint on the same open banking API. Pick the ones your fintech product needs; the rest sit dormant on the same connectivity contract.

  • PIS

    Payment initiation routing

    Initiate customer bank payments through licensed PIS partners. viaBanking handles the API and provider selection; the licensed PIS partner sends the initiation instruction. Funds move bank-to-bank.

  • VFY

    C2B account credit verification

    Read-only API call to the customer's bank confirms whether funds have actually landed on your C2B account. Fintech finance teams stop acting on the bank's first status; they release goods when real credit is on the account.

  • MGT

    User's payment consent management

    One dashboard for user's payment consent management across every bank connection. Track scope, expiry, refresh and revocation on one open banking layer.

  • LOG

    Evidence you log

    User's payment consent capture, SCA references and payment audit trails are surfaced continuously. Your compliance team uses that data to satisfy the regulator; viaBanking does not perform compliance for you.

  • EVT

    Webhook management

    Signed webhook events on every state change. Payment status, consent updates and account credit callbacks surface on one webhook management channel.

  • SBX

    Sandbox management

    Free sandbox that simulates provider responses. Fintech teams test the whole open banking journey without a card and without a paid contract.

  • AIS Roadmap

    On-demand balance & transaction queries

    On-demand query for a specific customer bank account balance or transactions via licensed AIS providers. On the roadmap; continuous or real-time balance display is not on the plan.

  • SUP

    Customer support service

    A customer support service for fintech engineers, compliance and finance teams. Included on every open banking service tier.

Evidence logs & management

The data your compliance team uses to satisfy the regulator

viaBanking logs and surfaces open banking data. Your compliance team uses that data. Regulatory interpretation, licence responsibility and the audit response stay with your team and with the licensed provider partners. viaBanking is the software layer; it is not a compliance-as-a-service.

Evidence logs

Data the compliance team can query

Every open banking call the platform routes is logged. Every user's payment consent capture and every SCA reference is recorded on the customer's own bank side and surfaced back through the API. The compliance team of a regulated fintech queries that log to answer its regulator. viaBanking does not perform your compliance work; it makes the underlying data legible.

  • User's payment consent capture logs with SCA reference on the customer bank
  • Payment audit trail per bank payment initiation call
  • Provider licence status (surfaced as reported by the provider, not as a viaBanking guarantee)
  • Immutable log retention windows configurable per fintech tier
  • Export to your own audit surface at any time
Management dashboard

Fintech management dashboard

One management dashboard for the fintech compliance, finance and product teams. User's payment consent management, bank connection management, payment routing management and C2B account credit reconciliation share one open banking management surface across every bank the fintech touches.

  • User's payment consent management per user, per bank, per account
  • Payment routing management per market
  • Bank connection health management
  • Finance reconciliation and cash management
  • User management with role scopes for compliance

Financial services on one platform

Every financial service, one open banking connectivity contract

Every fintech that ships on viaBanking is a regulated financial services product. The platform bundles the financial services connectivity a modern fintech needs into one open banking service, and lists exactly which financial services are live today vs planned for the roadmap.

Live financial services
  • Payment initiation Routed to a licensed PIS partner; the licensed provider performs the regulated payment step.
  • C2B account credit verification Read-only API call to the customer's bank confirms whether funds have actually landed on the C2B account against the initiated payment.
  • User's payment consent management User's payment consent capture happens on the customer bank; the platform stores the reference, tracks refresh/revocation and surfaces per-scope logs.
  • Payment audit logs Every bank payment initiation call recorded with provider licence reference and user's payment consent reference.
  • Reconciliation feed Real C2B account credit surfaced against the initiated payment, not just the bank's first status.
  • Customer support service A customer support service for engineering, compliance and finance teams. Included on every tier.
Roadmap financial services
  • On-demand balance queries Query a specific customer bank account balance on-demand via licensed AIS providers. Continuous or real-time balance display is not on the plan.
  • On-demand transaction queries Query recent transactions for a specific customer bank account within bank-permitted windows. Roadmap; delivered through licensed AIS partners.
  • Derived analysis views Derived-data views on top of on-demand AIS reads. Roadmap; scope depends on the AIS layer above.

Every financial service on the platform, live or roadmap, is routed through a licensed provider partner. The fintech legal team does not inherit the licence to run each financial service. New financial services shipping on the platform become available to every fintech financial services product without a rewrite. Financial services teams pick which financial service to enable per market, per fintech brand and per customer segment. The financial services roadmap is documented on one developer surface, so the fintech financial services team knows exactly which financial service is live today and which financial service is planned next quarter.

Payment orchestration

Bank payment initiation, routed through licensed partners

The viaBanking payment orchestration layer routes every bank payment initiation to a licensed PIS partner. The fintech product calls one open banking API to start a payment. The platform selects the right licensed PIS provider for the market and the bank in question. The licensed partner performs the regulated payment step. viaBanking surfaces status, webhooks and reconciliation on one payment management dashboard. See the Payment initiation API page for the raw API surface and Payment initiation services for the bundled pay-by-bank stack.

viaBanking does not move funds. Funds move bank-to-bank between the customer's bank and the C2B account; settlement is the bank's step, not the platform's step. What viaBanking guarantees is one API for every bank payment initiation, one payment status surface, one C2B account credit reconciliation feed and one payment audit trail for the fintech compliance team. Every payment call is logged with the provider licence reference, the user's payment consent reference and the customer bank reference.

Companion service

Confirm real credit on your C2B account, not just the bank's first status

After the customer's bank payment initiation completes, the platform performs a read-only API call to the customer's bank to confirm the funds actually landed on your C2B account. The fintech releases goods or services on real credit, not on the bank's first "success" status. The verification response is stored alongside the payment audit trail on the same open banking log surface. Read more on the Bank account verification API page.

Why viaBanking

Six advantages every regulated fintech gets

  1. 01

    One connectivity API for every bank

    Fintech engineering teams write to one open banking API. Every payment initiation call, user's payment consent capture and account credit callback goes through the same connectivity signals; the money itself moves bank-to-bank between the customer and the C2B account.

  2. 02

    Regulated services stay with providers

    Licensed PIS partners perform the regulated payment initiation step; licensed AIS partners will perform on-demand account queries once that scope ships. Fintech legal teams do not inherit the licence.

  3. 03

    Logs your compliance team can query

    User's payment consent capture, SCA references and payment audit trails surface continuously. Your compliance team uses that data; viaBanking is the software layer, not a compliance-as-a-service.

  4. 04

    Real settlement, not just first status

    The C2B account credit verification service confirms when funds actually land on the C2B account. Finance and product teams stop acting on the payer's consent alone.

  5. 05

    Payment routing without a rewrite

    Add a new market by switching on more banks. Payment routing management is a config change, not a code change, on the open banking platform.

  6. 06

    Customer support included

    A customer support service ships with every open banking service tier. Fintech engineers get answers on the same day, not on a queue.

Integration timeline

From connectivity contract to production in five steps

The same five steps every regulated fintech takes on viaBanking. Sandbox on day one, production in weeks, not quarters. New banks join the platform without a new integration on the fintech side.

  1. 01

    Sign the connectivity contract

    Fintech team signs the developer terms and gets sandbox keys the same day. No procurement email per bank.

  2. 02

    Wire user's payment consent and SCA

    Redirect the customer to their bank. The bank runs SCA and captures the user's payment consent. viaBanking stores the consent reference and audit trail.

  3. 03

    Call the open banking API

    Call the payment initiation and C2B account credit verification endpoints. Same open banking API, every bank, every fintech vertical. AIS on-demand balance queries on the roadmap.

  4. 04

    Handle webhooks and status

    Listen for signed webhook events. Reconcile payment status and C2B account credit against the initiated payment on one management surface.

  5. 05

    Ship to production

    Promote your code, point at live banks and monitor every fintech flow from one dashboard. Consent and payment audit logs stay surfaced continuously.

Comparison

Fintech stack without vs with viaBanking

Six line items that shift from the fintech engineering backlog to a single open banking management surface.

  Fintech without viaBanking Fintech on viaBanking
Bank access Fintech wires new integration per bank One connectivity API to every bank
PIS licensing Fintech buys per-provider contract Payment initiation via our licensed PIS partners
User's payment consent Manual per bank, per market One user's payment consent management dashboard
Audit evidence logs Assembled per audit, per fintech team Surfaced continuously; compliance stays with your team
Payment monitoring One monitoring stack per PSP One payment monitoring surface
Settlement view Bank's first status treated as success C2B account credit surfaced against the initiated payment

Use cases

What fintech teams actually ship on the platform

  1. 01

    Fintech customer onboarding funding

    The new customer funds their fintech account via a bank payment initiation on the open banking API; funds move bank-to-bank into the fintech's C2B account. viaBanking confirms the credit landed with the C2B account credit verification service before the fintech activates the customer account.

  2. 02

    Pay-by-bank checkout

    Payment fintech initiates the customer bank payment through a licensed PIS partner; funds move bank-to-bank into the merchant's C2B account. viaBanking surfaces payment status and real credit reconciliation on one management dashboard.

  3. 03

    Loan repayment collection

    Lending fintech collects borrower repayments via customer bank payment initiation; funds move bank-to-bank into the lender's C2B account. viaBanking confirms each repayment credit with the C2B account credit verification service.

  4. 04

    Insurance premium collection

    Insurtech fintech collects premiums via customer bank payment initiation; funds move bank-to-bank into the insurer's C2B account. viaBanking confirms every premium credit landed against the initiated payment. See coverage on the pricing page.

  5. 05

    Marketplace pay-out initiation

    Marketplace fintech initiates seller pay-outs via a licensed PIS partner; funds move bank-to-bank to the seller's bank account. Payment routing management picks the licensed PIS partner per market on one open banking API.

  6. 06 Roadmap

    On-demand balance queries

    Wealth or lending fintech queries a specific customer bank account balance on-demand via a licensed AIS partner as one financial data point. On the roadmap; continuous or real-time financial balance aggregation is not on the plan.

The team

Built by fintech engineers, for fintech engineers

The viaBanking team ships open banking connectivity every quarter. The compliance team ships new provider evidence every month. The management dashboards for financial services teams are built with a fintech finance team in the room. Read the wider services story on the about page or browse open roles on the careers page.

The solutions overview maps the open banking platform to real fintech verticals and the developer docs is where the fintech engineering team gets to a green build. Earlier-stage teams start on the open banking for startups page. Every fintech question a compliance, finance or product services team asks has a page on this site.

FAQ

Common questions from fintech teams

What is open banking for fintech?

Open banking for fintech is the connectivity layer a modern financial services product uses to initiate bank-to-bank payments and verify bank accounts. viaBanking is the software layer; the regulated PIS payment step is performed by licensed partner institutions. AIS account information reads are on the roadmap and will follow through licensed AIS partners.

Which fintech verticals can use the platform today?

Payment fintechs, neobanks, banking-as-a-service teams, insurtechs and marketplaces run on the live payment initiation and C2B account credit verification scope. Lending fintechs and wealth platforms that need broader AIS data reads sit on the roadmap and can start with the live scope today.

Does viaBanking manage our regulatory compliance?

No. viaBanking logs data your compliance team uses. Regulatory interpretation, licence responsibility and the audit response stay with your team and with the licensed provider partners. viaBanking is a software layer, not a compliance-as-a-service.

Do you provide AIS and PIS licences yourself?

No. viaBanking is a software and technology provider. PIS payment initiation is performed by licensed partner institutions. AIS account information is on the roadmap and will be delivered by licensed AIS partners. The platform routes API calls to those licensed providers.

What management tooling does the platform include?

One dashboard for user's payment consent management, bank connection health management, payment routing management, sandbox management and customer support. Finance teams read one management view for the live scope across every bank in the platform.

How fast can a fintech team go live?

Any fintech team can pay out a sandbox payment on day one. Production roll-out for PIS payment initiation and C2B account credit verification across the banks a fintech needs usually takes two to four weeks of API integration work.

Ready to build

Ship your fintech product on open banking today

Free sandbox. One open banking API for every bank. Talk to us about the compliance and management scope your fintech product needs, then browse pricing on the pricing page.

Talk to sales Explore the API