#gtilflm-quickstart
1 messages · Page 1 of 1 (latest)
gtilflm-quickstart
Hey @blissful harbor the CLI is optional and really only used when you're working locally on your own computer to build your code. Most developers first develop locally and only deploy to their hosting provider after their code is ready.
OK. I actually have a way of testing on the live site without disturbing things.
All I really want to do is send the API an amount and a customer name (maybe even email or customer ID too), then have them be able to pay via credit card.
Sure, but all of that requires careful planning as the developer really. Are you an experienced developer writing your own website/app integration and fully understanding how all of this works?
And this would be PHP so https://stripe.com/docs/api/authentication?lang=php
I'm fairly inexperienced, but I've done some API stuff before, and I built my own site.
Looks like you send info. via curl, then get back a json object.
Unless I'm missing something.
you definitely shouldn't just use curl, we have an entire PHP library for it. I'd recommend starting with https://stripe.com/docs/development/quickstart?lang=php and installing the Stripe CLI locally to get a feel for the API really
Thanks for replying!
you might want to look at https://stripe.com/docs/payments/payment-links which makes it easy to accept payments with little to no code. Or https://stripe.com/docs/checkout/quickstart?lang=php for an easy integration in PHP with some limited code.
Looks like you first have to use composer to install stripe-php though, which requires command line access.
Composer is the canonical way to install php libraries for most PHP developers nowadays. It's definitely something most developers would use.
You can also do a manual installation otherwise per https://github.com/stripe/stripe-php#manual-installation
Ok, that could work. Shared hosting is..... limited
many shared hosts providers support Composer
lol
Was just looking at that
Not sure if you can weigh in on this. If you need to be done, then no worries.
did you create that composer.json or provide the right permissions? That's really something you should discuss with your hosting provider