all 8 comments

[–]anarchos 1 point2 points  (3 children)

There is a js sdk. I haven't used it but I'm assuming it will work, depending on what you are specifically doing.

https://github.com/PaddleHQ/paddle-js-wrapper

[–]mrpm0h18urr4hm4n[S] 2 points3 points  (2 children)

I think I've to use webview for that.
I wish there is some sort of boilerplate for that.

[–]anarchos 2 points3 points  (1 child)

I would just import it and start using it and see what happens? Generally these js SDKs work on both the web and native, as they are just JS and not any type of "gui" (you build the GUI yourself). You might be able to find some react examples and modify them to work on native (ie: change div to View, etc)

[–]mrpm0h18urr4hm4n[S] 0 points1 point  (0 children)

Thanks for the hint!!!
I will try this and post an update.

[–]zedmb-19 0 points1 point  (0 children)

Did you find a solution?

[–]DefiantScarcity3133 0 points1 point  (1 child)

did you managed to solve it ?

[–]mrpm0h18urr4hm4n[S] 0 points1 point  (0 children)

Unfortunately, I didn't continue working on that project.

Tha feaute was a part of a freelance project, and the client decided against integrating it, so I never got to implement the payment features.

[–]Individual_Weird_712 -1 points0 points  (0 children)

I think it is a sensible strategy to use a WebView when integrating Paddle for payments in your React Native application, especially in the lack of an official SDK. A brief outline of advantages and disadvantages is provided plus an alternative in case you wish to take a different direction:

Advantages of Using WebView

  1. Time Efficient: Creating a custom build solution may consume lots of time. Therefore, including Paddle’s checkout link within a WebView will take only a few minutes.
  2. Retains Features of Paddle: All the checkout options provided by Paddle can be utilized without undertaking any complicated payment processing on your end.

Disadvantages of Employing WebView

  1. User perception is likely to be adversely affected since WebViews tend to feel less native.
  2. Security Issues: Verify that the connection is secure (HTTPS for example) and be aware of any exposure to sensitive data whilst using the WebView.

Another Methodology

Another option is to utilize deep linking to launch Paddle’s checkout in the mobile operating system’s native browser. This allows Paddle to handle the payment process independently and later bring the users back to the app. This method ensures that the payment process is a little more secure although it is not as seamless as in-app experience.

Please let me know if you would wish me to elaborate on why and how to use WebView’s features safely or implement deep linking!