There is a bug that leads to internal transactions with an amount that matches the CrowdNode API amount to be considered a possible CrowdNode response.
Issue being fixed or feature implemented
Only check for possible CrowdNode responses if it's an incoming transaction.
Related PR's and Dependencies
Screenshots / Videos
How Has This Been Tested?
[ ] QA (Mobile Team)
Checklist:
[x] I have performed a self-review of my own code and added comments where necessary
[x] I have added or updated relevant unit/integration/functional/e2e tests
There is a bug that leads to internal transactions with an amount that matches the CrowdNode API amount to be considered a possible CrowdNode response.
Issue being fixed or feature implemented
Related PR's and Dependencies
Screenshots / Videos
How Has This Been Tested?
Checklist: