- OBPM payment outbound Connector: Payment initiation and lifecycle management, payee contact synchronization (create and update), including domestic and international payee routing, fee retrieval, bank details lookup, and other outbound features. Doesn’t handle payment status updates.
- OBPM payment inbound Connector: Status updates, recurring payment schedules, future-dated payment ingestion, and off-channel payment ingestion (FPS and internal payments) from the payments core using dedicated JMS queues.
- OBPM direct debit Connector: Mandate search, retrieval, and cancellation.
- Flexcube foreign exchange Connector: Currency exchange rate retrieval.
Use cases supported
Payment initiation
Initiate single or recurring payments across supported payment schemes.
Payment management
Manage payment lifecycle including modifications and cancellations.
Payee synchronization
Synchronize beneficiary and payee information with OBPM, including create and update operations for domestic and international payees.
Future-dated payment ingestion
Receive future-dated payments initiated in the payments core and surface them to channel apps through Sync Hub.
Direct debit management
Search, retrieve, and cancel direct debit mandates.
Payment ingestion
Receive recurring payment schedules and off-channel payments from the payments core.
Ancillary features
Retrieve bank details, payment fees, exchange rates, and holiday calendars.
Supported Grand Central endpoints
The OBPM Connector supports the following operations from the Grand Central Unified API v1:
The OBPM Connector supports the following operations from the Grand Central Unified API v2:
For Unified API v2,
fetchFees returns fee amount and currency in the customer’s debit-account currency. That amount is what the bank actually debits, not the OBPM internal pricing currency.
To receive status updates on initiated payments, recurring payment schedules, future-dated payments, and off-channel payments from the payments core, the OBPM payment inbound Connector listens to dedicated JMS queues. For more information, see Get started. The payee contact sync feature validates the incoming JSON payload against the unified spec schema, routes domestic and international payees based on
obpm.contact.sync.domesticCountryCode, and performs XSLT transformation to convert the request into the XML format expected by OBPM.For more information about the Grand Central Unified API endpoints that support these features, see Unified APIs. For a complete list of Grand Central error codes and vendor mappings, see Error codes.