Save months of bank-by-bank integration work
Bank Integrations, One API
ISECure gives you one interface for payment files, statements, and certificates: your product sends and retrieves, we handle the bank connection, accounts, certificates, and security.
Built for software companies: accounting, ERP, invoicing, and finance products that need bank connectivity.
bank traffic runs through ISECure
bank connectivity, certificates, and file traffic
use ISECure for production bank connectivity
TypeScript SDK
import { WSChannel } from "isecure-ts-client";
const data = new WSChannel({
Company: "Example Company",
Name: "Example User",
Email: "finance@example.com",
Phone: "+358401234567",
PublicKey: process.env.ISECURE_PUBLIC_KEY_PEM!,
BaseUrl: "https://ws-api.test.isecure.fi/v2",
Bank: "nordea",
Mode: "data",
Password: process.env.ISECURE_DATA_PASSWORD!,
});
const session = await data.login();
if (session.status !== "authenticated") {
throw new Error(`Login failed: ${session.status}`);
}
const files = await data.listFiles({
FileType: "CAMT",
Status: "NEW"
});
const [statement] = files.FileDescriptors;
const downloaded = await data.downloadFile(
statement.FileType,
statement.FileReference,
);Get started
First test call in three steps
The test environment is built for developer evaluation: inspect the API, create a test account, and make the first list or download call before production bank agreements are finalized.
1. Open the API or install an SDK
Use the OpenAPI description directly, or start with the TypeScript, Python, or PHP client.
2. Create a test account
SDK registration against the test endpoint creates the account and returns the integrator API key for later calls.
3. Make the first file call
Log in with the data account and call listFiles or downloadFile against test material.
Integration model
Why this is simpler than bank-by-bank integrations
Bank connectivity is more than uploading a file. A production-ready integration needs certificates, bank-specific behavior, audit trails, error handling, and secure key management.
Launch without months of bank-specific code
Start with the test API, send and retrieve bank files through one model, and add banks without another integration project.
Certificates and keys off the product team
ISECure handles PKI certificate enrollment, renewals, import/export, and KMS-encrypted storage in a PCI DSS level system.
Less exposure and compliance surface
The bank connection runs as a separate hosted service on AWS PCI DSS certified components. Your team does not have to build its own certificate vault, bank-connection monitoring, or high-security interface.
SDKs, OpenAPI, and PGP security
TypeScript, Python, and PHP clients speed up implementation. File material can require PGP signatures, and customer keys can be exported only to the customer's PGP key.
Architecture
What happens in the integration
Developers send and retrieve bank files through the API. ISECure handles bank WS traffic, certificates, key storage, and operational monitoring.
SDK coverage
Clients for different integration paths
The current PHP SDK and wscli remain available for command-line workflows and existing integrations. The TypeScript and Python clients bring the same model to modern services.
TypeScript SDK
AvailableFor Node.js and browser-adjacent services that need a typed client, predictable error types, and an OpenAPI-aligned developer experience.
Python SDK
AvailableFor background jobs, finance automation, and data pipelines where bank files are submitted and retrieved on a schedule.
PHP SDK and wscli
AvailableThe existing PHP client and command-line tool support current integrations, test runs, and onboarding workflows.
OpenAPI
AvailableThe API description, documentation, and command-line tool support testing, onboarding, and CI/CD workflows.
Coverage
Supported banks
ISECure connects the same integration model to banks such as Nordea, OP, Danske Bank, S-Bank/LähiTapiola, and Ålandsbanken, plus Handelsbanken, Aktia, POP Bank, Savings Bank, and OmaSP through Samlink and Crosskey connections. Bank files pass through the service without file-type-specific filtering or processing.
FAQ
Frequently asked questions
What do we need for testing and production?
You can start with the test environment, OpenAPI description, and SDKs. Production still requires the bank's corporate agreement, bank credentials, and certificates; ISECure handles the technical API, certificate process, and onboarding.
Which file types are supported?
ISECure does not filter or process bank files by file type. In practice, the same model supports the material allowed by the bank, including pain.001 payments, camt.053 statements, and other bank-specific WS-channel file types.
Can we use the SDK without vendor lock-in?
Yes. The API supports certificate import/export, and the customer's private key can be exported only to the customer's PGP key.
How is certificate renewal handled?
ISECure handles the PKI certificate lifecycle, renewals, and KMS-encrypted storage in a PCI DSS level system, so the product team does not have to build its own certificate vault.
How does pricing work?
Pricing depends on integration scope, banks, usage volume, and onboarding needs. Testing can start before the final production scope is agreed.
Where are data and keys hosted?
The service runs on AWS with PCI DSS certified components. Keys are stored with KMS encryption, and the bank connection runs as a separate hosted service from the customer software team.