The 3rd Party store list a “PayPal and Credit Card Payment Pack”. Is there a link to the author (is it Xojo?) or a place that has more information?
The last time I look at this, it didn’t support subscriptions so we couldn’t use it although they said they are working on it…otherwise it’s very easy to use…
Hello, I created the classes so feel free to private message me with any questions. Our classes allow you to do paypal payments, credit card payments, process instant payment notifications and display payment summaries all in pure Xojo code.
The major question is: how save is it to use?
I mean a good hacker can retrieve a lot of useful information of apps. And that could well be Paypal account data etc…
We process everything by the official PayPal Api documentation. PayPal payments are redirected to the PayPal website and Credit Card payments are processed with API tokens that can be revoked on a per app basis. The PayPal account data stays on the server side in the encrypted xojo binary and is transmitted over a secure connection to PayPal when necessary. All programmers and apps need to be aware of security concerns however that applies to all programming languages and frameworks.
Is there a working PayPal class available somewhere? All classes I found so far use http 1.0 while PayPal demands http 1.1.
You can find my PayPal classes for free at Xojodevspot.com and I can tailor them for free as needed. The source is included so you can learn from as well. You can also find my SimHttp socket class there which is an HTTP 1.1 protocol socket class replacement/add-in for Xojo (Encrypted it is free to use, source is a available for purchase in the XDS Store.), plus all sorts of helpful great stuff. We left the PayPal class tailorable so the developer could implement custom save methods and encryption; that way, the background processing methodology becomes unknown to anyone whom attempts to hack. But all the difficult parts are taken care of such as API and processing methods. Even though we sought to sell the PayPal class originally, we left it open source, under advice from PayPal that; “a static processing library tends to be more vulnerable than a dynamic one, with propriety (“under-the-hood”),” when I inquired to PayPal the best way to provide top protection to the consumer who’d purchase the class. (I added the assumed ‘under the hood’) So unless I could guarantee the consumer 100% compensation to any damages or losses, I wouldn’t dream of selling it under PayPal’s explicit advice. Most developers throw in a “we’re not responsible if once you buy it.” (Bad business)
@Matthew: Thanks a lot. Testing shows an error in DoDirectPayment at
http.Post(domain, 15)The given error is:
You don't have permission to access "http://api-3t.sandbox.paypal.com/nvp" on this server.This is strange as your class uses the HTTPSecureSocket class.
I asumed that this was due to the http version, but some other tests showed that Xojo httpSecureSocket does get access to PayPals sandbox API.
[quote=87218:@Victor Peters]@Matthew: Thanks a lot. Testing shows an error in DoDirectPayment at
http.Post(domain, 15)The given error is:
You don't have permission to access "http://api-3t.sandbox.paypal.com/nvp" on this server.This is strange as your class uses the HTTPSecureSocket class.
I asumed that this was due to the http version, but some other tests showed that Xojo httpSecureSocket does get access to PayPals sandbox API.[/quote]
Did you log into your PayPal sandbox and check the direct payment option? The error is stating that your sandbox is not configured for direct payments 
the difference between http 1.0 and http 1.1 protocol isn’t in the httpsocket xojo socket itself, but how the data is handled, as well as info provided to the server in a request. It would be quite easy for xojo to add the necessary handlers specific to 1.1 (which baffles me as to why it hasn’t already been done since http 1.0 was depreciated in 2002-2003). Id be glad to take one-on-one time with you getting it setup or write a “how to setup PayPal” you.