NEXT COHORT · 10 OCTOBER 2026Cohort underway · Contact us for availability ↗
All payment stories

pacs.028: A Missing pacs.002 Does Not Mean Payment Failure

Lumina Academy

A missing pacs.002 does not prove an SCT Inst payment failed; I explain why a BA must separate timeout, account restoration and final status.

Payment Series — Episode 17

A junior once asked me: “Cross-border payments have the Swift gpi Tracker. What do we have for SCT Inst when pacs.002 never arrives?” It is a practical question, because a missing response can look like a failed payment even when the beneficiary has already received the money. As a payment BA, I want to understand what actually happened before treating silence as a final outcome.

The €5,000 payment with two different views

Consider a €5,000 instant payment. The Payment Engine shows “Processed”, the beneficiary’s Core Banking shows the account credited, but the debtor bank has not received pacs.002. Ten seconds pass. In the SCT Inst scenario described in this episode, the originator bank restores the customer’s account.

The customer now has €5,000 back. The beneficiary may also have €5,000. That is the point where I stop and challenge the statement “the payment failed”. Restoring the customer’s account protects the customer; it does not, by itself, prove that the beneficiary was never credited.

I would put the evidence side by side:

• Payment Engine: processed.

• Beneficiary Core Banking: account credited.

• Debtor bank: pacs.002 not received.

• Customer account: restored after the timeout.

These are different observations, not interchangeable descriptions of the same final result. If the requirement reduces them to one failure flag, it loses the very distinction that the investigation needs.

What pacs.028 helps us establish

pacs.028 is a Payment Status Request. In this example, it is used to investigate the original transaction and retrieve the missing outcome. The question is not whether a response arrived on time. We already know it did not. The question is what happened to the payment that the missing response should have described.

Without that investigation, an unresolved payment can be treated as a confirmed failure. I would not write a requirement that makes that jump. A timeout tells us something about the response we were waiting for; it does not automatically tell us what the beneficiary bank completed.

This is also why the familiar UPI experience is useful as a way of thinking about the problem: an account is debited, the outcome is unclear, and investigation is needed before resolution. I am comparing the uncertainty, not saying that UPI and SCT Inst use the same messages or rules.

Separate the three decisions

For me, the decision logic starts by separating three things that are often bundled together:

1. Processing timeout: did the expected confirmation arrive within the relevant time?

2. Customer-account restoration: what happened to the originator’s account after that timeout?

3. Final interbank payment status: what was the actual payment outcome?

In the worked example, the timeout and restoration are known. The missing confirmation still needs investigation. I would therefore keep the outcome unresolved until the relevant evidence establishes what happened, rather than label the payment failed simply because the customer has been restored.

The beneficiary bank’s response matters just as much. When pacs.028 arrives, the bank needs to report the actual outcome, not merely repeat one system’s last status. That requires a reliable view across the Payment Engine, Compliance and Core Banking. “Processed” in one component is not a substitute for understanding the end result across the systems involved.

So, What Makes the Difference?

A good BA looks beyond the response timer and asks what evidence supports the next decision. I would focus on these questions:

• What does each displayed status actually mean?

• Are timeout and final failure kept separate?

• Can we establish whether the beneficiary account was credited?

• Does account restoration leave an unresolved interbank outcome to investigate?

• Can the response reflect the actual outcome across the relevant systems?

The test is not speed alone. It is whether we can accurately establish what happened when the expected confirmation is missing. That is where a seemingly small status requirement becomes a much more important payment-control discussion.

Key Takeaways

• NO RESPONSE IS NOT FAILURE: Missing pacs.002 does not prove the payment failed.

• RESTORATION IS A SEPARATE ACTION: Returning the customer’s balance does not establish the beneficiary’s position.

• INVESTIGATE THE ORIGINAL PAYMENT: pacs.028 helps retrieve the missing outcome.

• FOLLOW THE EVIDENCE: Reliable status needs the relevant systems, not one isolated label.

At Lumina Academy, I use scenarios like this to connect message knowledge with practical BA questions. For a focused conversation about your payments learning, book a session at https://topmate.io/jebaraj_d.

Changed: Converted Episode 17 into a structured blog, retaining the €5,000 example and separating timeout, restoration and payment status.

More stories

PAYMENTS WATCH

Stay curious.
Stay ahead.

Connect your learning to what’s happening in payments.

INDUSTRY INSIGHTS · 1 / 3Explore Sibos: the conversations shaping the future of paymentsExplore the update ↗