Online Banking Payments - some record as Non-sufficient Funds when client has receipt of payment
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
**Describe the bug in current situation**
This issue resulted from OPS ticket 2877. Client made online banking payment for Firm Registration but it was recorded as Non-sufficient Funds and registration was not completed. (BCROS account 32325 - Thaporn Kamhaeng - registering Body Culture with NR3742257. Staff completed registration for FM1020606)
When searching the payment in the Transactions section of the staff dashboard, it displays a status of Non-sufficient Funds despite that value not being in the drop down list of values for that column.
Why are online banking payments being recorded as non-sufficient funds when the client has the receipt that the payment was completed by the bank? (Note that this isn't happening with every online banking payment - we only hear of the ones that have issues)
**Link bug to the User Story**
**Impact of this bug**
Client's payment is taken from their bank account but registration is left uncompleted.
**Chance of Occurring (high/medium/low/very low)**
**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**
**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Actual/ observed behavior/ results**
Online banking payment completes successfully but payment is recorded as non-sufficient funds and registration doesn't complete.
**Expected behavior**
Online banking payment completes successfully, payment is recorded as complete and registration completes successfully.
**Screenshots/ Visual Reference/ Source**

Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the online banking payment and transaction-status handling, then verify that a successfully completed payment records as complete and allows registration to finish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100