-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$250] Expense - "Debit or credit bank account is not set up on Corpay" error when paying elsewhere #55731
Comments
Triggered auto assignment to @twisterdotcom ( |
Global Reimbursement is currently in development. @madmax330 is this expected now/do we have a plan to address already? |
Job added to Upwork: https://www.upwork.com/jobs/~021884400529827139603 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani ( |
Hmm that's strange, it should not be trying to use corpay in this case, I'll have a look at the logs and see if I can fix it |
@madmax330, @twisterdotcom Eep! 4 days overdue now. Issues have feelings too... |
@madmax330 anything I can do here? |
No I'm working on the PR as we speak |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.89-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Money Requests
Action Performed:
Precondition:
Expected Result:
No error should occur because admin pays elsewhere.
Actual Result:
"Debit or credit bank account is not set up on Corpay" error when paying elsewhere.
Workaround:
Unknown
Platforms:
Screenshots/Videos
bug.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @madmax330The text was updated successfully, but these errors were encountered: