Why Do Transactions Get Stuck in “Processing”?

When a transaction remains in the “Processing” status, it means the payment flow was initiated by the customer but never completed or authorized.

This typically occurs when the customer did not proceed to their banking app or online banking interface to approve the payment after starting the process on your platform.

🔍 Common Reasons for Processing Status

1. User Abandonment
   The customer may have changed their mind mid-flow - whether due to trust concerns, hesitation, or simply deciding not to complete the purchase.

2. Flow Interruptions
   Network issues, device limitations, session timeouts, or failed redirects can prevent the customer from reaching the bank interface to authorize the payment.

3. Technical Failures
   Occasionally, errors within the banking ecosystem or during the redirection steps can break the flow. Ivy detects these and classifies them under specific failure reasons.

✅ How to Investigate Further

You can retrieve detailed failure reasons via webhooks provided by Ivy. These will help you classify the cause - whether it was user-driven, bank-side, or a technical issue.

🔗 See Ivy's full list of failure reasons →

Summary

A stuck “Processing” status doesn’t mean anything went wrong on Ivy’s end - it usually indicates that the customer didn’t take the final step to authorize the transaction. Ivy will not attempt to debit the account unless the user explicitly approves the payment in their bank.