#fubobull-checkout

1 messages · Page 1 of 1 (latest)

errant helm
#

hi there! can you share the issue which you're running into?

analog wave
#

sorry

#

I am not as familiar with discord

errant helm
#

np!

#

the way Stripe Checkout works is that your frontend makes a request to your server. Your server will then make a request to Stripe to create the Checkout Session. Your server would then return the Checkout Session URL to your frontend

#

since the "form" doesn't appear on your site : have you tried walking through your implementation to see which part of the process is the issue at yet?

analog wave
#

All I want is a one page check out. I don't want a shopping cart. All I want to do is just have a virtual terminal like authorize net has, where they can enter a credit card to pay for a set price

errant helm
#

are you always selling the same product?

#

i.e. there's no changes to the items

analog wave
#

I sell tickets for comedy shows

#

so the price will vary per show, and per seat

#

So i just need to input 1 amount

#

and then charge that amount. Everything else I will do on the backend after it has been authorized.

#

as a for instance in connect-direct-charge-checkout-master

#

the only files are

#

index.php which does nothing

#

create-checkout-session.php

#

shared.php which also does nothign

#

script.js

#

guitar.png

#

success.php and canceled.php both empty

#

a css directory

#

if I go to my example page:

#

I get the error. But I have already completed those steps

#

I already had a .env file. and put all those setting in it

#

And this is what I am saying. I have tried this on like 5 different instances that you download. it is the same crap different day.

#

If I had to guess it is probably missing checkout.js

errant helm
#

hmmm, onesec, let me take a look at that sample and try it out too

analog wave
#

I am looking at github, and it appears the files in the zip are not the same as the files listed on the actual page.

#

That is not the same as what is downloaded in the zip

#

I am trying those now

errant helm
#

are you getting this error?

analog wave
#

Is that from your implementation?

#

I just uploaded something else.

#

let me test

#

this is what I get

#

Missing .env
Make a copy of .env.example, place it in the same directory as composer.json, and name it .env, then populate the variables.

It should look something like the following, but contain your API keys:

STRIPE_PUBLISHABLE_KEY=pk_test...
STRIPE_SECRET_KEY=sk_test...
STRIPE_WEBHOOK_SECRET=whsec_...
DOMAIN=http://localhost:4242
BASE_PRICE=1000
You can use this command to get started:

cp .env.example .env

#

However, that is not correct.

#

I already set all that

errant helm
#

can you share a screenshot of the folder with the .env file?

analog wave
#

I think part of the issue is the directions are not straight forward. You have to go to so many different places to figure this out, and your nav, honestly is just not great

#

it is impossible to figure out where to go for the different things you have to integrate.

errant helm
#

your folder looks different from the one which i've cloned from the sample

#

i think you're in the public folder?

#

my server folder looks like this

unknown.png
analog wave
#

Correct

#

that is in my main director

#

directory

#

My public directory is pay

#

the pay directory is what I sent you a screen shot of.

#

I have a ton of other files in the directory that is ../ back from that

errant helm
#

it looks like you're trying to modify your code to fit that of the sample?

#

cause if i try to run the sample as it is, it works

analog wave
#

nope it is as is

#

Just edited the variables that apply to me

#

like api key

#

etc

#

I think i am done wasting my time on this

#

Your documentation is really lacking.

#

for instance web hooks.

#

I was able to set one up on my server

#

but then what

#

i can generate a php

#

from that, but what do I do with it?

#

your instructions are lacking

#

everyone that sets this up must be psychic

#

It really doesn't give a good overview of how to use web hooks

#

It is just one giant mess just like the rest of the site

#

I downloaded a zip wiht the sample code for web hooks and it had a server.php script in there

#

so what do I do with that.

#

when i try to run it server side, through https it doesn't even work

errant helm
#

sorry about that, i'll pass on the feedback. If you want to continue troubleshooting i'd be happy to help - i'd probably suggest starting afresh and we can walk through the sample step by step to get you setup if you want to continue

analog wave
#

Yeah, I just don't have another 40 hours to waste on this.

#

it needs to be simple

#

the documentation is utterly useless because it is all fragmented

#

people just want to be able to get up and running fast.

#

you should just have a different zip for every language

#

and it should be setup with private and then /www folder. Everything should be in that folder. you should outline all prompts to make on the server, and then have a simple config file.

#

it really isn't that complicated

#

If I setup an authorize.net account, i will be up and running in like 5 mintues

#

not an exageration

errant helm
#

i'm a bit confused because your sample looks different from the one i cloned. Typically, following the readme would get you up and running. But i definitely do agree that it can be a bit overwhelming for someone new to Stripe.