Meet us at conferences around the world
SiGMA South America
iGB L!VE London
SBC Summit Lisbon
SiGMA Europe
B2B platforms needed to update balances quickly, but early payment statuses did not always mean final settlement. This created reconciliation complexity, settlement uncertainty, and exposure when funds left the payer but had not yet reached the merchant.
In B2B platforms, a single settlement misstep can disrupt operations. Unlike card-based processing, Open Banking separates funds leaving the payer (debtor) from those reaching the merchant (creditor) into distinct stages.
Updating balances too soon after payer-side settlement can create exposure before merchant-side confirmation. If funds aren't received promptly, workflows stall and orders are delayed.
With these pressures in mind, our clients were looking for a solution that could:
Support timely balance updates without treating early payment status as final settlement.
Use internal operational stages aligned with Open Banking payment statuses for payer-side and payee-side settlement.
Reduce administrative overhead in reconciliation and exception handling.
Maintain a smooth customer experience while minimising risk.
Card-based authorisation and capture don't directly map to Open Banking, so here they serve only as internal labels. This created several operational challenges:
Names implying sure-shot fund guarantees risked acting before actual settlement.
Banks report varying levels of detail: some only show initiator ACWC/RJCT/ACSP/ACCC, others show payer UKWN or payee NACQ settlement.
Platforms manually tracked exceptions and pending payments, which increased operational costs and errors.
Delays confirming funds created frustration for end users and eroded merchant confidence in the platform.
If the client released a payment after approval — but the bank funds bounce, the merchant and issuing payer bear the financial risk.
Payneteasy introduced a status-driven Open Banking payment flow built for B2B platforms.
For internal operational, monitoring, and reconciliation purposes, transaction stages are aligned with ISO 20022 payment statuses.
Monitor
Provisional Update
Flag
Confirm
Payer-side settlement status signals that funds have left the payer's account, which allows the platform to update internal records for monitoring. Payee-side settlement status indicates funds have reached the beneficiary, which marks the point for final settlement confirmation and reconciliation.
With this mapping in place, internal teams gain clearer visibility into transaction progression and can make operational decisions based on actual settlement status.
Platforms gain visibility from pre-auth to final settlement, with status changes monitored for confirmations and exceptions.
The monitoring logic can be applied across different payment rails, including Faster Payments, SEPA, and cross-border transfers, while accounting for differences in settlement timing and status reporting. This helps operational teams identify unresolved transactions earlier and reduce manual follow-up. Combined with Payneteasy's payout platform, it provides end-to-end visibility across the entire payment reconciliation cycle.
Payment status overview in USD
Total balance
$58,421.12
Available to pay out
$22,278.12
Available soon
$17,327.00
In transit to bank
$18,816.00
Recent events
We enabled provisional balance updates once payer-side settlement was detected, while keeping final settlement and reconciliation tied to later confirmation.
Transactions that didn't reach payer-side settlement were automatically flagged, which reduced manual reconciliation and follow-up. Status events were also integrated with merchant workflows to update order fulfilment. Automated updates cut delays and eased operational friction across the payment lifecycle.
Want to reduce settlement exposure on your platform?
See how Payneteasy's status-driven approach maps to your payment flows.
Book a technical walkthroughTo reduce financial risk, the system enforces limits on in-flight transactions (those that are pre-authorised but not yet captured). Users face both count and amount restrictions.
Exposure limits
Updated 2 min ago
Max in-flight transactions
50
Current limit
Max exposure amount
$100,000
Current limit
For instance, a user may only have two pre-authorised transactions in progress. Any attempt to start a third is held until one of the previous transactions is captured.
Similarly, a maximum value can be set, such as $5,000, and any new transaction above that limit waits until earlier pre-auths are completed. All transactions are tracked per payer using identifiers, such as card holder and email, which gives platforms clear oversight of pending activity.
The system separates initiation, payer-side settlement, and payee-side settlement to show which payments are in progress, unresolved, or fully settled. If a transaction remains payer-settled but not merchant-settled for several days, this indicates unresolved settlement exposure that requires review.
By combining limits with status-based monitoring, the platform keeps in-flight exposure low without disrupting daily operations.
Key outcomes of the new approach:
Enforcing count and amount limits on in-flight transactions reduced the risk of over-committing unsettled balances.
Real-time status tracking across payer-side and payee-side settlement stages gave teams a clear view of which payments are in-flight, unresolved, or fully settled.
Automated events and exception handling allowed platforms to prioritise pending deposit, approval, or voided transaction agents.
Early balance updates reflected progress where appropriate, while limits on in-flight transactions prevented users from over-committing funds.
The status-driven approach works across Faster Payments, SEPA, and cross-border payout rails, adapting to local settlement timing and reporting differences.
Payneteasy's status-driven Open Banking flow provided a structured, risk-aware framework with ISO 20022 statuses, real-time monitoring, and pre-auth controls. Clear pre-auth/capture separation and enforced limits boosted security and efficiency. The key point is to treat payer- and merchant-side settlement as separate stages with controls between them.
How automated dispute resolution with Ethoca and Verifi alerts cut chargebacks by 87% and preserved the merchant's MID.
Send mass payouts worldwide via API — OCT cards, bank transfers, wallets. Multi-currency, white label, instant cross-border disbursements.
Let our team map your Open Banking payment flows and show where status-driven controls reduce exposure.
Thank you for reaching us. Your request has been sent successfully. We will get back to you as soon as possible.
Message was not sent
