Is it possible to run an custom action when a buy was successful and set colums in the user profile?
I’ve done it without actions, duplicating the App: Sales tab, and using that do to a relation back to the user.
I think I have a tutorial for this in jesusvargas.glideapp.io
The user can change the email in the buy button screen.
So I have no chance to connect the buy with the user profile.
The email field should be locked or the Row-ID of the profile should be written to the app:buy tab.
Here the emails in the profile.
How can I match this when the user edits the mail while buying?
@Jacktools_Net that is a concern I have that users can change their email address that would return a no match. Be interesting to know if there was a way round this, although not seen an answer to this.
I do put a message on the previous screen to warn users not to change their email address on the buy screen.
Have you actually experienced anyone changing their email address?
The app is not published at the moment but while testing i run into this problem.
Adding a text to inform the user is a good idear, but enable this field by glide would be nicer.
But at the moment I have to wait until the user can purchase recurrent (monthly/ yearly) payments.
Other community members have worked out how to do membership - maybe this will help?
Thank you for the link. I will check it out. Unfortunately my no code stack is a little bit different. Let’s see what i can do with integromat and stripe or paypal.
@Jacktools_Net you can do it
Create a Business Profile whre the user can add the business information.
Let’s create Integromat a new Customer when a new line is added to the Business Profile.
Sounds like a challange.
I have done it without an action in the past using a unique id value. I am sure you can do the same with an action as well. Best of luck.
So after some research the Stripe Customerportal looks prommising.
This is how my Integromat scenario looks like. It works for stripe test and productive environment.
If the user has no customer Id in his profile the scenario creates a user, saves the new id in the profile sheet and open the customer portal.
If the user has a customer id then the scenario opens the customer portal.
On the glide site it is a simple button with open url as action.
Now the customer has a nice place where he can manage his plans and bills i guess.
Ok after a few days of learning I have to say it is straight forward to use glide and integromat with the customer portal of stripe.
This looks great, any thoughts on using this to make one off payments?
I just set up the new webhooks action to trigger a charge to a customer set up on Stripe through integromat, I’m then thinking to send the successful payments to gsheets and then use some logic to show payment successful.
I’m keeping stripe customer ID and card ID outside of gsheets and glide, just using lookups in integromat data. But I’m not a developer and still a little concerned with security with this method though…
I think, when I get you right, for one time payment you can use the buy button component from glide.
I only have the customer id in my g sheet but with row owner column.
Oh and I have the price ids in the product sheets.
Thanks Jack, sounds like a good set up.
I have been using the normal buy button, but running into some issues… hence the experimentation!
Perhaps this is a posible solution for you:
Ah thanks for your help, appreciate it. I tried this, but didn’t like the user could update the amount in the URL.
I’m using Stripe connect for transfer payments and billing for subscriptions. So may keep testing this option or just do a stripe checkout each time. Or hopefully Glides payment functionality is updated or I can find a workaround to keep it in the app.
I saw this complaint about PayRequest - this makes it a no-no!
"Ah thanks for your help, appreciate it. I tried this, but didn’t like the user could update the amount in the URL.
I’m using Stripe connect for transfer payments and billing for subscriptions. So may keep testing this option or just do a stripe checkout each time. Or hopefully Glides payment functionality is updated or I can find a workaround to keep it in the app."
Not sure if this is still a problem, but in my agency apps I have used PayHere’s URL method recently and has no problems with that. Very reliable.