I need to accept payments in my marketplace via Google Pay and Apple Pay. This is not possible because I use Bubble’s Stripe Plugin which is limited only to bank card payments which is annoying and embarrassing. I’m told I have to use the API Connector instead which is entirely new to me and very daunting.
What I don’t understand is this…Currently, when I take a payment from a bank card via Bubble’s Stripe PlugIn the user is diverted to Stripe’s Checkout. Isn’t this the same Checkout they’ll be diverted to if I use the API connector for payments? If yes, then how are they going to be able to use Google/ApplePay on this checkout? What is it that makes these payment methods available? And what happens if Stripe or Bubble just turn them off again in the future?
I think I need a basic overview of the API Connector and I’ve seen several but these have only been for picking random playing cards, movie previews, TV Listings which is interesting but all seems very different to sending, presumably, secure payment/transaction information. Can anyone point me in a suitable direction for a newbie that doesn’t involve me paying to watch 50+ hours of youtubes to understand it as, I’m told, it only takes 5 minutes to set it up.
To clarify, Stripe’s Checkout is a browser-based payment form that allows users to enter their payment information. When you use the Stripe Plugin in Bubble, the user is indeed redirected to Stripe’s Checkout. However, this is different from using the API Connector, which allows you to integrate Stripe’s payment functionality directly into your Bubble app.
When you use the API Connector, you’re not redirecting the user to Stripe’s Checkout. Instead, you’re using Stripe’s API to handle the payment processing directly within your Bubble app. This is what allows you to use Google Pay and Apple Pay, as these services can be integrated directly into your app using Stripe’s API.
The API Connector is a way to communicate with Stripe’s API directly from your Bubble app, allowing you to send and receive payment information securely. This means you can handle payments within your app without having to redirect the user to an external page.
To answer your question about how users will be able to use Google/Apple Pay on this checkout, it’s because Stripe’s API Connector allows you to use Stripe’s Payment Intents feature. Payment Intents enable you to use payment methods like Google Pay and Apple Pay, which are typically used for one-time payments or subscription payments.
Regarding your concern about Stripe or Bubble turning off these payment methods in the future, it’s unlikely that they would do so. Google Pay and Apple Pay are widely used and popular payment methods. Stripe and Bubble would likely need to provide a reasonable alternative or notification period before discontinuing these features.
For a newbie, I recommend starting with Stripe’s official documentation on the API Connector and Payment Intents. They provide a comprehensive guide on how to set up and integrate these features into your Bubble app.
Additionally, you can check out Stripe’s official tutorials and guides on their website, which cover topics like setting up payment forms, handling payments, and integrating payment methods like Google Pay and Apple Pay.
If you’re still struggling to understand the basics, you can try reaching out to Stripe’s support team or searching for online tutorials and courses that focus specifically on integrating Stripe’s API Connector with Bubble.
On the stripe hosted checkout page they will see those options if they available for their country and you have enabled them from your stripe account dashboard
Enabling them from your stripe account dashboard and whether or not they are supported in the customers country
Stripe will not turn them off, Bubble plugin is just pre-configured api calls and they didn’t set them up in such a way that users can get complete control over their stripe integrations.
For a single API call, when you know how to set them up, yes, it might just take 5 minutes. For learning how the API connector works, learning how Stripe API works and how to read Stripe documentation and being able to troubleshoot issues during the initialization of API calls as well as how to navigate through the Stripe dashboard, plus how to setup webhooks for necessary events, and implementing all of the API calls your setup would require, no, it is not just a 5 minute thing.
You could buy my course which has 40 hours of video which you do not need to watch and are not on youtube, but are put together in a text book style to take you from beginning to end so as to learn everything you would need to know, especially how to understand API connector and stripe documentation so you could then do anything else you need not covered in the course. The course comes with editor access so you could use the API calls in the course apps’ editor and copy/paste them, as well as all of the UI elements with associated workflows/API calls for implementing quickly and easily without ever needing to learn what it is you are doing.
Not really. When using the Stripe Checkout API you are redirecting to the Stripe hosted checkout page, which is recommended over doing things directly in your app because you avoid the potential issues of leaked data, especially for highly sensitive data like user credit card details, so no real reason as a startup to take on the task of keeping all of that sensitive data out of hands of bad actors, and instead make use of Stripe for what they do well, which is financial transactions and storing all of the sensitive data related to them. Let Stripe handle the hard stuff, after all, whether you are doing it in your app or through Stripe hosted checkout page, you are paying Stripe the same fees, so mind as make them work for their money while simultaneously keeping your company and app safe from potential legal liability of leaked financial data.
it is enabling them in the stripe account as well as them being available in the customers country
There is a lot of work to be done for that to happen. Even when using the Stripe hosted checkout page there are best practices to follow to mitigate leaked data when running the API calls themselves.
Can be done without using Payment Intents, and can be done with using the Stripe checkout session API.
Using payment intents adds a lot more work and complexity to your integration than just using the Stripe checkout session api call.
I would recommend using the Stripe Checkout Session API for a newbie
Stripe support team is horrendous. No client of mine or student of mine has ever reported satisfactory experiences. The support center agents are not trained in use of the system and are not developers themselves, they are just call center employees trained in regarding scripts. They do not know how to use the system or how to give best advice on how to use it. An example from my own experience yesterday was that the attempts I made before reaching out to Stripe support were not possible, and Stripe support instructions were to do exactly as I did. When I told them and showcased it didn’t work, the response was
(12:21:02 PM) boston85719@gmail.com: This was the approach I attempted on my own prior to reaching the conclusion it doesn’t work and reaching out to support for guidance.
(12:22:41 PM) Fred: understandable, im not the best developer myself so that was my thought process, what i will do is get in touch with one of our internal devs to make 100% sure that there is a possibility to get that updated. Do you mind if we move this to email
Although the support agents at Stripe will go through the process of attempting to help, the chances of them being able to actually help are slim to none.
Many, many thanks for taking the time out to answer my questions so thoroughly…I really appreciate that.
I’ll also have a good look through Stripe’s own information - somewhere I’ve fallen out of the habit of researching because their “Support” teams often don’t know what Bubble is so it makes integration less likely to be what I’m after.
What you say makes a lot of sense. My concern about Bubble or Stripe turning off GP and AP methods in future came from the fact that it’s apparent that these methods USED to be available via the Bubble PlugIn in the past but isn’t any more and that’s a really surprising decision to make and undermines my faith in the reliability of it all.
Many thanks for all this information. It’s very kind of you to take this time to help me. I’m going through it all line by line so I can learn more what I need to do…
Can I just check…you say the following in answer to my question about how a user will be able to pay with AP or GP…
If this is the case, then does this mean I can leave things as they are and it will work for a User when they’re diverted to Stripe’s Checkout even though they’re there due to my using Bubble’s Stripe Plugin? I’m convinced that I’ve verified and enabled both payment methods in my Stripe Account
and I’m in the UK as are all my users so both payment methods should appear but, for me at least, they don’t. (I don’t use Apple stuff so I get that Apple Pay may not appear but I’d expect Google Pay to) Is there therefore a setting I’ve missed? I’ve seen that others have experienced these payment methods dropping from the Stripe Checkout too so I suspect it’s something deeper.
Thanks again though for your very helpful reply. I’ll get on and study it in depth.
Unfortunately I do not use bubble plugin, so I have no experience with it. However, in my experience using the checkout session api call I didn’t need to do anything for those options to show up on stripe hosted checkout page other than enable them in my stripe dashboard.
Many thanks again. I think I’ve actually resolved this as I’ve now got it to work at checkout via Bubble’s Stripe Plug In. I’ve scribbled out my thoughts on how it now works here…