Notifications and subcriptions
Cobre’s Notifications & Subscriptions capability allows organizations to receive real-time updates about key platform events through a centralized webhook-based mechanism. Instead of relying on periodic polling or manual monitoring, clients can build operations that respond immediately to changes in balances, payment status, counterparties, reports, evidence flows, and more.
This matters because it improves operational speed, reconciliation accuracy, and customer experience—especially at scale and across multiple payment rails and markets.
1. What Cobre Enables with Notifications & Subscriptions#
With Notifications & Subscriptions, Cobre enables clients to:Subscribe to platform events across multiple products and services (Accounts, Money Movements, Cross-Border, Bulk, Reports, Evidence, Keys, Counterparties, etc.)
Receive real-time webhook notifications whenever selected events occur
Build event-driven automations for reconciliation, risk alerts, customer notifications, and operational workflows
Standardize event consumption using a consistent event schema across all subscribed features
Improve security by enabling signed notifications that help verify authenticity and integrity
Increase delivery reliability with a retry scheme for transient delivery failures
Scale integrations more predictably by shifting from “check status” to “react to events”
2. Notifications & Subscriptions in the Cobre Model#
Notifications & Subscriptions is a cross-feature layer that connects Cobre’s operational objects with client systems:Cobre Balances generate events when balances are credited or debited, enabling real-time liquidity monitoring and reconciliation triggers.
Money Movements and related flows (including Bulk and Cross-Border) generate events that reflect lifecycle and operational state changes—helping clients react to payment completion, rejection, or internal status transitions.
Transactions can be reflected through event payloads and used to sync financial ledgers or power reporting pipelines.
Reports and Evidence Requests can emit events that allow teams to automate compliance and reconciliation processes.
3. Key Capabilities / Options#
3.1 Centralized Event Subscription Across Products#
Cobre provides one unified mechanism to subscribe to events across platform domains, including:Cross-Border Money Movements
3.2 Webhook Notifications with a Standard Event Schema#
All notifications follow a consistent event format, typically including:An event key (what happened)
An event-specific content payload
3.3 Signed Notifications for Integrity and Authenticity#
For clients that require higher security controls, Cobre supports signed notifications, allowing webhook receivers to verify that:The notification is genuine
The payload was not altered in transit
3.4 Reliability Through Automatic Retries#
Cobre applies a retry scheme for delivery failures caused by connection issues.
Retries are designed to improve resilience while avoiding unnecessary duplication in cases where clients intentionally reject requests (e.g., 4xx responses).
3.5 Event-Driven Automation at Scale#
Notifications can be used to trigger workflows such as:internal payment state updates
downstream actions tied to money movement results
4. Core Concepts and Terminology#
Subscription: A configuration that defines which event types a client wants to receive and where they should be delivered.
Event: A structured notification representing something that occurred in the Cobre platform (e.g., balance credited, payment updated).
Event Key: The identifier representing the type of event (used to classify notifications).
Webhook: The delivery mechanism used to send notifications to the client’s system in real time.
Signed Notification: A notification that includes cryptographic verification signals so the receiver can validate authenticity and integrity.
Retry Scheme: Automatic redelivery attempts for eligible failures (e.g., connection errors).
5. Speed, Settlement & Reliability (if applicable)#
Notifications are designed for near real-time operational awareness, meaning events are delivered as they occur rather than being available only through scheduled exports or periodic checks.Reliability is supported by:Automatic retries for connection errors, improving delivery success when systems experience transient downtime.
Optional signed notifications, which improve trust and auditability by allowing clients to validate the notification.
For example, an “account credited” event reflects a posted balance change, while a “money movement status” event reflects a process state.
6. Typical Business Use Cases#
Common use cases include:Real-time reconciliation triggers when balances change
Payment status automation for customer support or merchant operations
Fraud and risk monitoring based on transaction or counterparty-related events
Internal ledger synchronization using event payloads as the source of truth
Operational alerting (e.g., failed movements, evidence status changes)
Workflow orchestration for bulk or cross-border payment programs
7. Transactions, Reporting & Reconciliation#
Notifications & Subscriptions improves reconciliation by making Cobre events available as they happen, enabling:Immediate sync of transaction impacts into internal ledgers
Automated capture of balance changes for treasury and finance teams
Faster exception handling when movements fail, reject, or require operational attention
8. Governance, Controls & Auditability#
Notifications & Subscriptions supports governance through:Traceability: every notification includes an event identifier and timestamp, enabling audit trails.
Integrity controls: signed notifications allow clients to verify authenticity and detect tampering.
Operational resilience: retry behavior reduces the risk of missing critical events during brief outages.
9. Notifications & Subscriptions vs Polling / Periodic Status Checks#
| Dimension | Notifications & Subscriptions | Polling / Periodic Checks |
|---|
| Update timing | Real-time push | Delayed, depends on frequency |
| Operational workload | Lower (event-driven) | Higher (constant queries) |
| Reliability approach | Retries for eligible failures | Client must manage retries and gaps |
| Security options | Signed notifications available | Typically none |
| Best for | High volume, automation, reconciliation | Small volume, simple workflows |
Notifications & Subscriptions is usually preferred when clients need real-time operations, scalable reconciliation, and lower integration overhead.
10. Summary — What Cobre Delivers with Notifications & Subscriptions#
Cobre enables clients to: Subscribe to platform events across key product lines
Receive real-time webhook notifications with a standardized schema
Build automation workflows for reconciliation, monitoring, and payment operations
Improve security with signed notification integrity validation
Increase delivery resilience through a defined retry schemeBy turning Cobre into an event-driven platform, Notifications & Subscriptions helps businesses operate payments at scale with stronger visibility, faster reactions, and better financial control. Modified at 2026-01-08 23:45:06
