Some Context:
1. Austin Deculus and Bobby Hart got constant help. That is, they got to block the edge after he was chipped or hit by the TE/RB or Harris. GRo finally realized that Alt is not playing, and that both tackles need help concurrently.
2. Bozeman had 4 bad snaps, 3 of which b/c Jaelen Phillis moved inside (instead of dealing with a TE+Tackle). The other 34 snaps of Bozeman were good. The 13 yards screen to Dissly was all Bozeman.
3. Becton is responsible to the critical pressure on Herbert by Phillips (miraculous pass play to Ladd). Phillips got to Herbert in record time because Becton did nothing... we need to start having this conversation: Becton is not good.
Justin Herbert just threw for a first down on 2nd&18 and 2&28 on consecutive snaps, both wiped out by penalties. It's time to once again call for the football gods to get him out of that franchise.
Draft day today, the return of the Phat Tekkers Fantasy League!
Forfeits, Bets & Thundercunt behaviour
Be a shame not to re run this video from last year, the laughs at my expense.
Filmed in a nice Italian with the family*
#nflfantasy#fantasyfootball
🆕🎨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 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`)
If you're using Stripe Checkout with `setup_future_usage: 'off_session'` - you're probably missing on making a subsequent call for updating payment method to redisplay - see 👇
@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: #save-payment-methods-to-prefill-them-in-checkout" target="_blank" rel="nofollow noopener">docs.stripe.com/payments/check…
Now, the next time the user makes a 2nd purchase, he will be able to choose from his existing on-file payment method. How come this is not the default @stripe ?
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
It is very interesting
But Stripe webhooks are not very consistent
When I am trying different payment links it could give different values and some fields could be null
well, will figure it out eventually but I think there is should be a better solution for that
what's the right way to do @stripe subscriptions?
I think @levelsio does Stripe Payment Links but it seems like Stripe wants you to use Stripe Checkout Sessions?
@theo you know? anyone?
does it matter? already got an implementation working. Aside from not being able to set an editable email address with Stripe Checkout Sessions does it matter?