PEXA incident

CBA Service Issue - Payment File Response

Minor Resolved View vendor source →

PEXA experienced a minor incident on June 23, 2026 affecting Financial Settlement Services, lasting 2h 27m. The incident has been resolved; the full update timeline is below.

Started
Jun 23, 2026, 03:34 AM UTC
Resolved
Jun 23, 2026, 06:01 AM UTC
Duration
2h 27m
Detected by Pingoru
Jun 23, 2026, 03:34 AM UTC

Affected components

Financial Settlement Services

Update timeline

  1. investigating Jun 23, 2026, 03:34 AM UTC

    We’re aware of a payment file response issue currently impacting CBA and their transactions. If your workspace is affected and has commenced settling, it may remain in a status of 'Ready and Settling' or 'Completed and Disbursing' for longer than usual while we work to resolve the issue. We’re actively working with CBA to resolve this issue. We apologise for the inconvenience this has caused you and your customers. Please be advised this is not a PEXA issue. We appreciate your patience and will provide you with an update within the hour.

  2. monitoring Jun 23, 2026, 04:16 AM UTC

    We can confirm the payment file response issue impacting CBA and their transactions is now resolved. Impacted workspaces that have commenced settling will now proceed as expected. Please note this is not a PEXA issue We’re keeping a close eye on this and we apologise again for the disruption this has caused you and your customers.

  3. monitoring Jun 23, 2026, 05:12 AM UTC

    We can confirm the payment file response issue impacting CBA and their transactions is now resolved. Impacted workspaces that have commenced settling will now proceed as expected. Please note this is not a PEXA issue We’re keeping a close eye on this and we apologise again for the disruption this has caused you and your customers.

  4. resolved Jun 23, 2026, 06:01 AM UTC

    CBA has resolved the payment file response issue. Please note, this was not an issue on PEXA's side. Impacted workspaces that had commenced settling will now proceed as scheduled. We’re sorry for the inconvenience this has caused you and your customers.