🆕🎨You’ll soon be able to set @stripe Checkout branding dynamically via the API vs. relying on universal branding settings through the Dashboard. Let me know if you’d like early access to this feature! (mnATstripeDOTcom)
🆕 We shipped 2 @stripe Payment Links updates to help you build a text to pay flow:
- 🔒 *locked_prefilled_email*: use a URL parameter to prefill a non-editable email
- 📦 *price data*: create products and prices inline with the Payment Links API—no need for a separate API call
@burgalon@stripe This is all explained at the URL below, specifically how `s_f_u` is not compliant with some European data laws
https://t.co/PrfwPoFqEA
@burgalon@stripe By explicit consent I mean the customer has not explicitly consented to the saving of their payment details. There's no requirement for your integration to collect that prior to passing `s_f_u`, so payment information saved that way is 'hidden' by default (via `allow_redisplay`)
@burgalon@stripe 👋 Hey, Jonathan from the Checkout team here
We default to not pre-filling cards saved via `s_f_u` as there's no explicit consent collected from the customer
The recommended way to save cards to be automatically pre-filled is outlined here: https://t.co/LAQhTLhG1t
We've improved the Stripe Checkout look and feel when your customers move from in-app to web for purchases. Now Stripe Checkout makes it seamless to move from in-app to web—fast, compliant, and optimized for conversion.
Demo below, let us know any feedback!
@tech_nurgaliyev 👋 Hello from the Payment Links team!
Can you talk more about the webhook inconsistencies you're describing? Does sound unexpected, but there's probably a reason explanation