#sharpie89-products-from-stripe

1 messages · Page 1 of 1 (latest)

lone bane
#

it depends on how you plan to use the data, and what you're request patterns look like

#

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

proud stone
#

Ah

#

Yes, but ordering and paginating etc. would have to be done custom

lone bane
#

but later to scale you'll definitely want to cache this data yourself somewhere

proud stone
#

Yeah, it would go over the limit too fast because of requesting for every little detail

lone bane
#

exactly

proud stone
#

Just keeping them synced would be the best option

lone bane
#

usually this is static data, too, so it's not necessary to retrieve anew each time you consume it, perfect for caching

proud stone
#

By caching u mean not inserting into a db?

lone bane
#

could be done many ways, but that's one sure.

proud stone
#

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?

lone bane
#

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

proud stone
#

how do i add apple pay and google pay?

I now have:

                    'alipay',
                    'card',
                    'ideal',
                    'bancontact',
                    'giropay',
                    'p24',
                    'eps',
                    'sofort',
                    'sepa_debit'
                ]```
lone bane
#

add to what?

proud stone
#

Those worked out-of-the box

#

To checkout

#

I don't have those 2

#

Or do those only appear when you're on phone?

lone bane
#

What device are you using?

proud stone
#

Google chrome

#

chromium*

#

On pc

lone bane
#

Those payment methods fall under card, but only appear if you have a suitable payment method saved

#

(saved browser cards are no longer applicable)

proud stone
#

Would I have to do anything or does the stripe checkout client pick this up automatically?

lone bane
#

then to test apple pay you must use safari and have a card saved in your wallet

proud stone
#

they're on, i'm gonna assume they're probably working. Thanks!

chilly dune
#

catching up here, let me know if you aren't able to get that working and I can help!

lone bane
#

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

chilly dune
#

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

proud stone
#

Aha

chilly dune
#

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

proud stone
#

isn't it handy to have automatic tax though?

chilly dune
#

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"

proud stone
#

oh yes

chilly dune
#

but ultimately for Automatic Tax right now, Google and Apple Pay aren't supported so you keep it in for your business use-case

chilly dune
#

I see the Google Pay button there! ^

proud stone
#
                '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.

chilly dune
#

oh sorry just saw this

#

why would anyone not want to use it?
users who want to build their own payment form. But I would use Checkout, it is very easy to get started and Stripe handles all the payment methods automatically for me so I have way less integration work