Submit File
Manual upload — the non-B2B portal channel. B2B, API and FileAct feed the same pipeline.
Drop file or click to browse
ISO 20022 XML (pain.001) · Tab / Pipe / Semicolon / Space / Caret / Tilde Content-based detection — extension is indicative only
＋ New delimited format? Map its columns →
Onboard a corporate's own layout — no code change (RFP §1.4)
Processing Result
Submit a file or select a test case to run the full pipeline.
Straight-Through Processing
Corporate ERP drops a file on SFTP → picked up event-driven → validated → transformed → CSV routed to CIB → status returned to the corporate's folder. Zero human intervention.
| Corporate | Protocol | Authentication | Polling | Status |
|---|
Live Channel Activity
Waiting for activity…
SFTP Folder Monitor — CORP-ABC
RFP §1.1 folder model: IN · ARCHIVE · STATUS · ERROR, plus routed CIB delivery
Infrastructure
Checking…
Output Volume by File Type Code
| Code | Output files | Records |
|---|
Inbound Files by Format
| Format | Files processed |
|---|
Recent Activity
| Time | Correlation ID | File | Outcome | Txns | Outputs |
|---|
Submit for Approval
Maker–Checker dual control (RFP §2.2.2-1.3). A file submitted by a Maker is held until a different Checker approves it.
Submit a payment file as Maker
Held in the approval queue — not processed until a Checker approvesSigned in as . Segregation of duties enforced — you cannot approve a file you submitted.
Approval Queue
Checker actions — approve to process, or reject with remarks.
| Reference | File | Attempt | Maker | Submitted | Status | Action |
|---|
Processing History
Complete audit trail — every file with correlation ID, SHA-256, outcome and generated artifacts. System of record: PostgreSQL.
| Processed | Correlation ID | Channel | Input file | Format | Outcome | Acc | Rej | Artifacts | Audit |
|---|
Payment File Type Codes
Bank-specific code table — new payment purposes onboard via configuration, no code changes (RFP §1.4-C).
| Payment type | Code | Description | CCY |
|---|
Format Detection Profiles
Content-based detection — extensions are indicative only (RFP §1.2).
| Profile | Delimiter | Detection | Status |
|---|
Splitting Rules (RFP §1.4-B)
| Rule | Value | Configurable |
|---|
Output File Naming Rules
Rule-based naming per channel / format / file type — configurable without code changes (RFP §1.4).
| File type | Pattern | Example |
|---|