JPMorgan 4 min read

Your Bank App Works. So Why Is Your Transfer Stuck?

Key takeaways

  • Transfers between banks can involve several institutions and processing stages.
  • An outage at an intermediary can delay customers whose own banks are working.
  • Simultaneous delays at several banks do not establish a shared cause.
  • Recovery includes resolving pending transfers and preventing duplicate or missed transactions.

You can log in, check your balance, and still find that money sent to another bank hasn’t arrived. The app is the front door; completing the transfer may depend on several systems behind it. That distinction matters when assessing whether an outage at a bank such as JPMorgan could leave other banks’ customers waiting.

Follow the transfer’s route

Moving money between two accounts at the same bank can follow a different path from sending it to another bank. An interbank transfer can involve the sending bank, the receiving bank, and systems that carry payment instructions and settle obligations between them.

Settlement is the process through which banks fulfill what they owe each other for those transactions. The mechanics vary by payment service and network.

Some transfers also involve an intermediary bank. You interact with your own bank’s app, but completing the transaction requires another institution to do its part.

That does not mean every interbank transfer passes through JPMorgan. Its name and size alone tell you little about whether a particular outage could affect your payment. What matters is the actual transaction route and which services along it are available.

How a delay crosses bank boundaries

Imagine a transfer from Bank A to Bank B, with Bank C handling an intermediate step.

If Bank C stops processing those transactions, Bank A might still accept your request but be unable to complete the next stage. Bank B could be waiting for the information or funds it needs before the money reaches your account.

Both banks’ apps could look perfectly healthy. Your payment would still be stuck.

The same logic applies to JPMorgan. If it handles an intermediate step for a particular transfer, a failure in that service could affect customers at other banks. The scope would depend on which function failed and which transactions relied on it.

This is why claims that an outage has “spread” need some unpacking. A downstream bank might have a broken system of its own. Or it might be working normally while waiting for another institution to finish processing a transaction. Those are different problems with different recovery paths.

The same timing does not prove the same cause

Reports of trouble at several banks can look like one big incident. Timing alone cannot establish that connection.

A shared payment network or external provider might be experiencing problems. The banks could also be dealing with separate failures. Attributing the delays to one institution requires evidence of the dependency.

Even the phrase “online banking is down” hides several distinct symptoms:

  • Customers cannot log in.
  • Balance information fails to load.
  • Transfer requests are rejected.
  • Accepted transfers have not arrived.

Each points to a different part of the service. A login problem tells you something different from a payment awaiting settlement.

To assess a claim that JPMorgan caused delays elsewhere, you need to know which function failed and which types of transactions were affected. Explanations from the banks or payment network operators should support that connection.

“Service restored” still leaves work to do

Shared networks and intermediary services reduce the need for every bank to build a separate processing arrangement with every other bank. Those connections help make transfers possible across institutions.

They also create dependencies that matter during recovery. An alternative route may offer little protection if it relies on the same failed system. Even an independent route must have enough capacity to absorb the extra traffic.

Restoring access is only one step. Pending transactions still need processing. If a response disappeared midway through a transfer, the institutions involved need to establish whether the transaction actually completed before attempting it again. Otherwise, they risk duplicate processing or leaving a payment unresolved.

Customers need updates that reflect those distinctions. Can they submit new transfers? Are pending payments moving? Where can they check whether a specific transaction has completed? A generic “back to normal” banner answers none of those questions.

A polished app is easy to judge; the connections behind a transfer are harder to see. The more revealing test comes during an outage: can the institutions involved finish the transaction, and can your bank tell you clearly where your money stands?

JPMorgan Financial Infrastructure Online Banking

Comments

    Loading comments...