Only Appke store pay should work with Applepay, other build (dmg) should have the traditional link.

I have applied with Benevity/Apple Pay to get us approved. They should respond in a few days.

@Popolechien any news on this? Should we move that to 3.5.0?

@Popolechien We need an update here before implementing the feature.

No news. I have resubmitted, made a note to ping them on Monday 23rd, but seeing as a bunch of contact links are wrong/deprecated/broken I am cautiously optimistic.

From Apple:

Hi team,
We are excited to let you know that your organization has been approved to accept donations with Apple Pay.
You can now submit your iOS app to the App Store for review or deploy your website’s integration of Apple Pay. If you’re in the process of integrating Apple Pay into your app or website, make sure to review the guidelines and resources on the Apple Developer website.
If you have any questions on implementing Apple Pay, you can talk to other developers and Apple engineers on the Apple Developer forums or contact us.
Best Regards,
Apple Developer Relations

@BPerlakiH You need anything else to move forward with the code?

Thank you @kelson42, I think initially it should be good, if anything arise while implementing it, I will let you know.

I've found the following things we need:
https://causeshelp.benevity.org/hc/en-us/articles/360001149486-Benevity-and-Apple-Pay

To accept donations with Apple Pay, your organization will need the following:
Payment provider
Apple Developer Program membership
Approval to accept donations with Apple Pay
Apple Pay implemented in your app or website

My question is do we have a payment provider?
I do see on the website DonorBox, which is backed up by Stripe, so maybe we could use Stripe (it’s on Apple’s list for us).

My understanding is that once we have payment provider they will give us a CSR file we can use to create our Apple Payment Certificate here:
https://developer.apple.com/account/resources/certificates/list
as described in Apple's doc:
https://developer.apple.com/help/account/create-certificates/create-a-certificate-signing-request

@BPerlakiH Yes, we have Stripe and we should use it. Can you handle the details directly with @Popolechien please?

@kelson42 I managed to put together the initial code part of this, with a very basic payment sheet, that Apple provides.
We can create any type of payment request with a specific total (eg. 15USD), I am not sure yet, if it should reflect the full form from the website support page? So that the user can edit the amount, choose a specific cause to support etc.
I am not yet sure about recurring payments (monthly / annually) but will have a look.

Ok so I looked on Stripe to generate a CSR certificate and that clearly is above my skillset. @rgaudin can you please look into it?

@BPerlakiH I've created the CSR on Stripe and requested the certificate from Apple using it and received the certificate which I uploaded to Stripe as well. Both seem happy. Do you need anything else?

Thank you very much.
Q: should it reflect the full form from the website support page ?

A: not really, but potential donors should be given the choice of making this a one-time or monthly recurring donation (annual is never used, and donations will likely be flagged as coming from iOS so the priority and comment parts can also be ignored). I don't know how much leeway you have (or how much space is available before the screen gets crowded), but 10/34/custom amount is a decent range of choices.

Let me know what is doable within a reasonable amount of work (e.g. if it is a full day to implement a distinct recurring donation panel, then never mind and just make it a radio button for people to chose).

Thank you, I am looking into it what's the best way to achieve it.

@BPerlakiH Do you have gain clarity here about the path to follow?

@kelson42 Yes, we need the user input in terms of what amount he/she wants to donate.
I managed to put together a UI for it, based on the form from the website. So it's possible to select from predefined amounts, and custom one as well. For simplicity the multi currency is only added to the custom amount, but I suppose that should be OK.

https://github.com/user-attachments/assets/70284c82-e23d-4d22-aef1-d6dff1291081
https://github.com/user-attachments/assets/ecb52232-e1ab-4f0b-ac82-969be23e0ab1
https://github.com/user-attachments/assets/427261c3-f898-4717-9b67-084c030c02c4

Thanks a lot @BPerlakiH. Two questions:

• Is there a default currency (e.g. the user's?) If not then make it USD
• Can you please make the little heart red rather than transparent so it is more visible? See Fixed: The donation popup does not look well in tablet. kiwix-android#4012 for what I mean (I suspect we poached it from Signal, if that's any help)

Great ; I think the feature is here and we should work on making it a bit more appealing. A sentence (from @Popolechien, telling users why we ask for donations, etc), an icon maybe (love-receiving Kiwix?) and probably an Apple Pay logo as we want users to know that they wont need to take out their credit card to make a donation.
I believe regular users are not aware that we were required to use Apple Pay to add the feature to the app.
If we only accept Apple Pay, that seems important as well.

I'd recommend sticking to the Signal playbook and have a minimalist text. Here is what they have

(the Read more link adds a little popup with a bit more text but nothing much else except for a bigger heart - I do not think we need to go that route.

So for the header text here is my suggestion

No ads, no tracking 
Kiwix is a non-profit funded by people like you. If you enjoy Kiwix and find it useful, make a donation and help keep it fun. 

Note: as in the Signal banner the first line "No ads, no tracking" should be in a bigger font.

Latest Signal is a bit different. First of all, the donate menu is inside the Settings.
Then the process is two-steps with a card first and then the new version of what you shared.
It's not that minimalist anymore as there's the profile picture, accompanied with an icon (support level I think but not sure) and then when selecting an amount, there's an amount-related emoji animation

I'm with you on following what others with more resources and success have (probably) thought-through and done but that should not prevent us from making our own decisions

Thank you for the feedback.
@Popolechien:

Is there a default currency (e.g. the user's?) If not then make it USD

We can add as many currencies as we want (eg. Signal is using all possible currencies of the world), the limitation will come not from the development process, but rather from the payment provider, they might not accept all of them.
Yes, there's an easy way to get the user's local (language and) currency, so it's possible to default to that one.
Please remember, this brings up another layer we need to take care of, which is the currency rate, which ideally should be updated from an online source. Since USD/EUR/CHF are rather close by value to each other, we could default to values such as 10,15 etc without using a data source for currency rates. If we go full scale, other currencies will be rather volatile in this matter, so we would need to re-calculate those values, as an example from Signal, displaying values in IDR:

On the plus side this is convenient for the user, on the other hand the whole section of donations will become dependent on "being online", and not just the final "Apple Pay" button.

@rgaudin Thanks for the suggestion with Signal, I did checked their iOS app as well, and that looks good. In terms of making it look nice, I think the iOS part is where the nice look and feel will end. On macOS the system provided components aren't that nice, to be honest... There's no real comparison, as there's no donation section for Signal macOS app, but Apple Pay will work equally good on macOS.

Additionally from what I can see on Signal, is that there's also a minimum amount for one time donation defined as well (USD 3$).

@BPerlakiH I think the $3 minimum is to discourage fraudulent transactions IIRC so we might as well implement it unless it's bein implemented by default.

As for currency let's default to EUR/USD only based on user location, with USD being the "real" default (that is, for non-EU users) and no bothering with FOREX adjustments.

We should go now for a minimal version, with only USD and no custom design. It has to be clean and working bit nothing more. Improvements and refinements ideas should be tracked in new issues. It's important now to quickly move on the PR.

Remark: It's important his feature to have no impact on custom apps