bankintegration.dk

What It Is

BankIntegration.dk is a Danish bank integration service from BankIntegration ApS for ERP and financial system providers. Its core positioning is not as a general-purpose developer platform, but as a way for ERP vendors to embed customers’ bank transaction data, balances, and payment capabilities into their own systems, reducing the complexity and communication overhead of integrating with banks one by one.

Core Capabilities and Technical Model

The platform provides a REST API that is called exclusively over HTTPS. The public documentation lists endpoints for sending payment requests, checking payment status, retrieving account transactions, and retrieving account balances. ERP providers must first contact support to obtain an API key and an ERP name/code, and each request must include an authentication header. Its main advantage is unified connectivity to Danish banks and savings banks, enabling ERPs to support daily automatic import of account transactions, bank reconciliation, balance checks, and real-time payments from within the system. The website also notes that the customer onboarding wizard can be branded with the ERP vendor’s name and visual design.

Protocols, Ecosystem, and Documentation

The service supports both WebService protocols and OpenBanking/PSD2 protocols. WebService is a more stable and more fully featured corporate banking protocol: it can receive account transactions and initiate outgoing payments, but usually requires activation by the bank and may involve fees. OpenBanking can be set up quickly via MitID and typically needs renewal about every six months, but it can only receive account transactions and cannot initiate payments. In terms of documentation, the FAQ provides fairly detailed explanations of account setup, adding companies, bank agreements, renewal, accounts, and integration code workflows. The API documentation also lists the main endpoints, status codes, and authentication requirements, although the captured content does not show the full details of the authentication algorithm.

Pricing and Limitations

The public text does not provide clear platform pricing; it only mentions access to bank price lists and the option to contact sales. Bank agreement fees depend on the specific bank. WebService usually has setup and ongoing fees, while OpenBanking is typically free on the bank side. The main limitation is that the service is tightly tied to local Danish systems such as Danish banks, CVR, and MitID. Its helper component is currently explicitly listed as .NET C# 4.5.1, with components for other languages still under development.

Who It’s For and Access from China

It is best suited for ERP, accounting, and finance SaaS vendors serving Danish business customers, especially teams that want to quickly offer bank transaction syncing, reconciliation, and payment features. For companies targeting Chinese businesses or the Chinese banking system, its value is limited; local corporate bank connectivity, the Yonyou/Kingdee ecosystems, or bank open platforms may be more appropriate. The available text does not make it possible to determine access conditions from mainland China, and supported payment methods are not disclosed.