As we covered in a dedicated article, safeguarding requirements for payment institutions (PIs) and electronic money institutions (EMIs) is crucial to ensure the safety and security of customer funds. It is, however, hard to achieve operationally with the expected rigour, and up to one-fourth of PI and EMIs in the UK and Ireland fell short of their obligations in 2023, according to the regulators. The main issues highlighted were then:

Working backwards from those challenges, we cover in this article how a bank orchestration platform like Mambu Payments supports the critical challenges faced by payment teams accountable for fund safeguarding, making safeguarding orchestration scale and reliable.

We will explore those workflows from the perspective of regulated EMIs participating in SEPA in a country where safeguarding is conducted through segregation over insurance (leading to having two distinct accounts: one for safeguarding, one for payment and settlements).

When setting up their safeguarding operations, payment operators have to ensure that the money movements related to their operations are segregated from customer funds. In practice, this means opening additional accounts for transactions associated with business running costs and non-customer funds to book incoming payments.

One of the reasons for failing to follow this account de-mingling strategy is complexity. Managing multiple accounts can quickly create headaches for finance and treasury teams, ensuring that all accounts are provisioned appropriately at all times. Mambu Payments’ bank orchestration platform solves this challenge by connecting to all bank accounts and combining them into a central view of all accounts that finance teams can access.

All connected accounts to Mambu Payments can be queried through a single API request or accessed through the Mambu Payments dashboard.

GET https://api.numeral.io/v1/connected_accounts

Once all bank accounts are connected to the platform, customers can leverage the API to build adequate payment workflows to ensure only customer funds are deposited on the safeguarding account while all other funds are sent to operational accounts.

Payment accounts are provisioned daily to ensure enough funds are available to fund the net settled position of the PI/EMI at the end of the day. If the account is underfunded and its balance becomes negative, there is a high chance that the sponsor bank will remove access to the CSM and discontinue day-to-day operations, which can have a dire impact on the company.

On the other hand, an overfunded account increases operational risk by making more customer funds ‘accessible’ in the payment account.

Therefore, the daily provisioning relies on estimated balances between incoming and outgoing payment orders expected to arrive and then adds a margin of error based on the PI or EMI’s risk profile to avoid underfunding.

Let’s explore how Mambu Payments helps teams get a solid base for this forecasting exercise.

For payments initiated by the PI or EMI, the non-reconciled operations expected to impact the account in the upcoming day can be accessed through a single API call using the filter &reconciliation_status=unreconciled. Those payment orders are expected to impact the subsequent settlement and serve as a basis for the safeguarding forecast.

GET https://api.numeral.io/v1/payment_orders?reconciliation_status=unreconciled

For payments not initiated by the PI or EMI, SEPA indirect participants receive instantaneous pacs files and API calls to notify them of upcoming payments to be settled. In Mambu Payments, those payment notifications are called incoming payments, and expected incoming payments across all schemes can be accessed through a single API query in Mambu Payments.

GET https://api.numeral.io/v1/incoming_payments?reconciliation_status=unreconciled

Adding those incoming payments to be settled in the daily forecast on top of the initiated payments to be settled serves as a robust baseline for the forecasting.

Since the introduction of instant payments (FPS and SEPA Instant Credit Transfer), conducting a forecast of safeguarded funds once a day is no longer a viable option. Instant transfers in and out with instant settlement on the accounts can create balance variance, which has to be mitigated in real-time.

For this purpose, Mambu Payments shares real-time updates through a webhook of balances to enable the payment teams to take corrective actions immediately through instant intra-day transfers.

Based on customer instant payment orders and the business internal logic, instant transfers can be initiated through Mambu Payments from the safeguarding account to the settlement account to ensure adequate funds are available.

GET https://api.numeral.io/v1/payment_orders

A PI or EMI’s core banking system (CBS) is the single source of truth for customer balances. To remain accurate and compliant with regulations, CBSs need real-time access to payment execution and reconciliation statuses. With multiple incoming and outgoing money flows, keeping track in real-time of those data points for all customers can be daunting.

Mambu Payments’ orchestration layer provides the foundation for scalable processes by bringing together three components:

Combining those three capabilities, Mambu Payments can automatically reconcile booked transactions, allocate them to customer accounts and share the structured information back with the PI or EMI’s CBS to update the central ledger. All the while keeping an auditable trail of all events and changes to support compliance operations.

Mambu Payments supports regulated financial institutions in building pan-European bank operations that can scale. If improving safeguarding operations is a key topic for your company, do not hesitate to contact us.