@gaffneyantonio in case you mean the Customer ID, it is retrieved using plugin’s data calls, but you use it On page load event, depending on your mode:
@natvancleve it is strange why the Session ID is not retrieved on your side, but could you please try to use any of our demo examples the exact way and give it a try again.
It is not required to fill in, but the Image is being empty only in case the provided source is empty, or not provided at all.
Please note that you need to provide a List of images of your product:
And depending on your mode, if it’s payment, you can use the following setup to extract the customer ID if you need:
If I hit yes, I go to stripe checkout. If I hit no, the rest of the workflow happens without going to checkout.
Should I instead have these steps trigger on page load once the user gets to the success URL? And if so, is there some successful transaction Id or something I can send as a parameter?
Sure, you are able to trigger any workflows after a successful payment. When you land back from checkout on your successful URL page, you set on page load to check for the success code form your URL indicated in Create a session action. Then you can set any workflow you want after that. In our demo case, we save the ID from the customer, transaction etc. but you can set any ID you want.
Hello!
I’ve been playing around with the plugin for a while now. When I create a seller (connect standard/express account), I am able to redirect them to the stripe login, but when they come back to my app, the stripe ID isn’t stored. I use the workflow “complete standard/express account connection” and use “get code from page URL”, but the workflow doesn’t run and I’m unable to store the code into the database. I call on the token that is on the page I redirect the user to.
Happy to send an editor link in private; let me know if I am missing something
@natvancleve unfortunately this set up is not going to work because you are creating a redirect URL with session ID which hasn’t been created yet, which is why it is throwing the error. The best way of saving the session ID (if you will) is by saving it into a database field to your Current User. What you are trying to achieve in the URL it would not be possible for session ID, unfortunately.
@dannyliu you just need to set the On page load event with the complete action, in order to save the code from URL and save the stripe id into your database by making changes to your Current User. Please check our demo and its editor for preview.
If you look at my images, it’s creating a session ID, no? It creates a session ID whether I send that ID to the success URL or save it to the database. My checkout is working fine, and checkout requires the session ID, right?
What isn’t working is the “retrieve a session” call.
Yes, it does create the session ID but it is not possible to use it in the URL as you’re trying to pass. If you have no troubles at checkout then everything is ok. The only thing is that if you need to store the session ID in your database field, you just do it afterwards in your workflows as per our demo.
P.s. is it possible that we could hop into a video call for 5 minutes?
I think it would save us both time and I don’t want to keep spamming this thread. This is the only thing I need to get working before I share my app with the world.
Could you please add our support@zeroqode.com account to your Settings / Collaboration tab (ignore the warning message regarding plan, we are an agency and you can easily add us).
We’ll take a look into your workflow setups to see where the problem is, among with our developers.
Tell us your app name and page name where it occurs on test. We’ll investigate it inside your app then give a proper feedback asap. This will speed things up.
Thanks for your invitation. We have received it and are able to check on your app. Could you please provide the following details as previously mentioned:
As well as the exact steps to follow in order to reproduce the error.
We have checked on your app, but why do you need to verify whether or not a transaction was successful, because when the buyer is redirected back to the Success URL it already means that it was successful if you receive the success=yes in the URL params.
This would be doubling the work already handled by plugin.
I want to create a transaction in my database after checkout. I need a way to confirm that a unique transaction has taken place. Otherwise reloading the page or manually changing the success parameter to yes would create a new transaction.
I got the impression from your earlier comments that using the session ID was the best way to confirm a transaction. Is there another way?
Yes, using the session ID is the best way but you don’t need to retrieve it in order to verify a successful transaction because when you are redirected back to your page, you are using the Success URL specifically on this matter, so you can know by a URL param that it has been successful.
Sorry but this is not reproducing on our side. It should not be reproducing on our side as well if everything is configured properly. If you are saying that checkout is working fine, you’re all set up at this point. There is no need to verify it again by trying to retrieve the session ID at your own.
I am trying to change the “default payment description” which at the moment is the “connected accounts’ inserted website”.
So if a partner enters their Facebook site in the website field - and someone buys from them - the description for the payment is “www.facebook.com” which obviously is a bit scary.
I would like to set the default payment description to my own domain / the partner’s name.