Hi
I have a question about In app Provisioning for Apple Pay. I'm a developer in company which makes application for one of banks. They want to have ability to add cards to Wallet by their app not by Wallet application. I know which functions and documentation i need to use but I have a problem with testing it.
We are third party developer, have seperate teams, bank also has 3 apps for their testing environments. Bank sign agreements with Apple so they could have entitlements to check integration. And that is a question. Is there any change to check our implementation before checking it in production app?
I've seen sandbox account feature:
https://developer.apple.com/apple-pay/sandbox-testing/
but I can' open In App provisioning window without entitlements. In Apple documentation we have statement that Apple is giving this entitlement only for production applications. So how to test it and check implementation before getting to production or without "mocking" application as production (changing id).
Apple Pay
RSS for tagDiscuss how to integrate Apple Pay into your app for secure and convenient payments.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
**Hi Apple Developer Community,
I’m currently integrating Apple Pay across multiple merchants for my e-commerce solution, and I’ve run into a significant challenge. Apple enforces a limit of 100 Merchant IDs per Developer Account, which is creating a bottleneck for my project.
My Questions:
1- Is there a way to increase the limit of Merchant IDs on a Developer Account?
2- Has anyone faced a similar challenge and found a workaround to handle integrations with more than 100 merchants?
3- Are there any plans from Apple to lift or adjust this restriction for businesses working with high volumes of merchants?
I’d appreciate any guidance, advice, or information from those who’ve encountered and resolved this issue.
Thank you for your help!
Topic:
App & System Services
SubTopic:
Apple Pay
Tags:
Apple Pay on the Web
App Store Connect
Apple Pay
I am writing to express my deep dissatisfaction with a recent experience involving your services. I have discovered that I have been charged twice for the same product or service, which I find unacceptable. Additionally, I have not received the necessary support to resolve this issue, and the product or service in question does not function as it should.
The treatment I have received has been neglectful and far below the standards I expect from a company that prides itself on providing quality service. This situation has not only shaken my confidence in your services but has also caused significant frustration as a customer.
I demand an immediate resolution to this issue, including a refund for the duplicate charge and assurance that the purchased product or service will work as promised. If I do not receive a satisfactory response, I will be forced to take further action to protect my rights as a consumer.
I look forward to your prompt response to resolve this matter.
I forgot renew Apple Developer account, just 2 days
Now I did not see the button to renew account
Please help me
Topic:
App & System Services
SubTopic:
Apple Pay
All the listed Discover cards for Sanbox testing listed here are expired, i.e. expiry date is 11/2024.
https://developer.apple.com/apple-pay/sandbox-testing/
Are there any new cards?
Thanks
Topic:
App & System Services
SubTopic:
Apple Pay
I've implemented Push Provisioning, but am having trouble testing it.
When I try to add a payment pass with my activationData, encryptedPassData, and ephemeralPublicKey, I see the "Add Card to Apple Pay" screen, but then when I click "Add Card", I get a "Could Not Add Card" message.
When I inspect the error from didFinishAddingPaymentPass, it reads "The operation couldn’t be completed. (PKPassKitErrorDomain error 2.)".
Is this error PKPassKitError.Code.unsupportedVersionError? What does this error means?
Additional context:
We use cordova-apple-wallet to generate certificates and add payment pass.
Maybe this is a strange question but I think it's better to ask this before trying it and see what happens; if we use the dpan or mpan of a recurring payment to make a charge on a date other than the one shown to the final customer, could the payment be made without any problem by the bank or financial institutions involved? Naturally I understand that this would mainly cause great anger to the customer and of course if this were the case this could be explained in the billing agreement, but the doubt is mainly based on whether it is possible to use a dpan/mpan for a payment other than that of the original subscription.
Hi everyone,
I’m developing an iOS app for fundraising, similar to platforms like JustGiving. The app will allow multiple charities to register and receive donations directly into their Stripe accounts using Stripe Connect.
Given Apple’s strict guidelines, I want to make sure I address the following:
How can I ensure compliance with App Store guidelines for apps that facilitate donations to multiple charities?
Are there specific requirements for verifying charities or disclosing fundraising information within the app?
Any tips for providing sufficient documentation during the App Store submission to avoid delays or rejection?
I’d really appreciate advice from anyone who has experience with similar projects or navigating Apple’s review process for apps involving fundraising and third-party payments.
Thanks in advance!
Topic:
App & System Services
SubTopic:
Apple Pay
Hello, I have purchased an Apple Developer Program membership, and the payment was successfully completed. However, I am unable to access my developer account. When I try to log in to the developer section, it still prompts me to make a payment as if the purchase was not completed.
Can you please assist me in resolving this issue?
I am somewhat of a beginner in mobile app development. I have some questions about IAP and commissions. One of my clients has a website that basically acts as the middle man which connects the trainers and participants. Basically, the trainers pay my client a subscription fee and they can list the kind of trainings they have to offer (ex. cardio, weight lifting, ...etc.). These trainings can be one-to-one, one-to-many, or one-to-few depending on the trainers. When the participants see something that they like, they would make a payment directly to the trainers via the website. To save time, we will probably do some kind of webview app. Having said all these, my questions are as follows,
As far as the IAP is concerned, can the payments between the trainers and the participants use third party payment method and ONLY the subscription fee from the trainers to the client use the storeKit/Apple IAP plugin?
If the answer to the question above is Yes (i.e. using Apple IAP for subscription only but use a third party payment for the transactions between the trainers and the participants), does it mean that the commissions ONLY apply on the subscription fees and NOT the payments between the trainers and the participants?
If the answer to Question 1 is No (i.e. ALL the payments have to go through Apple IAP), the commissions would apply to both the payments between the trainers and the participants and the monthly subscription payments, right? In this case though, to my understanding, when using the Apple IAP plugin, essentially, all the payments go to Apple temporarily. After taking out the commissions, the payments would be released to the bank account on file with the App Store within 45 days of the last day of the fiscal month in which the transaction was completed. Am I correct? And if so, as far as the business model on the App is concerned, my client would collect the money released from Apple and then distribute the money to the appropriate trainers. Am I correct?
Context:
Our company distributes the same app under multiple brands/flavors using three different App Store Connect accounts. The app supports Apple Pay in 17 markets, allowing users to switch between markets and pay in their chosen market. To handle payments, we currently create separate Apple Pay Merchant IDs and certificates for each market within each of the three accounts.
This results in:
3 Merchant IDs per market (one for each account)
17 markets supported, requiring 51 certificates to be created and maintained
Key constraints:
All the apps cannot be unified under a single App Store Connect account due to certain requirements.
Question:
Is there a way to simplify this process by consolidating the merchant IDs or certificates across accounts while maintaining the current structure? For example, is there a way to share Merchant IDs across multiple accounts, or is there an alternative approach to reduce the administrative overhead of managing 51 certificates?
Any guidance or best practices for optimizing Apple Pay setups in such multi-account, multi-market scenarios would be highly appreciated!
Topic:
App & System Services
SubTopic:
Apple Pay
Hi everyone,
I am working on creating an NFC-enabled Apple Wallet pass but have been unable to get the NFC functionality to work. While the pass itself adds to Wallet without issues, the NFC feature does not activate.
Here’s a summary of what I’ve done:
1. Developer Setup:
Registered a Pass Type ID in my Apple Developer account.
Generated and installed the Pass Type ID certificate.
Installed the latest WWDR certificate.
2. Pass JSON Configuration:
My pass.json file includes the following NFC configuration:
"nfc": {
"message": "Tap to unlock door",
"encryptionPublicKey": "MY_ENCRYPTION_PUBLIC_KEY",
"payload": "encrypted_nfc_payload"
}
3. Testing Results:
When the pass includes the nfc field, it adds to Wallet but NFC does not work.
If I remove the nfc field, the pass works fine (minus NFC, of course).
What I Need Help With:
1. A step-by-step guide for correctly implementing NFC in Wallet passes, including details about encryption, key generation, and any additional setup steps.
2. Information on whether there are specific device or iOS version requirements for NFC-enabled passes.
If there are any prerequisites or specific configurations I might be missing, please let me know. I’d really appreciate detailed guidance or resources that could help resolve this issue.
Thank you!
Topic:
App & System Services
SubTopic:
Apple Pay
Tags:
Mobile Core Services
Wallet
Apple Pay
Core NFC
Hi,
We are using Apple VAS and ECP2 certified NFC readers. What process will we need to follow to issue NFC-based keys so that we can provide an access control use case?
Any help in this regard will be much appreciated.
Thanks,
Aweliv
Hi there,
We build and operate apps for several PBS stations, and we're considering adding in-app donations with Apple Pay:
https://developer.apple.com/apple-pay/nonprofits/
I'm curious if any examples of this functionality in a live app. We'd love to take a look, and get a better idea of use-cases before we tackle that project. (Seems like it would be a very nice upgrade.)
Cheers,
Kevin
I have an Apple subscription with a 2-week introductory offer and a 3-month promotional offer code. There are 2 subscription plans:
1-month subscription
12-month subscription
For the 1-month plan, my promotional offer code is "Monthly_Free," and for the 12-month plan, my promotional offer code is "Yearly_Free." However, when users try to enter the respective promo codes for the 1-month or 12-month plans, they receive the following error:
"Offer not available. Your account is not eligible for this offer. You can still subscribe at the regular plan price."
This works fine in the sandbox account, where I can use the promo codes as many times as needed, switching between the 1-month and 12-month plans easily. What could be the issue here?
I'm trying to upload my app with Tap to Pay on iPhone functionality. However, I'm getting error message "Profile doesn't include com.apple.developer.proximity-reader.payment.acceptance entitlement." I've confirmed many times that I have the distribution profile with this capability. Any idea what might be the issue? The development environment works perfectly.
Hey Everyone, i am trying the credentials for AMEX and Discover from here:
https://developer.apple.com/apple-pay/sandbox-testing/
The problem is, none of the AMEX and Discover is working with my CyberSource integration, not sure why? the same VISA and Master is working good
Topic:
App & System Services
SubTopic:
Apple Pay
Earlier this year implemented saving event tickets to Apple Wallet (and Google Wallet, which was painful by comparison!), as an optional alternative to recipients leaving the QR Codes in email or printing them.
Scanning barcodes on entry is done using camera on phones (either iPhone or Android). This is a somewhat pressured situation with lots of people needing scans in quite a short period of time. I do not do this myself but I do get feedback.
it was reported to me that Apple Wallet barcodes are significantly harder to scan accurately than those in Google Wallet. They think that is because the Apple QR Codes are quite a bit smaller (and presumably harder, therefore, to get focussed properly). They do work, it just takes longer to get a successful scan. This doesn’t seem to be anything I can control, and there seems to be plenty of space to make them bigger, even on my iPhone mini. These aren’t terribly dense barcodes; I imagine they would be harder still if they were. I also guess specialised barcode readers might do better, but we don’t have that luxury.
I’d appreciate it if they could be bigger when displayed in Apple Wallet, or at least to have that as an option.
We are implementing Apple Pay and Wallet features in our app and using mocked data for testing purposes. Specifically, in the status(completion:) method of PKIssuerProvisioningExtensionHandler, we return:
passEntriesAvailable: true,
remotePassEntriesAvailable: true,
requiresAuthentication: true,
In the passEntries(completion:) method, we provide mocked data for our card.
The issue is that the app icon inconsistently appears under the "From Apps on Your iPhone" section in the Wallet app. Sometimes it shows up as expected, but other times it does not.
On recent occasions, when the app is selected and mocked authorization is paased, the behavior includes a system error 'Cannot Add Card' even though we provided status that indicates that the app has available cards for Wallet.
For reference:
The app uses two bundle IDs supporting in-app provisioning and
PNO Pass Metadata has not been configured yet.
Could you help clarify the potential reasons for this inconsistent behavior?
When attempting to make a payment via Apple Pay in the card payment form, an error occurs, but there is no information about the error.
Here, you can watch a video with detailed information about what happened: https://drive.google.com/drive/folders/1bco64RH3UPcJTqjW6muIRDr1gW7lnJ6d?usp=sharing