Frequently asked questions

viaBanking is a software-only open banking aggregator with fund settlement verification. We provide a single integration with multiple open banking providers and confirm the actual settlement of funds into your own C2B account, not just that the payment was initiated.

viaBanking is for payment companies, fintechs, e-commerce and trading platforms. It fits any business that accepts bank payments through open banking and needs to know that funds have actually arrived, not just that the payment was initiated.

viaBanking is a software-only Technical Service Provider. You do not need a banking, EMI or payment licence to use viaBanking itself. Payment initiation is performed through licensed open banking providers (AISs and PISs), and your C2B account is opened directly with a C2B Account Provider. Any licensing related to your own business activity remains your responsibility, and our team will confirm what applies during onboarding.

Reach out through the contact form and we open a workspace with sandbox keys. You can build against realistic fixtures without a card and without production data.

Most teams reach a successful sandbox call the same day and complete a first end-to-end flow within one to two weeks, depending on scope.

30+ — markets across the EU / EEA / UK Confirm the required bank and service before integration.

2,500+ — banks & EMIs Service availability depends on the selected provider and bank.

Licensed AIS providers can offer consent-based account data services. viaBanking uses AIS only for read-only C2B credit verification. One-off payment initiation is live through licensed PIS providers. One-off payment initiation through licensed PIS providers is live. — viaBanking is a software / Technical Service Provider and Open Banking orchestration layer. Licensed AIS/PIS partners perform regulated actions. viaBanking is not a bank, payment processor or licensed AIS/PIS provider and does not hold or move customer funds. Scheduled, recurring and VRP payments are available only where supported by the selected provider and bank.

Support depends on what each bank provides under PSD2. Where a bank supports scheduled or recurring payment initiation, viaBanking passes those capabilities through in the standard data model.

Read-only C2B credit verification. — The merchant/business owns the C2B account, which is opened and serviced by its selected EMI, bank or C2B Account Provider. viaBanking connects to it to verify incoming funds in read-only mode. Balances, statements, transaction history and generic account aggregation are outside the current viaBanking product scope.

No. viaBanking is focused on open banking (AIS and PIS). Card acquiring, card issuing and card networks are not part of the product.

The user's payment consent flow is orchestrated by our licensed PIS provider partner, not by viaBanking. The end user authenticates directly with their account-issuing bank through that bank's own strong customer authentication flow. viaBanking never sees or stores banking credentials. The bank returns a consent that the end user can review and revoke at any time.

Confirm consent duration and re-authentication requirements with your licensed provider for the applicable jurisdiction.

Data is hosted in the European Union with reputable cloud infrastructure providers. Encryption in transit and at rest is applied by default.

Yes. We process personal data as a processor on behalf of our customers, in line with the GDPR and applicable national laws. Full details of how we collect, use, store and protect personal data are set out in our Privacy Policy.

No. Strong customer authentication happens on the user's account-issuing bank's own domain: the end user logs in with the bank's own credentials and completes SCA (second factor) directly with that bank. viaBanking never sees the login, the password or any other credential, only the access token the bank returns after the user authorises the connection.

We run regular internal reviews and engage third-party specialists for penetration testing. Details on our security posture are shared with customers under NDA during procurement.

The API is REST + JSON, so any HTTP client works. Reference examples for common languages are provided in the documentation.

The published payment request includes webhookUrl. Confirm callback authentication, delivery and acknowledgement requirements against the applicable API contract before relying on notifications.

Obtain the supported deduplication and retry contract for your integration. After a timeout or ambiguous write, check the original operation before submitting another payment; do not assume a header alone prevents duplicate execution.

Contact us for the applicable availability target, measurement period and service terms.

The sandbox simulates consent expiry, payment rejection, connection timeouts and rate-limit responses so you can exercise error paths without touching production data.

Confirm enabled services, production access, callback handling and retry behaviour with the integration owner. Follow the production checklist in Docs; completing sandbox tests alone does not confirm live availability.

Pricing is usage-based, with plans that scale by request volume and product mix (AIS, PIS, or both). The pricing page has current tiers, and larger volumes are quoted individually.

Yes. Sandbox access is free while you evaluate and build. No card is required to start.

Production traffic is billed under the selected plan from the first live call. Trial arrangements for enterprise procurement can be discussed with our team.

Usage is metered and invoiced monthly. Enterprise customers can arrange annual commitments through a signed order form.

The contact page lists the channels available for your workspace. Enterprise plans include a named contact and defined response-time targets.

Send incident reports or responsible-disclosure findings to the security contact listed on the contact page. We acknowledge reports quickly and coordinate on remediation.