Apple Pay

RSS for tag

Provide a fast, easy, and secure way for users to buy goods and services in your app or on your website using Apple Pay.

Posts under Apple Pay tag

200 Posts

Post

Replies

Boosts

Views

Activity

Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues
Hi, You're here because you've had issues with your implementation of In-App Provisioning Extensions for Apple Pay In-App Provisioning or In-App Verification. To prevent sending sensitive credentials in plain text, create a new report in Feedback Assistant to share the details requested below with the appropriate log profiles installed. Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues While troubleshooting Apple Pay In-App Provisioning or In-App Verification, it is essential that the issuer is able to collect logs on their device and check those logs for error message. This is also essential when reporting issues to Apple. To gather the required data for your own debugging as well as reporting issues, please perform the following steps on the test device: Install the Apple Pay and Wallet profiles on your iOS or watchOS device. If the issue occurs on Mac, continue to Step 2. Reproduce the issue and make a note of the timestamp when the issue occurred, while optionally capturing screenshots or video. Gather a sysdiagnose on the same iOS or watchOS device, or on macOS. Create a Feedback Assistant report with the following information: The bundle IDs App bundle ID Non-UI app extension bundle ID (if applicable) UI app extension bundle ID (if applicable) The serial number of the device. For iOS and watchOS: Open Settings > General > About > Serial Number (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > Serial Number. The SEID (Secure Element Identifier) of the device, represented as a HEX encoded string. For iOS and watchOS: Open Settings > General > About > SEID (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > System Report > NVMExpress > Serial Number. The sysdiagnose gathered after reproducing the issue. The timestamp (including timezone) of when the issue was reproduced. The type of provisioning failure (e.g., error at Terms & Conditions, error when adding a card, etc.) The issuer/network/country of the provisioned card (e.g., Mastercard – US) Last 4 digits of the FPAN Last 4 digits of the DPAN (if available) Was this test initiated from the Issuer App? (e.g., yes or no) The type of environment (e.g., sandbox or production) Screenshots or videos of errors and unexpected behaviors (optional). Important: From the logs gathered above, you should be able to determine the cause of the failure from PassbookUIService, PassKit or PassKitCore, and by filtering for your SEID or bundle ID of your app or app extensions in the Console app. Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Apple Pay client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
0
0
5.3k
Jan ’26
Guidelines 3.1.1 and 3.1.3(c): enterprise-only access on iOS
Hello, I’m looking for guidance on how App Review Guidelines 3.1.1 and 3.1.3(c) apply to an enterprise learning platform with the following access model: Organizations purchase access for their employees through a business-to-business agreement. Employees sign in to the iOS app using accounts provided by their organization. They do not purchase access or pay within the app. Individual users may access the platform separately through the web or Android, but the iOS app is intended only for employees covered by an organization’s agreement. Would this model generally qualify for the enterprise services exception under Guideline 3.1.3(c)? If so, what information or configuration would help App Review verify that iOS access is limited to eligible organization-funded users? I understand that each app is reviewed on its specific implementation. I’d appreciate any guidance or relevant experience from developers who have dealt with a similar setup. Thank you!
0
0
30
2d
Can I identify the card network, such as Cartes Bancaires, from decrypted Apple Pay paymentData?
We are a merchant based in Europe and work with multiple PSPs, some of which do not support the Cartes Bancaires network. After decrypting the Apple Pay paymentData, is it possible to identify the card network or card brand, such as Cartes Bancaires, before submitting the transaction for authorization? If so, which field contains this information, and is Cartes Bancaires returned as a distinct value? For co-badged cards, does the decrypted payload indicate all available networks or only the network selected for the transaction? We would like to use this information to route transactions to a PSP that supports the relevant network, helping us improve authorization rates and reduce processing costs. Thank you.
0
0
159
3d
I can not pay for my developer account
I have tried over the past couple of days with multiple different cards and they have all come back with payment denied. It is the last step for the developer account to be complete so I can start converting my app to iPhone and iPad. Has anyone had this happen? I put in an email to support and also sat on hold for an hour and 40 minutes before the call just hung up yesterday. Help really stuck here.
0
0
24
3d
Sandbox startSession returns HTML 500 after ~10s for all registered merchants (platform integrator)
We're an Apple Pay platform integrator (Web Merchant Registration API). Since some point between 27 Oct and 12 Nov 2026, merchant validation against the sandbox gateway fails for every merchant we have registered. Request: POST https://apple-pay-gateway-cert.apple.com/paymentservices/startSession mTLS with our Platform Integrator Identity certificate, body: {"merchantIdentifier":"<registered id>","displayName":"Test","initiative":"web","initiativeContext":"<registered domain>"} Response: after ~8–10s, an HTML page "500 Internal Server Error" (footer "Apple"), not the usual JSON error. With curl --max-time 60 it still returns the 500 at ~10.7s, so the timeout is on Apple's side. What we've checked: Fails under two separate platform integrator identities, from our servers and from a developer laptop with plain curl (no proxy). curl timing: TLS handshake complete in 0.23s, TTFB ~9s. Network/IPv6/OCSP/SSL inspection don't apply. The same request with an unregistered merchantIdentifier returns the expected JSON 417 (mass_enablement_authorization_denied) in <0.5s. registerMerchant, unregisterMerchant and GET /paymentservices/merchant/{id} all work normally; merchant details show the expected domains and encryptTo hash. A newly registered merchant with a single valid domain also gets the 500. Domain verification file is served correctly and its pspId matches. Identity and payment processing certificates are valid and OCSP reports "good". Production gateway responds normally (fast JSON 4xx for unregistered merchants). The same setup returned valid sessions in under a second until at least 27 Oct 2026. Is anyone else seeing sandbox startSession failures, or can Apple check whether something has changed on the sandbox gateway?
0
0
78
1w
Domain Verification for Web Apple Pay - expired/revoked?
Our Apple Pay merchant domain verification appears to have expired or been revoked without any notification. We discovered the issue only after Apple Pay on the Web stopped working and we saw errors during the merchant session call. Is there a way to determine: When the merchant domain verification became invalid? What event caused it to expire or be revoked? Whether Apple provides notifications when the verification status changes? Whether there is an API or recommended monitoring method to proactively check merchant domain verification status? We would like to understand how this is controlled so we can detect the issue before it impacts Apple Pay on the Web.
0
0
43
1w
How to determine if my app's credit card has been added to apply pay of my device
Im trying to implement add to Apple Pay feature in my app. I have an issuer bank's credit card as an existing feature. Now question is, say its added successfully already, I relaunch my app, how to tell if already added to Apple Pay? I have made some reads, and asked AIs, but I can't seem to get a clear answer. Passkit's primaryAccountIdentifier - if use this, how will our backend store this? I mean, I don't think its ideal approach for mobile app to be responsible for calling backend api. deviceAccountNumberSuffix - what if my app have other cards that can be added to Apple Pay and has same suffix. Then seems broken flow.
1
0
1k
3w
Apple Pay merchant domain verification fails despite valid TLS configuration
We are unable to verify our Apple Pay merchant domains. Apple Developer Portal returns: “Domain verification failed. Review your TLS Certificate configuration to confirm that the certificate is accessible and a supported TLS Cipher Suite is used.” We have confirmed that the verification endpoints are publicly accessible, return HTTP 200, and support TLS 1.2/1.3 with valid certificates and supported cipher suites. The domains are behind Cloudflare. However, when verification is triggered, we do not see an HTTP request from Apple in our Cloudflare request logs. Has anyone experienced a similar issue with Apple Pay merchant domain verification, especially with domains behind Cloudflare? We have also submitted a report through Feedback Assistant.
1
0
549
3w
Apple Pay on the Web sheet fails with PKPaymentAuthorizationStateFatalError after successful merchant validation (PROD trust policy)
Environment macOS 26.5.1 (Build 25F80) Safari 26.5 Apple Pay JS API version 8 Using https://applepay.cdn-apple.com/jsapi/v1/apple-pay-sdk.js Reproduces on the staging website (Does not reproduce on the production website with non sandbox account) Signed into a Sandbox Tester Apple ID, with a test credit card registered exactly per Apple Pay Sandbox Testing — this is the only card in Wallet on the laptop Merchant validation is performed by our staging backend against our real (non-sandbox) merchant identity/certificate — i.e. a sandbox tester card being evaluated against a staging merchant session, which per the sandbox testing documentation is the expected/supported setup for testing on a live site without a separate merchant sandbox environment Summary After completeMerchantValidation() succeeds and the merchant session is accepted, the payment sheet still terminates with PKPaymentAuthorizationStateFatalError a few hundred milliseconds later, right after the native side logs a second "Evaluating merchant session using PROD trust policy." for the same session. The user sees "Payment failed" and the sheet closes. This happens on the very first attempt, with no user interaction beyond tapping the Apple Pay button — no shipping address is even selected before the failure. Since the sandbox tester card + production merchant session combination is the setup the sandbox testing guide describes, we'd expect the sheet to proceed to onpaymentauthorized (Apple's sandbox docs describe payments as being processed as $0 test transactions in this mode) rather than fail natively before that stage is ever reached. Steps to reproduce Visit an item page with an Apple Pay button. Tap the Apple Pay button to open the payment sheet. The sheet presents normally; no interaction with shipping address or payment method is required for the failure to occur. Within ~1 second, the sheet dismisses and displays a "Payment failed" error state. Minimal reproduction of the JS side const session = new ApplePaySession(8, { countryCode: 'US', currencyCode: 'USD', supportedNetworks: ['visa', 'masterCard', 'amex', 'discover'], merchantCapabilities: ['supports3DS'], total: { label: 'Merchant', amount: '10.00' }, }); session.onvalidatemerchant = async () => { const merchantSession = await validateMerchantOnServer(); // succeeds session.completeMerchantValidation(merchantSession); // accepted — see log below }; session.onpaymentmethodselected = () => { session.completePaymentMethodSelection({ newTotal: { label: 'Merchant', amount: '10.00' }, }); }; session.oncancel = event => console.log('cancelled', event); session.begin(); We reproduced this with both our full checkout implementation and this stripped-down request object (no shipping contact required, no line items) — same failure either way, which rules out anything about our order/line-item data. What we expected The sheet to proceed to the biometric authorization step and dispatch onpaymentauthorized once the user confirms. What actually happens The sheet fails immediately with a PKPaymentAuthorizationStateFatalError transition, even though every JS-side completion call (completeMerchantValidation, the payment-method selection) succeeded and returned PKPaymentAuthorizationStatusSuccess. System log (captured via log stream --info --debug --predicate 'process == "Safari" OR process == "passd" OR process == "com.apple.PassKit.PaymentAuthorizationUIExtension"') 21:50:41.544 PaymentCoordinator::beginPaymentSession() -> 1 21:50:41.570 Received prepareWithPaymentRequest: <private> 21:50:42.297 PaymentCoordinator::validateMerchant() 21:50:42.563 PaymentCoordinator::completeMerchantValidation() 21:50:42.564 Received merchant session update with status:PKPaymentAuthorizationStatusSuccess session:<private> 21:50:42.564 Evaluating merchant session using PROD trust policy. <- 1st occurrence, passes 21:50:42.572 PaymentCoordinator::didSelectPaymentMethod() 21:50:42.572 PaymentCoordinator::completePaymentMethodSelection() 21:50:42.653 Evaluating merchant session using PROD trust policy. <- 2nd occurrence 21:50:42.656 State machine change state from ClientCallback to PrepareTransactionDetails with param: <private> 21:50:43.391 Task Completed: <private> 21:50:43.393 State machine change state from PrepareTransactionDetails to PKPaymentAuthorizationStateFatalError with param: <private> 21:50:43.393 Error Payment failed with fatal error <private> 21:50:45.130 PaymentCoordinator::didCancelPaymentSession() The first "Evaluating merchant session using PROD trust policy." line passes (the flow continues to didSelectPaymentMethod). The second occurrence is immediately followed by Task Completed and then the FatalError transition, which suggests PassKit re-validates the merchant session's trust a second time right before PrepareTransactionDetails, and that second check is what's rejecting the session — even though the identical session object was accepted moments earlier at completeMerchantValidation(). What we've tried / ruled out Confirmed every JS completion method (completeMerchantValidation, completePaymentMethodSelection) is called and returns success — no 30-second timeout, no missing completion call, no thrown exception on our side. Reproduced with a minimal, hardcoded ApplePayPaymentRequest (fixed $10.00 total, no shipping fields) — rules out anything about our real order/line-item/sales-tax data. Reproduced on the main branch and independently on our staging deployment running unmodified code — rules out anything specific to our recent frontend changes. The <private> redaction in the system log prevents us from seeing what specifically fails during the second trust evaluation. Confirmed the sandbox tester card and its registration follow the sandbox testing guide exactly — it's the only card on the device, and no other Wallet cards are involved. Question What does PassKit's second "Evaluating merchant session using PROD trust policy" check (immediately before PrepareTransactionDetails) actually validate, beyond what's already checked at completeMerchantValidation() time? Is a sandbox tester card being evaluated against a production merchant session expected to pass this second check, or does sandbox testing per the linked guide require something additional on the merchant/session side (e.g. a specific field on the merchant session, or a specific environment value) that our backend isn't setting? Is there a way to get an unredacted reason for the rejection — e.g. via a private-data-enabled log profile or another diagnostic — since the redacted system log alone doesn't surface one?
3
0
3.3k
3w
Pre-requisites for Production Go-Live (PSP/Payment Processor)
We are a Payment Service Provider (PSP)/Payment Processor/Payment Gateway and have completed the Apple Pay integration and successfully tested transactions in the Sandbox environment. We are now planning to move the integration to Production and would like to understand the prerequisites, certification requirements and process involved in enabling Apple Pay for our merchants. Could you please clarify the following: Production Enablement: What are the mandatory prerequisites for a PSP/Payment Processor/Payment Gateway to move from Sandbox to Production? Certification: Is formal certification or approval from Apple required for the Payment Processor before Go-Live? Certificates: Are separate Production Payment Processing and Merchant Identity Certificates required? Merchant Onboarding: What is the process for onboarding and enabling individual merchants under our PSP/Payment Processor setup? Any provisions for Bulk On-boarding? Testing & Validation: Are there any mandatory test scenarios or validations required before Production enablement? Production Access: What approvals, configurations or access enablements are required from Apple's end? Go-Live Process: What is the recommended sequence of activities and expected timeline for Production activation?
0
0
81
3w
No App Store Connect API endpoint to associate a Bundle ID with an Apple Pay Merchant ID
We manage provisioning for a large number of App IDs across multiple apps via CI, using the App Store Connect API (not session-based Spaceship/Xcode auth). Capability management works well end to end for everything we've tried — Push Notifications, App Groups, Associated Domains, Data Protection, etc. can all be created, updated, and deleted via POST/PATCH/DELETE on /v1/bundleIdCapabilities. Apple Pay is the one exception. We can enable the Apple Pay capability itself via the API the same way as anything else, but there's no way to associate that capability with a specific Merchant ID. /v1/merchantIds exists as its own resource, but nothing in the bundleIdCapabilities or bundleIds schema links to it — no relationship, no include, no dedicated endpoint. In practice this means every new Apple Pay-enabled App ID we provision needs someone to go into the Developer Portal by hand (Identifiers → App ID → Capabilities → Apple Pay → select Merchant ID) before the generated provisioning profile will actually build — otherwise Xcode fails with errors like "doesn't include the Apple Pay capability" / "doesn't support the Merchant ID". Every other capability we use is fully scriptable; this is the one manual step left in an otherwise automated pipeline. Has anyone found a documented (or undocumented) way to do this via the API? If this is a confirmed gap rather than something we're missing, I've filed it as FB24414090 — if you've hit the same thing, adding your own Feedback number to a report on the same gap seems to be one of the few things that actually helps get traction internally, so feel free to reference this thread if you file one too.
2
0
800
3w
Apple Pay on the Web: merchant-hosted payment page, Register Merchant API, eligibility checks, and who decrypts the token
We are an acquirer and PSP with our own payment gateway. Merchants can either: Use an Apple Pay payment page hosted by us, or Host their own payment page and submit payment data to us via server-to-server APIs. We are currently implementing Apple Pay on the Web using the Platform Integrator model. The acquirer-hosted payment page flow is clear to us, but we have a few questions regarding merchant-hosted payment pages. Our current understanding (please correct us if any of this is incorrect) We register each merchant using the Web Merchant Registration API as a Platform Integrator, with a unique partnerInternalMerchantIdentifier. Merchants do not have their own Apple Developer accounts. For merchant-hosted payment pages, the merchant's checkout domain is provided in domainNames. The domain verification file is downloaded from our Apple Developer account (Platform Integrator account), and the merchant hosts that file under the /.well-known/ path on their domain. The merchant registration created through the Web Merchant Registration API is then used for Apple Pay eligibility checks and merchant validation. Questions: Domain registration For a merchant-hosted payment page, is it correct to register the merchant's domain against that merchant's partnerInternalMerchantIdentifier registration? Verification file When onboarding multiple merchants: Is the same domain association file used across all merchant domains? Or is a unique verification file generated per merchant registration? Eligibility checks and Apple Pay button The "Supporting Apple Pay on Third-Party Browsers" documentation (Scenario 3) suggests that a payment service provider may provide a JavaScript library that loads apple-pay-sdk.js for merchants. For merchant-hosted pages, is it supported and recommended for the PSP/platform integrator to provide a thin wrapper library around: canMakePayments() applePayCapabilities() Apple Pay button rendering Session creation Or is Apple’s preferred approach that the merchant's checkout page interacts directly with Apple Pay JS APIs? PSP/acquirer decrypts the payment token If the PSP/acquirer is responsible for token decryption, we understand that encryptTo should be set to the Platform Integrator identifier. For merchant-hosted payment pages, are there any additional requirements beyond domain registration and merchant validation? Merchant decrypts the payment token We would also like to support a model where the merchant decrypts Apple Pay tokens directly. In that case, our understanding is that encryptTo must reference the merchant's identifier rather than the Platform Integrator identifier. Is that understanding correct, and are there any additional onboarding or registration requirements for that model? Merchant validation For merchant-hosted checkout pages, what is the expected implementation pattern for onvalidatemerchant? Specifically: Should the merchant's frontend send the validationURL to the PSP/platform integrator backend, which then performs merchant validation with Apple and returns the merchant session? Or is a different flow expected when using the Platform Integrator model? Any clarification or guidance would be greatly appreciated. Thank you.
1
0
165
4w
Apple Pay on the Web: recurringPaymentRequest tokens can't be decrypted by the payment processor
Our payment processor can't decrypt the Apple Pay payment tokens for some of our recurring payment (continuous payment authority) set-ups. These are Apple Pay on the Web payments where the request includes a recurringPaymentRequest, to set up the agreement without taking a payment. Our payment processor says the decryption fails on their side before the payment is authorised, and they asked us to raise it with Apple. Our one-off Apple Pay payments with the same merchant ID decrypt normally as do a number of our recurring payments. We have reviewed the decryption errors section of troubleshooting-apple-pay-payment-processing-issues and haven't found a cause that explains why only the recurring set-ups fail. We have the transaction identifiers and timestamps for the affected payments, and we can share them privately. Could you confirm whether these tokens were encrypted with our merchant's payment processing certificate, and whether recurring or merchant-token set-ups are handled differently? The code-level support form asked us to post here first because we don't have an Xcode project. If Feedback Assistant would be better for this, we're happy to file a report there and reply with the Feedback ID. Thank you
0
0
64
Oct ’26
Apple Pay sign-in pop-up disappears quickly on iPhone 15 in Safari
im developing apple pay in safari and im using iPhone 15 & ios version 26.5 to test. im testing the scenario, when user is logged off apple account and try apple pay, there should be a pop up message, giving user two options: Cancel & Sign In. when im testing on mac, the pop up window works fine with title 'Apple Pay requires icloud' - Sign in your apple account to set up apple pay - cancel & sign in however, when im testing on my iphone, the pop up window vanish very quickly in like 1 second. im wondering how to fix the issue so that user can be redirect to sign in their account.
1
0
328
Oct ’26
Apple Developer Program Membership Still Pending After Payment & Support Not Responding
Hi everyone, I’m hoping someone here can help or advise me on what to do next. I enrolled in the Apple Developer Program and completed the payment on October 1, 2026. However, my account is still showing Pending, and the Developer portal is still asking me to purchase the membership again. My details are: Enrollment ID: X2YRV8DQ57 Order ID: W1988568006 Payment date: October 1, 2026 Current status: Pending Developer portal still shows: “Purchase your membership” I have already contacted Apple Developer Support and sent them all the required details, including the payment information and screenshots, but I am still waiting for a resolution. The frustrating part is that Apple Developer Support is not responding to my follow-up emails, and when I contact Apple customer service by phone, they are unable to help because they apparently do not have access to the Apple Developer enrollment/payment system. I am currently completely blocked because I need the Developer Program membership to continue with App Store Connect and TestFlight testing, but I also do not want to pay for the membership a second time when I have already completed the payment. Has anyone experienced this recently? If so: How long did it take for Apple to activate your account? Was there any specific Developer Support team you contacted? Is there any way to escalate an enrollment/payment issue? Should I continue waiting, or is there another process I should follow? Any guidance would be greatly appreciated. I have already provided Apple with my order and enrollment information, but I have not received any meaningful update yet. Thanks in advance.
2
1
233
Oct ’26
In-App-Verification - PassKit
I am working on In-App-Verification. I am able to add my cards manually in the Apple Wallet Sandbox. I am getting the option to Verify using App. When I click on the Verify Button, I am able to redirect to my Testflight App. But when I use the API PKPassLibrary().pass(withPassTypeIdentifier: passTypeIdentifier, serialNumber: serialNumber) its not returning me the expected Pass. It is infact giving an empty result The entitlements which I already have added are: com.apple.developer.pass-type-identifiers com.apple.developer.payment-pass-provisioning So I have below questions: Do I need to do something else for PassKit API's to work? Is it even possible to test In-App-Verification in the TestFlight App using sandbox Wallet? Is it possible to redirect user to debug and enterprise builds also as currently the redirection from Apple Wallet is not working for debug and enterprise builds? The PassKit API which I indicated earlier is working in debug build when I sideload from Xcode. But since deeplink from Wallet does not work for debug builds, I am not able to proceed with testing. What will be behavior in App-Store build production environment without using sandbox, by using real cards? Will it work there?
0
0
76
Oct ’26
401 error registering sandbox domain with Web Merchant Registration API
Hi, We recently applied for the Web Merchant Registration API and created our platform integrator ID. I am trying to register a domain in sandbox with the API: POST https://apple-pay-gateway-cert.apple.com/paymentservices/registerMerchant Content-Type: application/json { "domainNames": ["<URL>"], "partnerInternalMerchantIdentifier": "<merchant_id>", "partnerMerchantName": "<merchant_name>", "encryptTo": "<platform_integrator_id>" } Client certificate is provided via curl --cert/--key; the TLS 1.3 handshake completes successfully — the server requests the client cert, our Certificate + CERT verify are accepted, and the connection is established. But the response is { "statusMessage": "Payment Services Exception Unauthorized", "statusCode": "401" } How do I go about debugging this?
0
0
409
Oct ’26
Sandbox Visa test card refused at provisioning (403) on supervised iPhones only; Mastercard fails at eligibility (500) everywhere
We test Apple Pay in the sandbox on supervised iPhones in a device lab (Apple Configurator supervision, no MDM enrollment, no SIM, iOS 26.x). Since late September two of the test cards from the Sandbox Testing page no longer add to Wallet. Discover test cards still add fine on the same devices and accounts. Filed as FB24994276 (Visa) and FB24994258 (Mastercard), with device logs and timestamps. Visa 4622 9431 2318 9285 (FB24994276), only on our lab devices: eligibility → 412 → TSM sync → 200, "received eligibility status: 1" terms shown and accepted provision → HTTP 403 → PKProvisioningErrorDomain Code=3 → "Invalid Card" Same result on two different lab iPhones, including one signed in to a brand-new sandbox account. The same new account and the same card add successfully on an unsupervised iPhone on a home network (iOS 18.2.1). Neither side sends location data. Mastercard 5204 2452 5046 0049 (FB24994258), on every device we tried, lab and home, iOS 18.2.1 and 26.x: eligibility → 412 → TSM sync → retry → HTTP 500 → PKProvisioningErrorDomain Code=5 Questions: What does the 403 at the provisioning step mean for the Visa card? Does supervision, the iOS version, our network egress, or the fact that our devices re-provision cards every test session play a role? Is the Mastercard sandbox environment currently broken, or is there a Mastercard test card that works? Happy to capture a sysdiagnose with the Wallet logging profile if that helps.
0
0
152
Sep ’26
In App Provisioning PKErrorHTTPResponseStatusCodeKey=500
Hello, we are developing in app provisioning of our American Express network cards. After clicking add to apple wallet in our app, I launch the PKAddPaymentPassViewController and click next. It loads for a few seconds and then I get: [<private>] ProvisioningOperationComposer: Step '<private>' failed with error Error Domain=PKProvisioningErrorDomain Code=5 UserInfo={PKErrorHTTPResponseStatusCodeKey=500} Does anyone have any insight on what this error means?
5
1
1.5k
Sep ’26
Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues
Hi, You're here because you've had issues with your implementation of In-App Provisioning Extensions for Apple Pay In-App Provisioning or In-App Verification. To prevent sending sensitive credentials in plain text, create a new report in Feedback Assistant to share the details requested below with the appropriate log profiles installed. Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues While troubleshooting Apple Pay In-App Provisioning or In-App Verification, it is essential that the issuer is able to collect logs on their device and check those logs for error message. This is also essential when reporting issues to Apple. To gather the required data for your own debugging as well as reporting issues, please perform the following steps on the test device: Install the Apple Pay and Wallet profiles on your iOS or watchOS device. If the issue occurs on Mac, continue to Step 2. Reproduce the issue and make a note of the timestamp when the issue occurred, while optionally capturing screenshots or video. Gather a sysdiagnose on the same iOS or watchOS device, or on macOS. Create a Feedback Assistant report with the following information: The bundle IDs App bundle ID Non-UI app extension bundle ID (if applicable) UI app extension bundle ID (if applicable) The serial number of the device. For iOS and watchOS: Open Settings > General > About > Serial Number (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > Serial Number. The SEID (Secure Element Identifier) of the device, represented as a HEX encoded string. For iOS and watchOS: Open Settings > General > About > SEID (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > System Report > NVMExpress > Serial Number. The sysdiagnose gathered after reproducing the issue. The timestamp (including timezone) of when the issue was reproduced. The type of provisioning failure (e.g., error at Terms & Conditions, error when adding a card, etc.) The issuer/network/country of the provisioned card (e.g., Mastercard – US) Last 4 digits of the FPAN Last 4 digits of the DPAN (if available) Was this test initiated from the Issuer App? (e.g., yes or no) The type of environment (e.g., sandbox or production) Screenshots or videos of errors and unexpected behaviors (optional). Important: From the logs gathered above, you should be able to determine the cause of the failure from PassbookUIService, PassKit or PassKitCore, and by filtering for your SEID or bundle ID of your app or app extensions in the Console app. Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Apple Pay client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
Replies
0
Boosts
0
Views
5.3k
Activity
Jan ’26
Guidelines 3.1.1 and 3.1.3(c): enterprise-only access on iOS
Hello, I’m looking for guidance on how App Review Guidelines 3.1.1 and 3.1.3(c) apply to an enterprise learning platform with the following access model: Organizations purchase access for their employees through a business-to-business agreement. Employees sign in to the iOS app using accounts provided by their organization. They do not purchase access or pay within the app. Individual users may access the platform separately through the web or Android, but the iOS app is intended only for employees covered by an organization’s agreement. Would this model generally qualify for the enterprise services exception under Guideline 3.1.3(c)? If so, what information or configuration would help App Review verify that iOS access is limited to eligible organization-funded users? I understand that each app is reviewed on its specific implementation. I’d appreciate any guidance or relevant experience from developers who have dealt with a similar setup. Thank you!
Replies
0
Boosts
0
Views
30
Activity
2d
Can I identify the card network, such as Cartes Bancaires, from decrypted Apple Pay paymentData?
We are a merchant based in Europe and work with multiple PSPs, some of which do not support the Cartes Bancaires network. After decrypting the Apple Pay paymentData, is it possible to identify the card network or card brand, such as Cartes Bancaires, before submitting the transaction for authorization? If so, which field contains this information, and is Cartes Bancaires returned as a distinct value? For co-badged cards, does the decrypted payload indicate all available networks or only the network selected for the transaction? We would like to use this information to route transactions to a PSP that supports the relevant network, helping us improve authorization rates and reduce processing costs. Thank you.
Replies
0
Boosts
0
Views
159
Activity
3d
I can not pay for my developer account
I have tried over the past couple of days with multiple different cards and they have all come back with payment denied. It is the last step for the developer account to be complete so I can start converting my app to iPhone and iPad. Has anyone had this happen? I put in an email to support and also sat on hold for an hour and 40 minutes before the call just hung up yesterday. Help really stuck here.
Replies
0
Boosts
0
Views
24
Activity
3d
Sandbox startSession returns HTML 500 after ~10s for all registered merchants (platform integrator)
We're an Apple Pay platform integrator (Web Merchant Registration API). Since some point between 27 Oct and 12 Nov 2026, merchant validation against the sandbox gateway fails for every merchant we have registered. Request: POST https://apple-pay-gateway-cert.apple.com/paymentservices/startSession mTLS with our Platform Integrator Identity certificate, body: {"merchantIdentifier":"<registered id>","displayName":"Test","initiative":"web","initiativeContext":"<registered domain>"} Response: after ~8–10s, an HTML page "500 Internal Server Error" (footer "Apple"), not the usual JSON error. With curl --max-time 60 it still returns the 500 at ~10.7s, so the timeout is on Apple's side. What we've checked: Fails under two separate platform integrator identities, from our servers and from a developer laptop with plain curl (no proxy). curl timing: TLS handshake complete in 0.23s, TTFB ~9s. Network/IPv6/OCSP/SSL inspection don't apply. The same request with an unregistered merchantIdentifier returns the expected JSON 417 (mass_enablement_authorization_denied) in <0.5s. registerMerchant, unregisterMerchant and GET /paymentservices/merchant/{id} all work normally; merchant details show the expected domains and encryptTo hash. A newly registered merchant with a single valid domain also gets the 500. Domain verification file is served correctly and its pspId matches. Identity and payment processing certificates are valid and OCSP reports "good". Production gateway responds normally (fast JSON 4xx for unregistered merchants). The same setup returned valid sessions in under a second until at least 27 Oct 2026. Is anyone else seeing sandbox startSession failures, or can Apple check whether something has changed on the sandbox gateway?
Replies
0
Boosts
0
Views
78
Activity
1w
Domain Verification for Web Apple Pay - expired/revoked?
Our Apple Pay merchant domain verification appears to have expired or been revoked without any notification. We discovered the issue only after Apple Pay on the Web stopped working and we saw errors during the merchant session call. Is there a way to determine: When the merchant domain verification became invalid? What event caused it to expire or be revoked? Whether Apple provides notifications when the verification status changes? Whether there is an API or recommended monitoring method to proactively check merchant domain verification status? We would like to understand how this is controlled so we can detect the issue before it impacts Apple Pay on the Web.
Replies
0
Boosts
0
Views
43
Activity
1w
How to determine if my app's credit card has been added to apply pay of my device
Im trying to implement add to Apple Pay feature in my app. I have an issuer bank's credit card as an existing feature. Now question is, say its added successfully already, I relaunch my app, how to tell if already added to Apple Pay? I have made some reads, and asked AIs, but I can't seem to get a clear answer. Passkit's primaryAccountIdentifier - if use this, how will our backend store this? I mean, I don't think its ideal approach for mobile app to be responsible for calling backend api. deviceAccountNumberSuffix - what if my app have other cards that can be added to Apple Pay and has same suffix. Then seems broken flow.
Replies
1
Boosts
0
Views
1k
Activity
3w
Apple Pay merchant domain verification fails despite valid TLS configuration
We are unable to verify our Apple Pay merchant domains. Apple Developer Portal returns: “Domain verification failed. Review your TLS Certificate configuration to confirm that the certificate is accessible and a supported TLS Cipher Suite is used.” We have confirmed that the verification endpoints are publicly accessible, return HTTP 200, and support TLS 1.2/1.3 with valid certificates and supported cipher suites. The domains are behind Cloudflare. However, when verification is triggered, we do not see an HTTP request from Apple in our Cloudflare request logs. Has anyone experienced a similar issue with Apple Pay merchant domain verification, especially with domains behind Cloudflare? We have also submitted a report through Feedback Assistant.
Replies
1
Boosts
0
Views
549
Activity
3w
Apple Pay on the Web sheet fails with PKPaymentAuthorizationStateFatalError after successful merchant validation (PROD trust policy)
Environment macOS 26.5.1 (Build 25F80) Safari 26.5 Apple Pay JS API version 8 Using https://applepay.cdn-apple.com/jsapi/v1/apple-pay-sdk.js Reproduces on the staging website (Does not reproduce on the production website with non sandbox account) Signed into a Sandbox Tester Apple ID, with a test credit card registered exactly per Apple Pay Sandbox Testing — this is the only card in Wallet on the laptop Merchant validation is performed by our staging backend against our real (non-sandbox) merchant identity/certificate — i.e. a sandbox tester card being evaluated against a staging merchant session, which per the sandbox testing documentation is the expected/supported setup for testing on a live site without a separate merchant sandbox environment Summary After completeMerchantValidation() succeeds and the merchant session is accepted, the payment sheet still terminates with PKPaymentAuthorizationStateFatalError a few hundred milliseconds later, right after the native side logs a second "Evaluating merchant session using PROD trust policy." for the same session. The user sees "Payment failed" and the sheet closes. This happens on the very first attempt, with no user interaction beyond tapping the Apple Pay button — no shipping address is even selected before the failure. Since the sandbox tester card + production merchant session combination is the setup the sandbox testing guide describes, we'd expect the sheet to proceed to onpaymentauthorized (Apple's sandbox docs describe payments as being processed as $0 test transactions in this mode) rather than fail natively before that stage is ever reached. Steps to reproduce Visit an item page with an Apple Pay button. Tap the Apple Pay button to open the payment sheet. The sheet presents normally; no interaction with shipping address or payment method is required for the failure to occur. Within ~1 second, the sheet dismisses and displays a "Payment failed" error state. Minimal reproduction of the JS side const session = new ApplePaySession(8, { countryCode: 'US', currencyCode: 'USD', supportedNetworks: ['visa', 'masterCard', 'amex', 'discover'], merchantCapabilities: ['supports3DS'], total: { label: 'Merchant', amount: '10.00' }, }); session.onvalidatemerchant = async () => { const merchantSession = await validateMerchantOnServer(); // succeeds session.completeMerchantValidation(merchantSession); // accepted — see log below }; session.onpaymentmethodselected = () => { session.completePaymentMethodSelection({ newTotal: { label: 'Merchant', amount: '10.00' }, }); }; session.oncancel = event => console.log('cancelled', event); session.begin(); We reproduced this with both our full checkout implementation and this stripped-down request object (no shipping contact required, no line items) — same failure either way, which rules out anything about our order/line-item data. What we expected The sheet to proceed to the biometric authorization step and dispatch onpaymentauthorized once the user confirms. What actually happens The sheet fails immediately with a PKPaymentAuthorizationStateFatalError transition, even though every JS-side completion call (completeMerchantValidation, the payment-method selection) succeeded and returned PKPaymentAuthorizationStatusSuccess. System log (captured via log stream --info --debug --predicate 'process == "Safari" OR process == "passd" OR process == "com.apple.PassKit.PaymentAuthorizationUIExtension"') 21:50:41.544 PaymentCoordinator::beginPaymentSession() -> 1 21:50:41.570 Received prepareWithPaymentRequest: <private> 21:50:42.297 PaymentCoordinator::validateMerchant() 21:50:42.563 PaymentCoordinator::completeMerchantValidation() 21:50:42.564 Received merchant session update with status:PKPaymentAuthorizationStatusSuccess session:<private> 21:50:42.564 Evaluating merchant session using PROD trust policy. <- 1st occurrence, passes 21:50:42.572 PaymentCoordinator::didSelectPaymentMethod() 21:50:42.572 PaymentCoordinator::completePaymentMethodSelection() 21:50:42.653 Evaluating merchant session using PROD trust policy. <- 2nd occurrence 21:50:42.656 State machine change state from ClientCallback to PrepareTransactionDetails with param: <private> 21:50:43.391 Task Completed: <private> 21:50:43.393 State machine change state from PrepareTransactionDetails to PKPaymentAuthorizationStateFatalError with param: <private> 21:50:43.393 Error Payment failed with fatal error <private> 21:50:45.130 PaymentCoordinator::didCancelPaymentSession() The first "Evaluating merchant session using PROD trust policy." line passes (the flow continues to didSelectPaymentMethod). The second occurrence is immediately followed by Task Completed and then the FatalError transition, which suggests PassKit re-validates the merchant session's trust a second time right before PrepareTransactionDetails, and that second check is what's rejecting the session — even though the identical session object was accepted moments earlier at completeMerchantValidation(). What we've tried / ruled out Confirmed every JS completion method (completeMerchantValidation, completePaymentMethodSelection) is called and returns success — no 30-second timeout, no missing completion call, no thrown exception on our side. Reproduced with a minimal, hardcoded ApplePayPaymentRequest (fixed $10.00 total, no shipping fields) — rules out anything about our real order/line-item/sales-tax data. Reproduced on the main branch and independently on our staging deployment running unmodified code — rules out anything specific to our recent frontend changes. The <private> redaction in the system log prevents us from seeing what specifically fails during the second trust evaluation. Confirmed the sandbox tester card and its registration follow the sandbox testing guide exactly — it's the only card on the device, and no other Wallet cards are involved. Question What does PassKit's second "Evaluating merchant session using PROD trust policy" check (immediately before PrepareTransactionDetails) actually validate, beyond what's already checked at completeMerchantValidation() time? Is a sandbox tester card being evaluated against a production merchant session expected to pass this second check, or does sandbox testing per the linked guide require something additional on the merchant/session side (e.g. a specific field on the merchant session, or a specific environment value) that our backend isn't setting? Is there a way to get an unredacted reason for the rejection — e.g. via a private-data-enabled log profile or another diagnostic — since the redacted system log alone doesn't surface one?
Replies
3
Boosts
0
Views
3.3k
Activity
3w
Pre-requisites for Production Go-Live (PSP/Payment Processor)
We are a Payment Service Provider (PSP)/Payment Processor/Payment Gateway and have completed the Apple Pay integration and successfully tested transactions in the Sandbox environment. We are now planning to move the integration to Production and would like to understand the prerequisites, certification requirements and process involved in enabling Apple Pay for our merchants. Could you please clarify the following: Production Enablement: What are the mandatory prerequisites for a PSP/Payment Processor/Payment Gateway to move from Sandbox to Production? Certification: Is formal certification or approval from Apple required for the Payment Processor before Go-Live? Certificates: Are separate Production Payment Processing and Merchant Identity Certificates required? Merchant Onboarding: What is the process for onboarding and enabling individual merchants under our PSP/Payment Processor setup? Any provisions for Bulk On-boarding? Testing & Validation: Are there any mandatory test scenarios or validations required before Production enablement? Production Access: What approvals, configurations or access enablements are required from Apple's end? Go-Live Process: What is the recommended sequence of activities and expected timeline for Production activation?
Replies
0
Boosts
0
Views
81
Activity
3w
No App Store Connect API endpoint to associate a Bundle ID with an Apple Pay Merchant ID
We manage provisioning for a large number of App IDs across multiple apps via CI, using the App Store Connect API (not session-based Spaceship/Xcode auth). Capability management works well end to end for everything we've tried — Push Notifications, App Groups, Associated Domains, Data Protection, etc. can all be created, updated, and deleted via POST/PATCH/DELETE on /v1/bundleIdCapabilities. Apple Pay is the one exception. We can enable the Apple Pay capability itself via the API the same way as anything else, but there's no way to associate that capability with a specific Merchant ID. /v1/merchantIds exists as its own resource, but nothing in the bundleIdCapabilities or bundleIds schema links to it — no relationship, no include, no dedicated endpoint. In practice this means every new Apple Pay-enabled App ID we provision needs someone to go into the Developer Portal by hand (Identifiers → App ID → Capabilities → Apple Pay → select Merchant ID) before the generated provisioning profile will actually build — otherwise Xcode fails with errors like "doesn't include the Apple Pay capability" / "doesn't support the Merchant ID". Every other capability we use is fully scriptable; this is the one manual step left in an otherwise automated pipeline. Has anyone found a documented (or undocumented) way to do this via the API? If this is a confirmed gap rather than something we're missing, I've filed it as FB24414090 — if you've hit the same thing, adding your own Feedback number to a report on the same gap seems to be one of the few things that actually helps get traction internally, so feel free to reference this thread if you file one too.
Replies
2
Boosts
0
Views
800
Activity
3w
Apple Pay on the Web: merchant-hosted payment page, Register Merchant API, eligibility checks, and who decrypts the token
We are an acquirer and PSP with our own payment gateway. Merchants can either: Use an Apple Pay payment page hosted by us, or Host their own payment page and submit payment data to us via server-to-server APIs. We are currently implementing Apple Pay on the Web using the Platform Integrator model. The acquirer-hosted payment page flow is clear to us, but we have a few questions regarding merchant-hosted payment pages. Our current understanding (please correct us if any of this is incorrect) We register each merchant using the Web Merchant Registration API as a Platform Integrator, with a unique partnerInternalMerchantIdentifier. Merchants do not have their own Apple Developer accounts. For merchant-hosted payment pages, the merchant's checkout domain is provided in domainNames. The domain verification file is downloaded from our Apple Developer account (Platform Integrator account), and the merchant hosts that file under the /.well-known/ path on their domain. The merchant registration created through the Web Merchant Registration API is then used for Apple Pay eligibility checks and merchant validation. Questions: Domain registration For a merchant-hosted payment page, is it correct to register the merchant's domain against that merchant's partnerInternalMerchantIdentifier registration? Verification file When onboarding multiple merchants: Is the same domain association file used across all merchant domains? Or is a unique verification file generated per merchant registration? Eligibility checks and Apple Pay button The "Supporting Apple Pay on Third-Party Browsers" documentation (Scenario 3) suggests that a payment service provider may provide a JavaScript library that loads apple-pay-sdk.js for merchants. For merchant-hosted pages, is it supported and recommended for the PSP/platform integrator to provide a thin wrapper library around: canMakePayments() applePayCapabilities() Apple Pay button rendering Session creation Or is Apple’s preferred approach that the merchant's checkout page interacts directly with Apple Pay JS APIs? PSP/acquirer decrypts the payment token If the PSP/acquirer is responsible for token decryption, we understand that encryptTo should be set to the Platform Integrator identifier. For merchant-hosted payment pages, are there any additional requirements beyond domain registration and merchant validation? Merchant decrypts the payment token We would also like to support a model where the merchant decrypts Apple Pay tokens directly. In that case, our understanding is that encryptTo must reference the merchant's identifier rather than the Platform Integrator identifier. Is that understanding correct, and are there any additional onboarding or registration requirements for that model? Merchant validation For merchant-hosted checkout pages, what is the expected implementation pattern for onvalidatemerchant? Specifically: Should the merchant's frontend send the validationURL to the PSP/platform integrator backend, which then performs merchant validation with Apple and returns the merchant session? Or is a different flow expected when using the Platform Integrator model? Any clarification or guidance would be greatly appreciated. Thank you.
Replies
1
Boosts
0
Views
165
Activity
4w
Apple Pay on the Web: recurringPaymentRequest tokens can't be decrypted by the payment processor
Our payment processor can't decrypt the Apple Pay payment tokens for some of our recurring payment (continuous payment authority) set-ups. These are Apple Pay on the Web payments where the request includes a recurringPaymentRequest, to set up the agreement without taking a payment. Our payment processor says the decryption fails on their side before the payment is authorised, and they asked us to raise it with Apple. Our one-off Apple Pay payments with the same merchant ID decrypt normally as do a number of our recurring payments. We have reviewed the decryption errors section of troubleshooting-apple-pay-payment-processing-issues and haven't found a cause that explains why only the recurring set-ups fail. We have the transaction identifiers and timestamps for the affected payments, and we can share them privately. Could you confirm whether these tokens were encrypted with our merchant's payment processing certificate, and whether recurring or merchant-token set-ups are handled differently? The code-level support form asked us to post here first because we don't have an Xcode project. If Feedback Assistant would be better for this, we're happy to file a report there and reply with the Feedback ID. Thank you
Replies
0
Boosts
0
Views
64
Activity
Oct ’26
Apple Pay sign-in pop-up disappears quickly on iPhone 15 in Safari
im developing apple pay in safari and im using iPhone 15 & ios version 26.5 to test. im testing the scenario, when user is logged off apple account and try apple pay, there should be a pop up message, giving user two options: Cancel & Sign In. when im testing on mac, the pop up window works fine with title 'Apple Pay requires icloud' - Sign in your apple account to set up apple pay - cancel & sign in however, when im testing on my iphone, the pop up window vanish very quickly in like 1 second. im wondering how to fix the issue so that user can be redirect to sign in their account.
Replies
1
Boosts
0
Views
328
Activity
Oct ’26
Apple Developer Program Membership Still Pending After Payment & Support Not Responding
Hi everyone, I’m hoping someone here can help or advise me on what to do next. I enrolled in the Apple Developer Program and completed the payment on October 1, 2026. However, my account is still showing Pending, and the Developer portal is still asking me to purchase the membership again. My details are: Enrollment ID: X2YRV8DQ57 Order ID: W1988568006 Payment date: October 1, 2026 Current status: Pending Developer portal still shows: “Purchase your membership” I have already contacted Apple Developer Support and sent them all the required details, including the payment information and screenshots, but I am still waiting for a resolution. The frustrating part is that Apple Developer Support is not responding to my follow-up emails, and when I contact Apple customer service by phone, they are unable to help because they apparently do not have access to the Apple Developer enrollment/payment system. I am currently completely blocked because I need the Developer Program membership to continue with App Store Connect and TestFlight testing, but I also do not want to pay for the membership a second time when I have already completed the payment. Has anyone experienced this recently? If so: How long did it take for Apple to activate your account? Was there any specific Developer Support team you contacted? Is there any way to escalate an enrollment/payment issue? Should I continue waiting, or is there another process I should follow? Any guidance would be greatly appreciated. I have already provided Apple with my order and enrollment information, but I have not received any meaningful update yet. Thanks in advance.
Replies
2
Boosts
1
Views
233
Activity
Oct ’26
Apple Pay for Partners
Apple Pay for Partners brings together the latest news, features, and fraud protection information for issuers, merchants, and platforms — all designed to support your integration and help you deliver the payment experience customers know and trust. Available in English only. Explore Apple Pay for Partners >
Replies
0
Boosts
0
Views
191
Activity
Oct ’26
In-App-Verification - PassKit
I am working on In-App-Verification. I am able to add my cards manually in the Apple Wallet Sandbox. I am getting the option to Verify using App. When I click on the Verify Button, I am able to redirect to my Testflight App. But when I use the API PKPassLibrary().pass(withPassTypeIdentifier: passTypeIdentifier, serialNumber: serialNumber) its not returning me the expected Pass. It is infact giving an empty result The entitlements which I already have added are: com.apple.developer.pass-type-identifiers com.apple.developer.payment-pass-provisioning So I have below questions: Do I need to do something else for PassKit API's to work? Is it even possible to test In-App-Verification in the TestFlight App using sandbox Wallet? Is it possible to redirect user to debug and enterprise builds also as currently the redirection from Apple Wallet is not working for debug and enterprise builds? The PassKit API which I indicated earlier is working in debug build when I sideload from Xcode. But since deeplink from Wallet does not work for debug builds, I am not able to proceed with testing. What will be behavior in App-Store build production environment without using sandbox, by using real cards? Will it work there?
Replies
0
Boosts
0
Views
76
Activity
Oct ’26
401 error registering sandbox domain with Web Merchant Registration API
Hi, We recently applied for the Web Merchant Registration API and created our platform integrator ID. I am trying to register a domain in sandbox with the API: POST https://apple-pay-gateway-cert.apple.com/paymentservices/registerMerchant Content-Type: application/json { "domainNames": ["<URL>"], "partnerInternalMerchantIdentifier": "<merchant_id>", "partnerMerchantName": "<merchant_name>", "encryptTo": "<platform_integrator_id>" } Client certificate is provided via curl --cert/--key; the TLS 1.3 handshake completes successfully — the server requests the client cert, our Certificate + CERT verify are accepted, and the connection is established. But the response is { "statusMessage": "Payment Services Exception Unauthorized", "statusCode": "401" } How do I go about debugging this?
Replies
0
Boosts
0
Views
409
Activity
Oct ’26
Sandbox Visa test card refused at provisioning (403) on supervised iPhones only; Mastercard fails at eligibility (500) everywhere
We test Apple Pay in the sandbox on supervised iPhones in a device lab (Apple Configurator supervision, no MDM enrollment, no SIM, iOS 26.x). Since late September two of the test cards from the Sandbox Testing page no longer add to Wallet. Discover test cards still add fine on the same devices and accounts. Filed as FB24994276 (Visa) and FB24994258 (Mastercard), with device logs and timestamps. Visa 4622 9431 2318 9285 (FB24994276), only on our lab devices: eligibility → 412 → TSM sync → 200, "received eligibility status: 1" terms shown and accepted provision → HTTP 403 → PKProvisioningErrorDomain Code=3 → "Invalid Card" Same result on two different lab iPhones, including one signed in to a brand-new sandbox account. The same new account and the same card add successfully on an unsupervised iPhone on a home network (iOS 18.2.1). Neither side sends location data. Mastercard 5204 2452 5046 0049 (FB24994258), on every device we tried, lab and home, iOS 18.2.1 and 26.x: eligibility → 412 → TSM sync → retry → HTTP 500 → PKProvisioningErrorDomain Code=5 Questions: What does the 403 at the provisioning step mean for the Visa card? Does supervision, the iOS version, our network egress, or the fact that our devices re-provision cards every test session play a role? Is the Mastercard sandbox environment currently broken, or is there a Mastercard test card that works? Happy to capture a sysdiagnose with the Wallet logging profile if that helps.
Replies
0
Boosts
0
Views
152
Activity
Sep ’26
In App Provisioning PKErrorHTTPResponseStatusCodeKey=500
Hello, we are developing in app provisioning of our American Express network cards. After clicking add to apple wallet in our app, I launch the PKAddPaymentPassViewController and click next. It loads for a few seconds and then I get: [<private>] ProvisioningOperationComposer: Step '<private>' failed with error Error Domain=PKProvisioningErrorDomain Code=5 UserInfo={PKErrorHTTPResponseStatusCodeKey=500} Does anyone have any insight on what this error means?
Replies
5
Boosts
1
Views
1.5k
Activity
Sep ’26