ISECure products
Choose the product that fits your workflow
Compare each product’s maturity, available environment, registration and subscription requirements, and how to get access.
Start before the bank agreement
Test the payment-file path now, point the same API at a real bank later
The products stay separate: Processing API prepares the file, your application signs it, and Bank Simulator tests the File Exchange feedback path. Once the agreement and production certificates are ready, the same File Exchange API targets the separately qualified real-bank connection.
- Processing APIPrepare bank payment files with control and approval.
- Your applicationVerifies and signs the exact same bytes locally.
- Bank SimulatorReturns synthetic pain.002, camt.054, and camt.053 files.
- Bank ConnectivityTargets a separately qualified real-bank connection through the same File Exchange API.
Move corporate bank files through one managed interface.
Use requires the customer's bank agreements. Exact bank and file support depends on the agreement and qualified profile.- Test environmentRegistration required · No subscription required · Open registration
- ProductionRegistration required · Paid subscription required · Standard onboarding
Beta
Start testing the complete file flow before the real bank agreement and production certificates are ready.
Only for bank simulator at https://ws-api.test.isecure.fi/v2. Simulator evidence does not prove real-bank behavior.- Test environmentRegistration required · Paid subscription required · Request access
Experimental
Prepare bank payment files with control and approval.
Available in the ISECure test environment to subscribed customers by request. Qualification of bank- and country-specific payment files is still in progress; production use, bank support, and service levels are not yet promised.- Test environmentRegistration required · Paid subscription required · Request access