Operations & payments
Payments, standing orders & settlement
Outbound payments with funds held in suspense until the rail confirms clearing.
What it covers
- RailsInternal book transfers, mobile-money payments and bank payments behind a pluggable rail adapter.
- Suspense holdsInitiation debits the customer and holds funds in the payments suspense account until the rail responds.
- CallbacksSigned rail callbacks settle or fail a payment; internal transfers settle synchronously.
- LimitsPer-segment and per-rail caps on a single payment and on a customer's daily outbound total.
- Standing ordersDaily, weekly or monthly recurring payments with pause, resume, cancel and due-run idempotency.
- Returns and recallsAccepted returns and recalls refund the customer; rejected recalls restore the payment.
How it works
- Initiate
Create the instruction, check limits and debit the customer into suspense.
- Wait for the rail
The rail settles or fails the payment through a signed callback.
- Handle exceptions
Process returns and recalls without creating duplicate financial effects.
- Settle and reconcile
Capture the rail's advice and post any settlement difference to the difference account.
Controls built in
- Payment initiation is idempotent by key.
- Callbacks are idempotent by rail reference and signed with HMAC-SHA256.
- Sanctions screening runs before funds move for external beneficiaries.
- Settlement batches reconcile against the rail and report differences.
Related modules
Talk through this module.
Book a walkthrough and we will map this module to your products, approval rules and reporting needs.