SumUp API Access via Open Banking (Denmark)
SumUp is best known as the card reader in the pocket of Danish cafés, market stalls and freelancers, but the money it settles lands in a real business account — and that account falls under PSD2. With open-banking.io you can reach your SumUp (Denmark) balances and transactions without wrestling with bank certificates, sandbox registrations or eIDAS paperwork. You sign up, the software generates your encryption keys on your own device, and everything you pull back is decrypted locally with a key that never leaves your hands.
SumUp in Denmark operates under BIC SUMUIE22 and issues business accounts, which suits the merchants and sole traders who take payments through it. Consent you grant lasts up to 180 days before SumUp asks you to renew, matching the PSD2 ceiling.
How to connect SumUp
Connecting happens entirely inside the open-banking.io dashboard — there is no API call, key or code in this step.
- Create your open-banking.io account and set an encryption passphrase. Your keys are generated locally, so only you can later unlock the data.
- In the dashboard, search for SumUp and choose the business account type.
- You are redirected to SumUp's own secure login, where you approve access on their consent screen. open-banking.io never sees your SumUp credentials.
- Approved accounts sync straight into your dashboard, ready to view.
Access your data
Reading SumUp data programmatically is an optional step you take after connecting. 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 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 on your machine. The API key alone only ever returns ciphertext; without your private key, nobody — not even open-banking.io — can read it.
That is the point of the zero-knowledge design: the servers hold only your public key, so your SumUp transaction history stays yours. No certificates, no per-bank onboarding, and pricing at roughly EUR 3/month.
Do I need a developer account to connect SumUp?
No. Connecting is done in the dashboard. API keys and credentials.json matter only if you later want to read data with code.
Can open-banking.io read my SumUp transactions?
No. Data is decrypted on your device with a key only you hold. The service stores only your public key.
How long does my SumUp consent last?
Up to 180 days, after which you re-approve access on SumUp's own consent screen.
Ready to start? Visit open-banking.io.