Schedule a demo

Open banking in Austria: how bank payments work

Austrian banks open regulated interfaces to licensed providers, and payers approve each euro payment inside their own bank. This guide explains the roles involved, how consent and authentication work, and what businesses typically check before releasing goods.

Austria EUR

Who does what in an Austrian bank payment

Three parties take part in every payment. The obligations banks carry under European rules are summarised in the PSD2 open banking overview.

  1. The Austrian bank opens the door

    Each bank offering online payment accounts in Austria maintains a regulated access interface. European payment rules require it to accept instructions from licensed institutions acting with the customer's consent.

  2. The payer decides in their own bank

    The payer chooses their bank, logs in with the method they already use and approves amount and beneficiary there. Credentials are never shared with third parties.

  3. Licensed providers do the regulated work

    A licensed PIS provider initiates the payment and a licensed AIS provider can read account data with consent. Software layers may sit between a business and these providers to coordinate them.

Where bank payments stop being predictable

  1. Bank transfers that settle on their own schedule

    A classic transfer depends on when the payer gets round to it and how they type the reference. Finance teams find it hard to plan shipping or activation around a payment they cannot see coming.

  2. A status that promises more than it knows

    An accepted initiation records the payer's consent, not the arrival of funds. Businesses that act on that first signal can eventually meet a payment that never landed.

  3. Every provider speaks its own dialect

    Providers report statuses in their own terms and run their own support processes. A business working with several of them has to reconcile different vocabularies for the same events.

  • 1Currency for Austrian bank payments: the euro
  • 1Approval step per payment, completed inside the payer's own bank
  • 0Bank credentials shared with the merchant or the providers

How businesses restore predictability

  • Choosing how banks are reached

    Businesses either contract licensed providers directly or use an orchestration layer that decides which provider reaches which Austrian bank, so routing can change without touching checkout code.

  • Statuses with fixed meanings

    Mapping every provider's outcomes into one short internal vocabulary gives order logic a single set of rules, whichever provider carried the payment.

  • Acting on confirmed money

    Many businesses treat a payment as complete only when the expected amount reaches their own account, confirmed through a read-only account check, rather than when consent is given.

  • References that reconcile

    A structured reference that travels with the payment and reappears on the credit lets finance match each euro to an order without manual lookup.

Austria and Germany: close, not identical

Many companies sell into both markets from one team. The currency and habits are close; the banks are not. The German side is covered in the Germany open banking guide.

  • Same euro, similar rules

    Austrian and German payers both pay in euro, and both markets apply the same European payment rules, so payment requests and reporting can follow one model.

  • Separate banks, separate journeys

    Payers in Vienna and in Munich bank with different institutions and approve in different apps. Provider reach and approval flows are therefore assessed per country.

  • One model for the whole region

    Businesses selling into both markets often run reconciliation, order release and reporting on a single payment model, while bank access differs underneath.

What the payer approves, and nothing more

  • Login stays with the bank

    Passwords, codes and device approvals stay inside the payer's Austrian bank. Strong customer authentication happens there, not on the merchant's site.

  • Consent for one payment

    The payer approves one amount to one beneficiary with one reference. When that payment resolves, the consent has served its purpose.

  • Account checks are read-only

    An account information check with consent can only read data. Used on the business's own account, it confirms credits without moving money or touching the payer's account.

Four steps of a typical Austrian bank payment

The sequence is broadly the same across European markets. How providers reach individual banks is explained under bank connectivity.

  1. The payment is created

    The business prepares a request with the euro amount, a reference and the account that should receive it.

  2. Payer selects and approves

    The payer picks their Austrian bank and approves inside it; a licensed PIS provider initiates the payment.

  3. Statuses are reported

    The provider reports status changes, which the business or its software layer maps into its own vocabulary.

  4. Credit confirmed, goods released

    Once the amount is seen on the receiving account, the business releases the order or service.

Who collects from Austrian payers by bank

  • Online shops in Austria

    A pay-by-bank option beside cards, with parcels typically leaving the warehouse once the credit is confirmed.

  • DACH sellers

    Companies serving Austria and Germany from one storefront and one finance team, often on a shared payment model.

  • B2B invoices

    Payment links that open the payer's bank with amount and reference already set, reducing retyped transfers.

  • Bookings and deposits

    Travel, events and rentals where a reservation is held only once the deposit has actually arrived.

  • Platforms and marketplaces

    Collecting from Austrian buyers alongside other European markets with consistent statuses across countries.

Five capabilities and who handles each

CapabilityWhat it coversTypically handled by
Bank selectionWhich Austrian banks the payer can choose fromviaBanking, through licensed PIS providers
Payment initiationA regulated service on the user's payment consentLicensed PIS provider
AuthenticationInside the payer's own Austrian bankThe payer's bank
Status normalisationOne vocabulary across banks, providers and countriesviaBanking
Account credit confirmationRead-only account information on the receiving accountviaBanking, via a licensed AIS partner

Five questions about open banking in Austria

Short answers for product, engineering and finance teams learning how bank payments work for Austrian customers.

How does open banking work in Austria?

The payer chooses their Austrian bank, approves the payment there with strong authentication, and a licensed PIS provider initiates it through the bank's regulated interface. The legal background is explained on the PSD2 open banking page.

Who regulates open banking providers in Austria?

Payment initiation and account information services fall under European payment rules as applied in Austria. Providers need a licence or registration from a national supervisor in the EU, and a licence granted in one member state can be passported into Austria.

How does Austria compare with Germany?

Both markets use the euro and apply the same European rules, but banks and payer journeys differ. The neighbouring market is described on the open banking in Germany page.

What does SCA mean for payers in Austria?

Strong customer authentication means the payer confirms each payment inside their own bank with two independent factors, such as a device and a PIN or biometric. The merchant and the providers never see these credentials.

When is a bank payment actually complete?

An accepted initiation means the payer consented; it does not prove the money arrived. Many businesses wait until the expected euro amount is visible on their own account, for example via a read-only account check, before releasing goods.

Curious about open banking in Austria? Get in touch

This page is for information only. The viaBanking team is happy to talk through the Austrian market and open banking questions in general.

viaBanking is a software and technology provider. Regulated payment initiation and account information services are delivered by licensed partner institutions. viaBanking does not hold an AIS or PIS licence, does not execute bank payments and does not move funds.