Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] CASHTOCODE Error Message appearing as null #7155

Open
2 tasks done
Debarshi-Gupta opened this issue Jan 31, 2025 · 0 comments · May be fixed by #7154
Open
2 tasks done

[BUG] CASHTOCODE Error Message appearing as null #7155

Debarshi-Gupta opened this issue Jan 31, 2025 · 0 comments · May be fixed by #7154
Labels
C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet

Comments

@Debarshi-Gupta
Copy link
Contributor

Bug Description

There is a bug which causes error_message to appear as null on failed payments for Cashtocode.

Expected Behavior

Error_message should not be null on failed payments for Cashtocode

Actual Behavior

Error_message is null on failed payments for Cashtocode

Steps To Reproduce

Error_message is null on failed payments for Cashtocode

Context For The Bug

No response

Environment

Integ, Sandbox, Prod

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?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

@Debarshi-Gupta Debarshi-Gupta added C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet labels Jan 31, 2025
@Debarshi-Gupta Debarshi-Gupta linked a pull request Jan 31, 2025 that will close this issue
14 tasks
@Debarshi-Gupta Debarshi-Gupta linked a pull request Jan 31, 2025 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant