Payments Message Processing
The Prowide Messaging Hub is a message handling platform -- it manages the full lifecycle of payment messages between your back-office systems and the SWIFT network or regional clearings.
This means the Hub excels at everything that happens to a payment message: initiation with intelligent forms, operator verification with re-keying of critical data, multi-level authorization, format translation between MT and MX, compliance validation, content-based routing, and delivery monitoring with ACK reconciliation.
The Hub is deliberately generic and flexible -- it handles any SWIFT message type, not just payments. This means you get a single platform for payments, treasury, securities, and trade finance messages, with workflows that you configure per message type, per value threshold, or per business unit.
For payment-specific business logic -- such as automatic return generation, fee calculation, or nostro/vostro accounting -- the Hub integrates with your specialized back-office systems through its flexible connector framework, keeping each system focused on what it does best.
What the Hub handles
Message initiation, operator verification, authorization workflows, MT↔MX translation, compliance validation, content-based routing, delivery monitoring, ACK reconciliation, back-office integration, and a full audit trail for every payment instruction.
The Messaging Hub covers the complete payment message lifecycle -- from the moment an instruction is created or received, through verification, authorization, translation, validation, and delivery.
For outbound payments, the Hub gathers instructions from operators or back-office systems. It enforces verification (where the operator re-keys value date and amount), then authorization workflows before translating to the required format, validating for compliance, and delivering to SWIFT or clearing systems.
For inbound payments, it receives from the network, translates if needed, reconciles acknowledgments, and routes to the appropriate internal destination -- all with full audit trail and operational visibility.
Every step is configurable per message type and value. High-value payments can require additional authorization levels. Low-value payments can flow through with minimal intervention.
Capture
Payment instruction via intelligent forms, back-office import, or file ingestion
Verification
Operator re-keys critical fields (value date, amount) to confirm accuracy
Authorization
Supervisory approval -- configurable as 4-eyes or 6-eyes per value threshold
Translation
MT↔MX conversion when clearing requires a different format than the source
Validation
Full SWIFT compliance -- semantic rules, CBPR+ guidelines, BIC directory
Routing & Delivery
Content-based routing to SWIFT, clearings, or internal systems
Reconciliation
ACK monitoring, status tracking, and exception alerting
Intelligent Message Entry
Create payment instructions using dynamic forms with auto-complete BIC selection, field validation, and context-sensitive help. Save frequently-used payments as reusable templates. Import instructions from FIN, RJE, or MX files for bulk processing.
Operator Re-Keying
A second operator verifies the payment by re-entering critical fields -- typically the value date and main amount. The system compares the re-keyed data against the original instruction and flags any discrepancies. This prevents data-entry errors from reaching the network.
Supervisory Approval
Authorized users review and approve the payment before release. The authorization step is fully configurable -- you can require it for all payments, only for high-value transactions, or based on any message content criteria. Supports 4-eyes and 6-eyes principles.
Not all payments are equal. A low-value domestic transfer doesn't need the same controls as a high-value cross-border instruction. The Hub's configurable workflow engine lets you define different processing rules per message type, value threshold, currency, BIC, or any message content.
Each workflow step -- verification, authorization, translation, validation, routing -- can be included or skipped based on your business rules. You can add extra authorization levels for high-value payments while letting routine transfers flow through with minimal intervention.
Workflows are configured through the Hub's visual rule builder -- no custom code required. Rules can be tested with dry-run mode before activation, and changes take effect without system restarts.
High-value payment workflow
Capture → Verification (re-key) → Authorization (6-eyes, two approvers) → Translation → Validation → Route to SWIFT
Low-value domestic payment
Capture → Verification (re-key) → Validation → Route to clearing
Straight-through processing
Receive from back-office → Validation → Translation (if needed) → Route to SWIFT -- no manual intervention
Different clearings require different message formats. Your core banking system might produce MT messages, but CBPR+ requires MX. A domestic clearing might need its own MX flavor. The Hub's translation engine handles this automatically.
When a payment needs to reach a clearing that uses a different format than the source, the Hub translates on the fly -- using the appropriate clearing-specific translator (CBPR+, SIC, RITS, LYNX, T2, and more). Your back-office systems continue working in their native format while the Hub adapts to whatever the network requires.
This is particularly valuable during the ISO 20022 coexistence period, where some counterparties and clearings have migrated to MX while your internal systems may still rely on MT.
Core banking produces MT
Hub translates to MX for CBPR+ or regional clearings, applying the correct translation standard automatically
Different MX flavors per clearing
SIC, RITS, LYNX, T2 each have specific MX requirements -- the Hub applies clearing-specific rules on top of base ISO translation
Bidirectional for inbound too
Inbound MX payments from the network can be translated to MT for back-office systems that haven't migrated yet
Receive from core banking
Ingest payment instructions from your core banking or ERP system via hot folders, IBM MQ, RabbitMQ, or REST API. The Hub picks up files or messages automatically and feeds them into the configured workflow.
Distribute to back-office
Route inbound payments, confirmations, and status updates to the appropriate internal system. Content-based routing ensures each message reaches the right destination based on type, BIC, currency, or custom criteria.
Statement & report export
Extract statement data from incoming messages and export in formats your back-office systems can consume. Convert SWIFT statement messages into structured reports for reconciliation or accounting.
Custom integrations via REST & workflow
For systems that need real-time integration -- accounting, compliance screening, or sanctions checking -- the Hub supports custom workflow actions and outbound REST API calls to invoke external services at any point in the payment flow.
Hub strengths for payments
Everything related to the message lifecycle -- from initiation through delivery and reconciliation.
Handled by your back-office systems
Payment-specific business logic that belongs in your core banking or specialized payment systems.
The Hub integrates with these systems through its connector framework -- REST API, message queues, file exchange, or custom workflow actions -- so each system handles what it does best.
Messaging Hub
Full payment message handling with web-based operations, visual workflow configuration, and message initiation with verification and authorization.
Prowide Integrator
Embed payment message capabilities -- translation, validation, and format conversion -- directly into your existing payment processing application.