Processing API
Prepare bank payment files with control and approval
Processing API helps your software prepare bank payment files through a controlled workflow before the real bank agreement and production certificates are ready. It checks the payment details, locks the approved version, and lets your application download the exact same file for local signing.
- Test environmentRegistration required · Paid subscription required · Request access
Product stage and access
Processing API is available in the ISECure test environment to subscribed customers by request. The product is Experimental, and qualification of bank- and country-specific payment files is still in progress. Production use, bank support, and service levels are not yet promised.
Request Processing API accessHow a payment file is prepared
- Choose the payment-file format for the bank and country within the user's access rights.
- Create a payment batch and add or correct its payments.
- Check the required details and lock one unchanged version for a person to approve.
- After approval, download the exact same file. The current technical output is ISO 20022 pain.001.001.09, and the TypeScript SDK verifies that the downloaded file has not changed.
Where Processing API's responsibility ends
- Processing API and Bank Connectivity use separate sign-in sessions.
- Bank Connectivity separately handles bank certificates and bank-file listing, download, and upload.
- The customer's private signing key stays in their own application. Processing API never receives the key and does not submit a payment to a bank.
- Approval in the ISECure workflow applies to the prepared file. It is not bank authorization or proof of a completed payment.
Choose test or production after signing
Processing APICreates and releases the checked payment file.
Customer applicationVerifies and signs the downloaded file under the customer's control.
Choose destinationUse the same File Exchange API with Bank Simulator now and a separately qualified real-bank destination later.
Test path · Bank Simulator
Upload the signed synthetic file to bank simulator through a separate File Exchange session, then retrieve pain.002, camt.054, and the updated camt.053.
The current Processing and Bank Simulator examples run separately. They do not yet correlate feedback automatically or safely retry an uncertain upload.
Open Bank SimulatorProduction path · Bank Connectivity
Upload the signed file to a supported bank only after the customer has separate Bank Connectivity access, a bank agreement, production credentials, and a qualified connection.
Simulator feedback is synthetic; it does not prove real-bank acceptance, a completed payment, or production qualification.