SumUp (Austria): Open Banking & API Data Access

SumUp gives Austrian merchants a business account tied to their card-payment takings, and open-banking.io lets you reach that account's balances and transactions under PSD2 — without certificates, without an eIDAS setup, and without SumUp ever handing your data to a third party in the clear. SumUp (Austria) accounts carry the BIC SUMUIE22, cover business account types, and grant a consent that stays valid for up to 180 days before you re-approve.

The design principle is simple: your data is decrypted on your own device with a key only you hold. open-banking.io stores your public key and nothing that can unlock your records, so the service is genuinely zero-knowledge.

How to connect SumUp

Connecting happens entirely inside the open-banking.io dashboard — there is no code, endpoint, or key involved at this stage.

  1. Sign up for open-banking.io and set an encryption passphrase. Your key pair is generated locally on your device from that passphrase.
  2. In the dashboard, search for SumUp and choose the business account type.
  3. You're redirected to SumUp's own secure login, where you approve access (the standard PSD2 consent screen).
  4. Once approved, your SumUp accounts sync back into the dashboard, and the consent runs for up to 180 days.

At no point are you sending credentials to open-banking.io or being routed through a developer API — you authenticate directly with SumUp.

Access your data

Reading SumUp data programmatically is an optional step you take after the connection exists. On the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. From there you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly. Every request carries the X-Api-Key header, and each response is decrypted locally with your own key.

That split matters: an API key alone only ever returns ciphertext from the servers. Without your private key on your machine, the payload stays unreadable — which is exactly what "zero-knowledge" buys you. The CLI and SDK only read and sync connections you already made in the dashboard; there is no connect command.

All of this runs at roughly EUR 3/month, across 2,600+ EU and UK banks.

FAQ

Do I need an eIDAS certificate for SumUp?

No. open-banking.io is certificate-free — you approve access on SumUp's own login and skip the regulated-certificate overhead entirely.

Can open-banking.io read my SumUp transactions?

No. The servers hold only your public key. Your records are decrypted on your device with a private key that never leaves it.

Up to 180 days. After that you re-approve access through SumUp's consent screen to keep syncing.

Ready to start? Visit open-banking.io.