ISO 20022 ingress
Accept supported payment, status, return, recall, administration, and health message families through defined endpoints.
Express-O 17 · Planned payment connection
Scheduled launch · Early 2027
The planned InstaPay Gateway will connect Express-O 17 to Philippine payment workflows. Part of the flagship offering scheduled for early 2027, its live rollout will be scoped around your institution’s network onboarding and core integration.
ISO 20022 payment orchestration
Express-O 17 will include an InstaPay Gateway alongside its Mobile App and other channel connections. The gateway is designed to separate payment-network handling from core banking operations, with traceable processing and exception management. Network onboarding, security, core adapters, and acceptance testing will be agreed before live use.
A production rollout depends on the bank’s network onboarding, applicable certification, core integration, security setup, and end-to-end acceptance testing. A product demonstration does not establish live network approval.
Review your requirements with us →The payment message journey
A dedicated integration layer separates InstaPay message handling from core banking operations.
Accept supported payment and status message families.
Check message structure, signatures, and duplicates.
Coordinate the network message and core banking adapter.
Follow status, exceptions, queues, and audit events.
InstaPay is a Philippine payment integration. Live rollout requires applicable network onboarding, certification, and bank acceptance testing.
Planned module capabilities
Purpose-built services isolate transport, security, message handling, core integration, and operations so each concern can be controlled and observed.
Accept supported payment, status, return, recall, administration, and health message families through defined endpoints.
Apply business-header checks, XML signature verification, schema validation, replay protection, and duplicate detection.
Route pacs.008, pacs.002, pacs.004, camt.056, and administrative messages to focused processors.
Return immediate protocol responses where required and use durable workers for deferred processing paths.
Keep payment-network protocol behavior in the gateway while core adapters own posting, reversal, recall, and inquiry integration.
Track queue state, retries, dead letters, audit events, admin session state, health, and processing metrics.
Modular architecture
The gateway creates an explicit boundary between payment-network protocol handling and core banking services.
Inbound and outbound ISO 20022 exchanges
Transport handling, business-header extraction, payload persistence, and acceptance
Signature, schema, replay, duplicate protection, parsing, and dispatch
Payment, status, reversal, recall, and administration processors
Core banking adapter, durable queues, event outbox, audit, metrics, and health
Operational safeguards
Raw inbound messages, processing state, outbound work, and events are persisted to support traceability and recovery.
Message hashes, business identifiers, replay records, and transaction state reduce duplicate processing risk.
Administrative session state, health endpoints, metrics, audit logs, retry state, and dead-letter visibility support live operations.
Part of Express-O 17
Connect real-time payment services through a dedicated integration layer while Express-O 17 remains the system of record for banking operations.
Explore the core banking platform →Let’s plan your next step
Share your current environment, reporting or payment scope, and operational priorities with our banking technology team.
Discuss your requirements