You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When retrying a failed ACH payment, a raw variable dump appears in the customer error message. This issue occurs in both the Blocks and Shortcode checkouts.
To Reproduce
Steps to reproduce the behavior:
Attempt to pay with ACH using the test account 000777777771 and routing number 110000000. The payment should fail.
Without refreshing the page, retry the payment using the account 000000000009 and routing number 110000000.
Observe that the error message includes a raw variable dump.
Note: These test accounts are from Stripe’s documentation: Testing ACH.
Expected behavior
On the second attempt, the payment should be processed successfully without displaying a raw variable dump in the error message.
If an error message is displayed, it must be useful for the shopper.
Screenshots
Screen.Recording.2025-02-27.at.08.57.38.mov
Environment (please complete the following information):
WordPress 6.7.2
WooCommerce 9.7.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When retrying a failed ACH payment, a raw variable dump appears in the customer error message. This issue occurs in both the Blocks and Shortcode checkouts.
To Reproduce
Steps to reproduce the behavior:
000777777771
and routing number110000000
. The payment should fail.000000000009
and routing number110000000
.Note: These test accounts are from Stripe’s documentation: Testing ACH.
Expected behavior
On the second attempt, the payment should be processed successfully without displaying a raw variable dump in the error message.
If an error message is displayed, it must be useful for the shopper.
Screenshots
Screen.Recording.2025-02-27.at.08.57.38.mov
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: