JohnCoatesOSS / Limitless

Fork of Cydia. Different name to avoid confusion. Goal: Refactor Cydia to make contributions easier. Backport features to Cydia's coding style so they can be submitted for consideration.
GNU General Public License v3.0
155 stars 28 forks source link

Apple Pay Support #44

Open ghost opened 7 years ago

ghost commented 7 years ago

Would it be possible to add Apple Pay support for purchasing tweaks, apps, and themes since Limitless can support the latest APIs or is that restricted by Cydia's backend? I know this would definitely simplify the purchasing process, having cards and info already loaded into Wallet.app, and make it easier/more secure to purchase, using your fingerprint.

Kfeavel commented 7 years ago

I personally haven't looked into the Apple Pay API, but I'm guessing it would require more than just linking the framework and writing the code. I would think that Cydia's backend would have to implement some sort of Apple Pay compatible API, which is doable, but something Saurik would have to do. I can look into it though and see. In the meantime, does PayPal have a nice iOS framework with a UI?

viktorgardart commented 7 years ago

@Kfeavel I've not used it myself but from the repo it looks good? https://github.com/paypal/PayPal-iOS-SDK

Kfeavel commented 7 years ago

@viktorgardart That looks so much better than anything Cydia has by default. I think we could incorporate that somehow.

JohnCoates commented 7 years ago

I've used PayPal's iOS SDK and it's great. Unfortunately we can't integrate it with the Cydia store. We might be able to integrate an open payment platform to make it easier for repos to accept payments though!

ghost commented 7 years ago

@JohnCoates what qualifies as an open payment platform? Something like Stripe (which also includes support for Apple Pay)?

JohnCoates commented 7 years ago

@roonieone yeah. Definitely Stripe, PayPal, etc. The question is how do we arrange so a repo can specify payment information that Limitless can use to process a payment? Also, how will we make it easy for the repo to know when a user has purchased a package?

kirb commented 7 years ago

Psst

I like that concept, but there has to be a server somewhere in there. And the repo needs to check somewhere it can verify the purchase token with. At which point it stops becoming as "open" as we'd want – just a slightly better way of doing the same thing.

JohnCoates commented 7 years ago

@kirb Since you're familiar with the playing field, what are the benefits of Chariz over Stripe or PayPal? What are the downsides? Can support for Chariz be integrated into repos easily?

kirb commented 7 years ago

Well, I'm providing a gateway service much like Cydia Store. Payments are still through PayPal (Stripe and some others are coming; awaiting some business-related things to be sorted first). We host the downloads, so the repo just needs to redirect to us; and the depiction should have either a buy link or our purchase iframe.

andrewwiik commented 7 years ago

To add onto this if limitless would allow overriding where the purchase button directs too this would make it feel more integrated.

kirb commented 7 years ago

The button is put there via the JS api, which only cydia.saurik.com is allowed to access. The only thing the app does to support paid packages is show their package cell in blue and enable the page loading spinner. Would love to see that api opened up but the security implications will need to be investigated (permission prompts?) – it supports quite a lot from typical nav controller/bar operations to listing installed apps to triggering a package/repo installation.

On Mon., 5 Dec. 2016, 9:54 am Andrew Wiik, notifications@github.com wrote:

To add onto this if limitless would allow overriding where the purchase button directs too this would make it feel more integrated.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/JohnCoatesOSS/Limitless/issues/44#issuecomment-264740269, or mute the thread https://github.com/notifications/unsubscribe-auth/AAvMvcEp_zP7Z2B215zV_gZbRhQAo1Oxks5rE0uigaJpZM4LADps .

-- Adam Demasi HASHBANG Productions hbang.com.au

andrewwiik commented 7 years ago

I know how the button works, I asked Saurik if he would allow other urls to change that sort of stuff and he said no :/ Why not allow a link to be put in the control for the package and have cydia use that over the js api if it exists in the package control file

JohnCoates commented 7 years ago

I just started looking into this, and I feel that Stripe might be the right choice. They offer a product that's geared for exactly this, called Relay. screen shot 2016-12-04 at 3 48 41 pm

A repo could list a product identifier along with the package, and with that they can attach a secret piece of metadata that contains the download URL. Then we can process the payment and retrieve the download URL.

andrewwiik commented 7 years ago

Stripe also offers a great deal through the github student developer pack

Sent from my iPhone

On Dec 4, 2016, at 6:52 PM, John Coates notifications@github.com wrote:

I just started looking into this, and I feel that Stripe might be the right choice. They offer a product that's geared for exactly this, called Relay.

It looks like a repo could list a product identifier along with the package, and with that they can attach a secret piece of metadata that contains the download URL. Then we can process the payment and retrieve the download URL.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.