[Due for payment 2026-03-30] [$250] The real return reason is only show in Expensify Classic when a report payment bounces

[twisterdotcom]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.3.18-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers): ted@expensify.com
Logs: https://stackoverflow.com/c/expensify/questions/4856: 9cbd5d9f6968db8c-SJC
Expensify/Expensify Issue URL: https://github.com/Expensify/Expensify/issues/595045#issuecomment-3884615330
Issue reported by: @twisterdotcom
Slack conversation (hyperlinked to channel name): https://github.com/Expensify/Expensify/issues/595045#issuecomment-3884615330

Action Performed:

Precondition:
Have an approved reimbursable report on a workspace with a CorPay reimbursement account set on it. Have a deposit account set that is not USD.

1. Amend your deposit account so the name doesn't match your account details
2. After approval, have the VBA admin pay the report
3. Wait for the bounce back
4. See the reportAction show the return reason in Expensify Classic but not in New Expensify:

Expected Result:

The return reason should show for in both platforms. It should read:

couldn't process the payment: $returnReason

When no returnReason is available, it should default to the same return reason we send via email in https://github.com/Expensify/Web-Expensify/blob/main/lib/Notification/ACHCreditBounce.php which is:

couldn't process the payment due to an incorrect routing/account number or closed account

Actual Result:

We always show due to a bank account issue.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @abbasifaizan70

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (External)

[melvin-bot]

Current assignee @twisterdotcom is eligible for the Bug assigner, not assigning anyone new.

[melvin-bot]

Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

[melvin-bot]

⚠️ Could not update price automatically because there is no linked Upwork Job ID. The BZ team member will need to update the price manually in Upwork.

[abbasifaizan70]

Proposal: ACH bounce return reason not shown in New Expensify report action

Please re-state the problem that we are trying to solve in this issue.

When a reimbursable report is paid via CorPay (VBA admin pays the report) and the payment bounces back (e.g. after amending the deposit account so the name doesn’t match account details), the report action in Expensify Classic shows the specific return reason from the payment processor. In New Expensify, the same report action always shows the generic message “due to a bank account issue” instead of the actual return reason. The return reason should be visible in both platforms.

What is the root cause of that problem?

New Expensify builds the message for REIMBURSEMENT_ACH_BOUNCE report actions in getMessageOfOldDotReportAction by always returning a single static translation and never reading the returnReason from the action’s originalMessage. The backend (Web-Expensify) stores the return reason in the report action when sending the ACH bounce notification (e.g. from the flow that uses the default text in ACHCreditBounce.php when no specific reason is available). Expensify Classic renders the message from the backend, so it shows the return reason. New Expensify ignores originalMessage for this action type and only uses:

App/src/libs/ReportActionsUtils.ts

Lines 1884 to 1888 in a257c62

	case CONST.REPORT.ACTIONS.TYPE.OUTDATED_BANK_ACCOUNT:
	return translate('report.actions.type.outdatedBankAccount');
	case CONST.REPORT.ACTIONS.TYPE.REIMBURSEMENT_ACH_BOUNCE:
	return translate('report.actions.type.reimbursementACHBounce');
	case CONST.REPORT.ACTIONS.TYPE.REIMBURSEMENT_ACH_CANCELED:

The translation key report.actions.type.reimbursementACHBounce is a fixed string:

App/src/languages/en.ts

Line 7275 in a257c62

reimbursementACHBounce: `couldn't process the payment due to a bank account issue`,

So the displayed message never includes the actual returnReason from the report action.

What changes do you think we should make in order to solve the problem?

Use the returnReason from the report action’s originalMessage when present: display “couldn’t process the payment: {returnReason}”. When returnReason is missing, display the same default text used in the backend email (e.g. in Web-Expensify’s ACHCreditBounce.php): “couldn’t process the payment due to an incorrect routing/account number or closed account”. Type the originalMessage for REIMBURSEMENT_ACH_BOUNCE to include optional returnReason, add translation keys for the two message variants, and in getMessageOfOldDotReportAction branch on originalMessage.returnReason to choose the correct message.

Solution:

--- a/App/src/types/onyx/OldDotAction.ts
+++ b/App/src/types/onyx/OldDotAction.ts
@@ -141,7 +141,7 @@ type OriginalMessageReimbursementACHBounce = {
     actionName: typeof CONST.REPORT.ACTIONS.TYPE.REIMBURSEMENT_ACH_BOUNCE;
     /**
      *
      */
-    originalMessage: Record<string, unknown>;
+    originalMessage: Record<string, unknown> & {returnReason?: string};
 };

--- a/App/src/libs/ReportActionsUtils.ts
+++ b/App/src/libs/ReportActionsUtils.ts
@@ -1883,8 +1883,12 @@ function getMessageOfOldDotReportAction(translate: LocalizedTranslate, oldDotAct
         case CONST.REPORT.ACTIONS.TYPE.OUTDATED_BANK_ACCOUNT:
             return translate('report.actions.type.outdatedBankAccount');
         case CONST.REPORT.ACTIONS.TYPE.REIMBURSEMENT_ACH_BOUNCE:
-            return translate('report.actions.type.reimbursementACHBounce');
+            return originalMessage?.returnReason
+                ? translate('report.actions.type.reimbursementACHBounceWithReason', {returnReason: originalMessage.returnReason})
+                : translate('report.actions.type.reimbursementACHBounceDefault');
         case CONST.REPORT.ACTIONS.TYPE.REIMBURSEMENT_ACH_CANCELED:
             return translate('report.actions.type.reimbursementACHCancelled');

--- a/App/src/languages/en.ts
+++ b/App/src/languages/en.ts
@@ -7273,7 +7273,8 @@
                 outdatedBankAccount: `couldn't process the payment due to a problem with the payer's bank account`,
-                reimbursementACHBounce: `couldn't process the payment due to a bank account issue`,
+                reimbursementACHBounceDefault: `couldn't process the payment due to an incorrect routing/account number or closed account`,
+                reimbursementACHBounceWithReason: ({returnReason}: {returnReason: string}) => `couldn't process the payment: ${returnReason}`,
                 reimbursementACHCancelled: `canceled the payment`,

Apply the same new keys (reimbursementACHBounceDefault and reimbursementACHBounceWithReason) in other locale files under report.actions.type with the same default string and the “couldn’t process the payment: {returnReason}” pattern, and remove or repoint any existing reimbursementACHBounce usage to the default key so behavior is consistent.

[twinkle-react]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[github-actions]

⚠️ @twinkle-react Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

[melvin-bot]

@suneox Whoops! This issue is 2 days overdue. Let's get this updated quick!