This page describes the customer journey from credential handover through your first connection. It is tool-agnostic: you may use any desktop SFTP client, command-line SFTP, treasury system, or managed file transfer (MFT) product that supports SFTP and SSH key authentication.
For file formats, folder layout, processing behaviour, and sample pain.001 files, continue with Bulk Payments via SFTP.
You will use SFTP to submit batches of multiple payment instructions in ISO 20022 pain.001 files. Each file can contain many payments; you can also submit multiple files over time as your operational schedule requires. Results and reconciliation artefacts are returned on the same SFTP endpoint (see the technical guide for /input, /output, and /archive).
After onboarding, BCB supplies:
| Item | Description |
|---|---|
| SFTP host | The server hostname or URL you connect to (environment-specific; UAT details are in the technical guide). |
| Username | A unique provisioned username for your organisation. |
| Private key | An SSH private key file used instead of a password. BCB holds the matching public key on the server side. |
You may receive these out of band (for example by secure email, your relationship manager, or an agreed key-exchange process). Treat the private key like a secret: restrict who can read it, do not share it in chat or ticketing systems, and do not commit it to source control.
Secure the credentials
Store the private key in a location only authorised staff and systems can access. If you use automation, use a secrets store or HSM pattern your organisation already approves.Create a connection profile in your SFTP software
In your chosen tool, create a new SFTP (SSH File Transfer Protocol) connection and enter:- Protocol: SFTP (not FTP).
- Host: the hostname BCB gave you.
- Port: typically
22unless BCB specifies otherwise. - Username: your provisioned username.
- Authentication: SSH private key (select the key file BCB provided).
Some applications require the key in a particular format (for example.ppkon Windows); convert only using trusted tooling if needed.
Connect and verify the workspace
After a successful login, you should see your client-isolated directory tree, including folders such as/input,/output, and/archive. If anything is missing or you cannot authenticate, contact BCB support with the error message from your client (not the key material).Read the technical guide and test
Use Bulk Payments via SFTP to learn where to drop files, how processing and statuses work, and to download samplepain.001files for UAT. Build or export your productionpain.001according to that specification before go-live.
- Upload completed
pain.001files to/inputonly, unless BCB instructs otherwise. - Poll or monitor
/outputforpain.002and reconciliation files (camt.053) as described in the technical guide. - For API status polling or optional webhooks (if enabled for your tenancy), see the technical guide’s status section.
For onboarding and integration support, contact api@bcb.bm.