PAY-API / PAY-JOBS - Move Credit Memo creation to Job
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
## What is the problem?
* Currently credit memo creation (PAD and Online Banking refunds) are done synchronously. This was done keeping in mind that the number of refunds would be in low numbers and can happen during business hours. But with the number of NR refunds happening, this is causing issue when someone is trying refund when CFS is down.
PS: We had one occurrence in prod https://sentry.io/organizations/registries/issues/2828553721/?environment=production&project=1762954&referrer=alert_email
## What is the impact?
* PAD and Online Banking refunds fail when CFS is down.
* Related to Ops devs running the refund script, and can come from Name Request Cancellations too.
* Low volume
* Resolution actions - retry the refund if using script, Name Request does not handle this.
## Proposed solution
* Move refund action (CMS creation) to job
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the PAY-API and PAY-JOBS refund and CMS-creation entry points, then trace the PAD and Online Banking refund flow and the Name Request cancellation path. Move the refund action into the job flow and verify that refunds no longer fail when CFS is down, including the retry behavior described for the refund script.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, javascript, postgres, python
- Domain
- api, backend, payments
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100