Sure would!
Actually I just realized that for my use case, because each individual is setting up their own individual link, I wouldnt have access/control over the information that is passed through their receipt of payment, meaning I cant zap any data back into Glide/GS. That is where a marketplace type of payment system would come in handy! It would also keep it a more consistent and on brand UX. Guess Iāll have to wait for Glide to implement something like Stripe Connect.
Awesome setup!
Howād you get the buttons to be so big? Good oleā CSS wizardry again!? āā
Is the ālocking customer detailsā so they canāt edit the payment screen a universal parameter or one set by Payhere?
Thanks again Robert - anxious for Part 2!
Yep! Just a simple line of code to add padding to the button.
That parameter was created by Payhereās Embed SDK.
Alright yāall, Part 2 is available!
Featuring
- Setting up Integromat Webhook: Payhere > Google Sheets > Glide App deep dive
- Validating subscription/membership status
- Keeping everything IN-APP using Glide Deeplinks in the Payhere success URL
- Completion of user onboarding based on subscription/membership status
Enjoy!
Awesome!
7.30, on a holiday, watching Robert Petitto how-toās, life is good.
Pls stop with all the wonderful solutions that are based on stripe⦠Itās really upsetting for those if us who canāt use it and need to do crazy workaroundsā¦
Sorry brother.
Thanks again for another wicked video! Weāre def gonna integrate this solution for a client!
Just a quick question in regards to the above quote:
When you insert the deep link in the Success URL, does āGlideā just close the Payhere webview, whilst enabling the conditional visibility settings and hiding the original payment option buttons?
I think you actually revisit the app within the webview (yes, you can view Glide apps within Web Views as @lucas_Pires and I figured out a couple weeks ago!). So, a bit Inception-like, but the visibility conditions should be consistent in the app as well as the app within the webview so if they close down the webview theyād still have the same experience.
Ok cool - I see, so once the app āupdatesā after a couple mins it will reflect the changes to the sheet anyways!
Rightā¦and if you use the webhook, it should be nearly instant (if you have a pro app).
Hey @Robert_Petitto
Quick question
How does the user āunsubscribeā
Just thinking once they have subscribed would be good to have a page in glide where they could manage their subscription and potentially āunsubscribeā
Apologies if I have missed this.
From what I can tell, thereās a link in the receipt email that gets sent to the client that brings up their payment/subscription page:
Thanks
So now Iām thinking if the client manages and cancels how is that fed back into the sheet feeding glide.
Gosh Iām full of questions today. I will have to dig deeper.
Cheers
That would be a separate aspect of the webhook (which I didnāt show). Youād create an integromat module that searches for the customer ID or email address then add a router, if not found, add a row to the sheet, if there is a row, edit the status column of the sheet.
Iāll create a vid momentarily.
Ahh I see, just got to understand how the webhook is triggered via payhere then. Will take a further look at their documentation.
I have to say I like the way you can lock the name and email in payhere, always concerns me that the email address can be tampered with using current glide solution.
Another thing for me is that you cannot create a relationship with āglide tablesā and the āApp: Purchasesā sheet without a work around. The work around does the job but somehow does not feel robust enough for me.
Thanks as always