[Enhancement]: Make Payment Dispute flexible to capture from other payment providers
- Dominant language
- Python
- Stars
- 562
- Forks
- 410
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 197
Description
### Affected Area
None
### Problem Statement
Currently Payment dispute is captured only from Stripe but it would be better if we can capture disputes from other providers as Paypal, Razorpay etc
### Proposed Solution
Links:
https://razorpay.com/blog/chargebacks/#What%E2%80%99s_the_process_to_resolve_a_chargeback
https://razorpay.com/docs/webhooks/disputes/#list-of-disputes-webhook-events
https://razorpay.com/docs/payments/disputes/dashboard/#view-disputes
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the existing Stripe dispute-capture flow and the linked Razorpay webhook and dispute documentation. Identify provider-specific assumptions and define the desired provider-neutral behavior, including supported events and completion criteria. No files or tests are named in the issue, so those need to be located before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100