Finland · BUDGET APP BANK SYNC
Budget with Holvi in Pigget.
Connect Holvi to Pigget and bring transactions into a zero-based budget automatically—without routine CSV imports.
Join the Pigget betaHolvi SYNC DETAILS
What Pigget can bring into your budget.
Automatic bank sync keeps your plan grounded in real spending. Pigget uses a read-only Synci connection powered by official European open-banking APIs: authentication happens with your bank, and the connection cannot move money.
Capabilities are supplied by Pigget’s connection partner and can change when Holvi updates its API. A temporary bank outage does not necessarily mean support has ended.
FROM TRANSACTIONS TO A PLAN
Bank sync that supports active budgeting.
Pigget is more than an expense tracker. Imported Holvi transactions are matched to the categories and decisions in your zero-based budget.
- 1
Connect Holvi
Approve read-only access in the bank’s own authentication flow. Pigget and Synci never receive your bank password.
- 2
Import transactions
Bring available accounts, balances and transactions into Pigget instead of repeatedly downloading CSV files.
- 3
Keep the budget honest
Review spending, assign categories and see how each purchase changes what is still safe to spend.
Holvi CONNECTION FAQ
Useful details before you connect.
Can I connect Holvi to a budgeting app?
Yes. Holvi is available in Pigget through Synci’s read-only European open-banking connection. You can import transactions into Pigget and use them in your budget.
Does Holvi provide pending transactions?
Not currently. Holvi may only expose booked transactions through its open-banking API.
Can Pigget sync Holvi credit cards?
Not necessarily. Holvi does not currently report credit-card support through this connection; current and savings accounts may still be available.
How much Holvi history can I import?
Up to 730 days of transaction history may be available when you first connect.
How often do I need to reconnect Holvi?
The current maximum consent period is 180 days. You may be asked to approve read-only access again after that.