[Bug]: Payment Blocks: No longer allow cloning card payment methods into or out of India

jjchrisdiehl commented 2 years ago

Quick summary

As reported here (pNPgK-5LT-p2), it appears that Stripe allows our platform to use access tokens to pull in customer card data if they already entered it elsewhere, but in the case of this customer in India, Stripe does not allow for this cloned card process to happen due to newer India data regulations.

Error message:

It appears that you are cloning a card payment method to a IN-based connected account. As part of our continued investment in India and to meet local data storage requirements, we no longer allow cloning card payment methods into or out of India, so we had to reject your request. For more information, please visit https://stripe.com/india-data-storage-faq.

https://stripe.com/docs/connect/cloning-customers-across-accounts

Steps to reproduce

See steps in above p2 from Thelma.

What you expected to happen

Stripe should load customer's saved payment methods.

What actually happened

Error saying the credit card details seem to be wrong.

Context

No response

Browser

No response

Simple/Atomic

No response

Other notes

No response

Reproducibility

Consistent

Severity

Some (< 50%)

Available workarounds?

No response

Workaround details

No response

sirbrillig commented 2 years ago

Probably the same as pNPgK-5te-p2 and this issue: https://github.com/Automattic/wp-calypso/issues/54038 which concludes that fixing this is complicated.

pauljacobson commented 2 years ago

We have a user who is affected by this in 5081098-zen

I'm including their details here so we can follow-up with the user once this issue is resolved.

AMcGrady commented 2 years ago

We have a user who is affected by this in 5538958-zen

I'm including their details here so we can follow-up with the user once this issue is resolved.

github-actions[bot] commented 2 years ago

Support References

This comment is automatically generated. Please do not edit it.

[ ] 5081098-zen
[ ] 5538958-zen
[ ] 7032306-zen

cuemarie commented 1 year ago

This report was found during a recent backlog sweep.

📌 ACTIONS

Added to Other as this is already on Shilling's radar

sudeepbaral commented 1 year ago

New issue reported here:

[ ] 7032306-zen

sirbrillig commented 1 year ago

Assigning to @Automattic/gold now that we have a team who works on Payments Blocks.

davemart-in commented 1 month ago

I don't think anyone outside of the Gold or Shilling team will pick this up. Removing this from The One Board.

millerf commented 1 month ago

I was not aware of this one. @michaeldcain or @sirbrillig I wonder if this is specific to Monetize or if this is also BD-related...

sirbrillig commented 1 month ago

I've put this into the Shilling team board to look at during out next meeting.

michaeldcain commented 1 month ago

@millerf it looks like this is a known issue with Monetize, related to cloning payment methods for connected accounts (not specific to BD). There's a related issue that looks like it would fix this as a side effect: https://github.com/Automattic/wp-calypso/issues/54038

michaeldcain commented 1 month ago

Jess shared the following link to where this might be happening for Monetize payment intents: fbhepr%2Skers%2Sjcpbz%2Sjc%2Qpbagrag%2Syvo%2Sovyyvatqnqql%2Sfep%2Sfgevcr%2Sfrg%2Qcnlzrag%2Qvagrag%2Qfgrc.cuc%3Se%3Q3790377s%23164%2Q200-og

millerf commented 1 month ago

@millerf it looks like this is a known issue with Monetize, related to cloning payment methods for connected accounts (not specific to BD). There's a related issue that looks like it would fix this as a side effect: https://github.com/Automattic/wp-calypso/issues/54038

@michaeldcain It looks like a major shift in the current approach 😓 I'll try to organise that at some point.

Automattic / wp-calypso