#sharpie89-products-from-stripe
1 messages · Page 1 of 1 (latest)
it depends on how you plan to use the data, and what you're request patterns look like
Learn about API rate limits and how to work with them.
Stripe enforces rate limits on your API requests
so it's possible, and for low request rates it may be a reasonably quick way to get your app running
but later to scale you'll definitely want to cache this data yourself somewhere
Yeah, it would go over the limit too fast because of requesting for every little detail
exactly
Just keeping them synced would be the best option
usually this is static data, too, so it's not necessary to retrieve anew each time you consume it, perfect for caching
By caching u mean not inserting into a db?
could be done many ways, but that's one sure.
Do you have experience in a way that works flawlessly?
I think without db it could be done in something like redis? And then it would be synced daily or something?
I wont claim any perfect way, every technique has tradeoffs but yes exactly something like that for quick recall
reload from api once per day instead of once per customer page visit
how do i add apple pay and google pay?
I now have:
'alipay',
'card',
'ideal',
'bancontact',
'giropay',
'p24',
'eps',
'sofort',
'sepa_debit'
]```
add to what?
Those worked out-of-the box
To checkout
I don't have those 2
Or do those only appear when you're on phone?
What device are you using?
Those payment methods fall under card, but only appear if you have a suitable payment method saved
You need to may sure you have a saved payment method in google pay: https://pay.google.com/gp/w/u/0/home/paymentmethods
(saved browser cards are no longer applicable)
Would I have to do anything or does the stripe checkout client pick this up automatically?
Make sure apple pay and google pay are turned on in your Checkout payment method settings: https://dashboard.stripe.com/settings/checkout
then to test apple pay you must use safari and have a card saved in your wallet
they're on, i'm gonna assume they're probably working. Thanks!
catching up here, let me know if you aren't able to get that working and I can help!
if you share a session url from an API create request @chilly dune or i can check to confirm for you
we have payment methods set up for both apple & google
O yeah if that's possible
does that work?
also: is there a downside to using checkout?
checking
is there a downside to using checkout?
not sure what downside you're thinking of?
ah I think I know what the issue is, checking
you're using Automatic Taxes on your CheckoutSession, for which Google Pay and Apple Pay aren't supported yet
so those buttons will not show up
Aha
if you remove the automatic_tax param entirely, you should see a CheckoutSession without Automatic Tax but it will show the Apple and Google Pay buttons
isn't it handy to have automatic tax though?
oh it absolutely is
I was more so saying "if you want to see Google Pay and Apple Pay in action, you can temporarily remove that param in test mode to see how they work"
oh yes
but ultimately for Automatic Tax right now, Google and Apple Pay aren't supported so you keep it in for your business use-case
I see the Google Pay button there! ^
'automatic_tax' => [
'enabled' => false,
],
'payment_method_types' => [
'alipay',
'card',
'ideal',
'bancontact',
'giropay',
'p24',
'eps',
'sofort',
'sepa_debit'
]
nice!
Yeah about the downsides: as in: why would anyone not want to use it?
Besides the styling stuff, just purely based on functionality
I'm kinda amazed at how easy this was. I installed laravel-cashier, run a new container with stripe cli listening and with checkout (which laravel-cashier has functions for) all within a few hours. So I'm just wondering why anyone would not use checkout, because it's way too easy.