We are a startup developping our business operations in Paris, France.
Aiming to originate our MVP and meet our next goals, we are now seriously considering adopting Bubble products.
However, we have one last pending point regarding payment API : does Bubble supports Vivawallet ?
Having tried few courses and tested some plugins already, we can find it.
Unfortunately , having consulted the forum, it seems that information related to this specific payment API is quite poor.
As an unexperienced developer, the only reasonable option might be to implement my own API calls (plugin may be challenging…).
I started to follow tutorials and advices to initialize my first API calls, that remain unsuccessful.
Do you where I can find any help for implementation ?
Many thanks !
Each API are different. For example, this one have different authentication process. Do you plan to use the Basic one or the oAuth2 one? This is the first thing to check and choose according to what you want todo. If you plan to only use your own account, you can choose the Basic one. But if you want to let your user authenticate with their own Account, you will need to use oAuth2 process.
If you struggle with API call, consider asking a Bubble Coach to help you
Indeed I spent quite sometime to figure out which one to use. As I aim to sell retail products from the app, the payment part is crucial. This is why I’m starting by that before any further app development.
From my research I understand that oAuth2 is definitely a lot safer but also way more complex to implement.
My first attempts were made on a POST http and following tutorials (How to Connect APIs to Bubble io Tutorial Part 2 - YouTube). I started using Basic as a try but could not initialize a successful call (neither using JSON or Curl).
Do you have an idea of the approximate time it could take to implement with oAuth2 ?
This error is related to auth. Checked a little bit more the auth info in the doc and you need to encode the username and api key into base64 and use Header (Use key in Header instead of basic auth https://www.base64encode.org/ will let you encode both. What I think is that you need to encode both path with colon like username:apikey
The header will be Authorization: Basic ZmJmMWUwOTAtNjVkZS00Yzc1LWI1ODAtZDlkOWJjNDk0YWQyOldEdi1WKw==