-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Description
Bug Description
Currently, when a refund request is initiated but no connector call is actually made (e.g., due to validation errors, missing data, or internal blocking conditions), the refund status is set to pending.
Impact
This creates a false impression for merchants. Since the dashboard/API shows the refund as pending, merchants assume the refund is already in progress with the connector/bank. In reality, no refund has been triggered externally.
As a result, merchants may:
- Expect funds to be returned to the customer soon, leading to unnecessary customer escalations.
- Re-trigger support queries after waiting for a long time when no refund is processed.
- Unable to re trigger refunds untill we use manaual-update api to mark as failed
Expected Behavior
If no connector call is made, the refund should immediately transition to failed instead of pending. This ensures:
• Transparency: Merchants know that the refund did not even begin, so they can take corrective action.
• Avoids customer confusion: Customers are not told their refund is in progress when it is not.
• Consistency: Only refunds that have actually been pushed to a connector should remain in pending.
Have you spent some time checking if this bug has been raised before?
- I checked and didn't find a similar issue
Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to submit a PR?
None