Submit File
Manual upload through the portal. API and any future configured delivery adapters use the same validation and transformation pipeline.
Drop file or click to browse
ISO 20022 XML · Delimited text · Excel (.xlsx) · PDF · Single-file ZIP Content-based detection — extension is indicative onlyProcessing Result
Submit a file or select a test case to run the full pipeline.
External Delivery Adapters
Production SFTP and a live SWIFT Alliance Gateway connection remain not configured until real endpoints, keys and bank acknowledgements are supplied. Isolated test adapters demonstrate the SFTP+PGP and FileAct+RMA mechanics with real cryptography and envelope handling.
| Corporate | Protocol | Authentication | Polling | Status |
|---|
Live Channel Activity
Waiting for activity…
Filesystem Test Adapter — CORP-ABC
Visible only when explicitly enabled for isolated testing; it is not an SFTP or CIB connection.
🔐 PGP Key Custody
Where the private keys used for corporate PGP encryption/signing actually live, and how they're protected.
RMA Whitelist — SWIFT FileAct
FileAct will not deliver a file between two BICs without an established RMA (Relationship Management Application) authorization. Configured here for the demo the same way the RFP asked payment codes to be configurable — no code change to add or revoke a relationship.
| Sender BIC | Receiver BIC | Status | Note |
|---|
SWIFT FileAct Test Adapter — SCORE:MUSCORPXXX
Isolated simulation of a FileAct store-and-forward exchange — envelope structure modeled on SWIFT FIN message blocks, RMA-checked before any payload is parsed. Not a connection to Swift Alliance Gateway.
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. 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 |
|---|
Managed Banking APIs
Persistent endpoint catalogue with activation control, versioning, OpenAPI documentation and execution evidence. Tests call the same live handlers used by external consumers.
Authentication not configured
OpenAPI JSON
Endpoint Catalogue
Disabling an endpoint is enforced immediately and recorded as a versioned configuration change.
| API / version | Method & path | Authentication | Timeout | Rate / minute | Executions | Status | Actions |
|---|
Live Test Console
Runs a real request through the selected managed endpoint. Payment tests use the packaged XSD-valid pain.001 sample.
Select "Test" on an active endpoint.
Execution History
Status, duration, caller source and processing correlation evidence.
| Time | API | Source | Status | Duration | Outcome / correlation |
|---|
Executable Validation Rules
Create a draft, test it against a real file, then activate it. Active rules run in the same canonical validation engine for portal and API submissions; every failure records the rule ID and version.
Persistent · Versioned · Auditable
Create Rule
No code or deployment required. New rules start in DRAFT.
Rule Catalogue
Activation and deactivation create a new version; prior versions remain in history.
| Rule / version | Scope | Logic | Severity | Status | Actions |
|---|
Version History
Every edit, activation, deactivation and deletion — who changed it, when, and what it looked like before. Nothing is silently overwritten.
| Rule | Version | Change | Logic at that version | Changed by | When |
|---|
Payment File Type Codes
Bank-specific code table — new payment purposes onboard via configuration, no code changes.
| Payment type | Code | Description | CCY |
|---|
Format Detection Profiles
Content-based detection — extensions are indicative only.
| Profile | Delimiter | Detection | Status |
|---|
Splitting Rules
| Rule | Value | Configurable |
|---|
XML Tag Mapping — ISO 20022 pain.001
Dynamic mapping: each canonical field lists the tag paths it is read from. Built-in paths cover the standard branches (instructed & equivalent amount, IBAN & Other-ID accounts); custom aliases onboard a corporate's dialect at runtime — no code change.
| Canonical field | Built-in tag paths | Custom aliases |
|---|
Output File Naming Rules
Rule-based naming per channel / format / file type — configurable without code changes.
| File type | Pattern | Example |
|---|