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
The previous language in the paymentsheet said:
(1) "Save this card for future [merchantDisplayName] payments." Now it says,
(2)"Save payment details to [merchantDisplayName] for future purchases".
The first one was better language because where the payment method was stored was ambiguous, while the second infers the payment information is stored with the us the merchant, which isn't true. All payment info is stored with Stripe, and the merchant can only see limited information about the payment, so it is misleading to our users to see in the SDK that payment method will be stored with with us. Our users are privacy-conscious and would prefer we don't store their payment info, so now there's more burden on us for better customer success/explanation that we indeed don't store their payment info. Since it's a simple copy change I hope that's doable on your end.
The text was updated successfully, but these errors were encountered:
@evelin1029 Thank you for your suggestion! We appreciate your insights and understand the importance of clear communication. We are actively looking into your feedback and have not yet made a final decision on the wording change. We are tracking this internally and considering how best to address the concerns you've raised. I will keep this ticket updated with any developments as we move forward.
The previous language in the paymentsheet said:
(1) "Save this card for future [merchantDisplayName] payments." Now it says,
(2)"Save payment details to [merchantDisplayName] for future purchases".
The first one was better language because where the payment method was stored was ambiguous, while the second infers the payment information is stored with the us the merchant, which isn't true. All payment info is stored with Stripe, and the merchant can only see limited information about the payment, so it is misleading to our users to see in the SDK that payment method will be stored with with us. Our users are privacy-conscious and would prefer we don't store their payment info, so now there's more burden on us for better customer success/explanation that we indeed don't store their payment info. Since it's a simple copy change I hope that's doable on your end.
The text was updated successfully, but these errors were encountered: