Versions supported: 14.5, 14.7.
Configuration properties
gc-obpm-batch-payment-connector
Set these properties inbatch-payment-v0.values.yaml. This connector initiates batch payments and writes batch metadata and payment chunks to Azure Blob Storage. It doesn’t require the OBPM or Flexcube common properties.
The connector authenticates to Azure Blob Storage using a managed identity, not a SOPS secret.
gc-obpm-batch-payment-inbound-connector
Set these properties inbatch-payment-inbound-v0.values.yaml. This connector polls an Azure Blob Storage container for batch and payment status update files, and publishes events to the Sync Hub ASB producer. It doesn’t require the OBPM or Flexcube common properties.
The connector authenticates to Azure Blob Storage using a managed identity, not a SOPS secret. It publishes one batch-level status update event and one or more payment-level status update events for each processed blob, then deletes the blob. If processing fails, the connector moves the blob to an error folder instead of deleting it.
Supported operations
The OBPM Batch Connector exposes the Grand Central Unified API. For the operation-to-endpoint tables, see Overview. For the full contract, see the unified API specifications.Events
The batch payment inbound connector publishes the following events to the Sync Hub ASB producer.
The batch payment inbound connector polls the following source.
The batch payment connector doesn’t publish or consume events. It writes batch payment files to Azure Blob Storage for OBPM to pick up, and OBPM separately writes the status files that the batch payment inbound connector polls.
Error mapping
The connector maps OBPM error codes to Grand Central status codes. For the full list, see Error codes. No connector-specific overrides exist for these connectors.Dependencies
- Azure Blob Storage, for batch payment file exchange with OBPM.
- Sync Hub ASB producer, which receives the published batch status and payment status events.
obpm-connector-sdk(shared HTTP and blob configuration).