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
When using PaymentRequest to handle apple/google pay integration, create payment_method (POSTv1/payment_methods) might fail if the email address from the wallet account is invalid (e.g. having trailing whitespaces [email protected]).
Though these kind of emails seem to have already been caught/handled on newly created wallet accounts, in live/prod scenarios a small percentage of old accounts still have email addresses with trailing whitespaces.
A proposed solution is to trim trailing whitespaces from email address value before using it on billing_details.email when creating payment method within PaymentRequest flow
Environment
No response
Reproduction
No response
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hey @ivanwidj -- no update to share here but I would suggest writing in to support as well, describing this problem, sharing a link to this issue and ideally including examples of failed payments/PM creation requests as a result.
What happened?
When using
PaymentRequest
to handle apple/google pay integration, createpayment_method
(POST
v1/payment_methods
) might fail if the email address from the wallet account is invalid (e.g. having trailing whitespaces[email protected]
).Though these kind of emails seem to have already been caught/handled on newly created wallet accounts, in live/prod scenarios a small percentage of old accounts still have email addresses with trailing whitespaces.
A proposed solution is to trim trailing whitespaces from email address value before using it on
billing_details.email
when creating payment method withinPaymentRequest
flowEnvironment
No response
Reproduction
No response
The text was updated successfully, but these errors were encountered: