Payments - Failed to set a default payment method when entering correct password

[kbecciv]

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

---

Action Performed:

Prerequisite: Set the VBA in testing account

1. Launch the app
2. Log in expensifail account
3. Go to Setting - Payment
4. Tap on Verified Account
5. Tap Set a default payment
6. Enter correct password
7. Tap Make Default payment method

Expected Result:

VBA is set as default payment method when entering correct password

Actual Result:

Failed to set a default payment method when entering correct password

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.34.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5434778_Screen_Recording_20220202-101003_New_Expensify.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @mountiny (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[mountiny]

@kbecciv I have checked the backend repository and it seems like this is related to the fact this card has been used very quickly after the last time it was used, which is fraud detection. Since this is a testing card, it makes sense.

Would you be able to retest this in a while?

[kbecciv]

@mountiny I will retest the debit card issue and update you.

[kbecciv]

@mountiny After using wrong password and submitting the form, I see the following message: Incorrect Expensify password entered.

Screen_Recording_20220202-123043_New.Expensify.mp4

[mountiny]

@kbecciv Thank you for retesting. This new video shows I think different scenario than when it was originally reported.

When it comes to the Cannot validate at this time due to rate limit on maskedPAN error in the originally reported issue, that seems to me still as a problem stemming from testing using this card very quickly in a row. Would you be able to retest with the correct password going first?

In the case, you have shown in the comment, I looked up where the Your card was declined. error message comes from and it is from Stripe directly and that also leads me to think that there is some problem with the testing card. We would definitely want to retest this and see what the pattern is, whether we can observe different behaviour using other cards.

[kbecciv]

@mountiny The reported issue is Failed to set default payment when entered correct password. Applause team are thinking this two issues have the same root of cause that's why I attached the screenshot with error message Cannot validate at this time due to rate limit on maskedPAN. Sorry for the confusion.

[mountiny]

Ah, I see. Thank you for the clarification.

I think I am quite sure that the cause for these two errors should not be the same. The one with maskedPAN comes from our own backend code, whereas the other one which simply says declined is coming from Stripe.

I think we should give this more tries to replicate since, in the case of the maskedPAN, this really should happen only if the same card is being added many times. In real use, this is not a problem (or signals fraud), but in testing, we are using the same cards and I guess the card details and the rate they are used at cause this error.

Could we retest this week some different cards for example? (not sure what is available for Applause)

[mountiny]

Any update here @kbecciv? Do we have some other cards we can test just to eliminate the option this is caused but re-use of the same card. Thank you

[kbecciv]

@mountiny Let me check with Applause team and I will update you.