Overview

Hi Apple Pay Team, We are building a QR-based payment platform and planning to integrate Apple Pay on the Web as a Payment Platform Integrator. Our setup: We operate a single domain (e.g., pay.example.com) where all Apple Pay transactions take place When a customer scans a merchant's QR code, our hosted page opens with the Apple Pay button We process payments on behalf of multiple merchants (receivers), each with a separate merchant ID at our payment processor We want to use a single Payment Platform Integrator ID with one set of certificates (Merchant Identity + Payment Processing) The payment processor handles sub-merchant identification and settlement to the correct receiver via card network (Visa/Mastercard) sub-merchant fields Our question: Since all transactions happen on our single domain, is it mandatory to register each sub-merchant via the Apple Pay Web Merchant Registration API (/paymentservices/registerMerchant) and use their partnerInternalMerchantIdentifier in the payment session request? Or is it acceptable to use our Platform Integrator's own merchant identifier for all payment sessions, given that: Only one domain is involved Sub-merchant identification is handled at the payment processor / card network level Our domain verification file is already hosted and verified We would appreciate clarity on the correct approach before we proceed with our integration. Thank you.

My iOS app “TaskCal: Task Manager” (version 1.2.8) has been stuck in “Waiting for Review” for more than 3 weeks, and I’m not sure what else I can do at this point. I’d like to know if there’s anything wrong with my submission, or if there’s any other way to get more clarity from App Review. Here are the key dates (GMT+8): Jan 30, 2026 – Version 1.2.3 was approved and marked “Ready for Distribution”. Jan 31 – Feb 8, 2026 – I submitted version 1.2.8 multiple times. Several submissions were later marked as “Removed” in App Store Connect. Feb 9, 2026, 12:39 AM – I submitted version 1.2.8 again. This submission has been in “Waiting for Review” ever since. Today is Mar 3, 2026 (Taipei time) – The status is still “Waiting for Review” with no change. Because of this, I contacted Apple Developer Support multiple times through Contact Support. I only received one reply, on Feb 21, 2026, which said: Hello Alan, Thank you for reaching out to Developer Support about your app, “TaskCal: Task Manager.” I understand that you’re concerned. After reviewing your app’s submission history, I can confirm that your app is still in the “Waiting for Review” status as of February 8th 2026. To address your concern about the duration of the review, I’ve contacted the review team to bring this to their attention. At this time, there’s no further action required from your end. If the review team needs any additional information to complete the review, they’ll reach out to you directly. We appreciate your patience during this process. Your case number is 20000107493507. Stephanie Developer Support Since then, there has been no visible progress and no follow‑up messages. The App Review page still shows: Version: iOS 1.2.8 Status: Waiting for Review Case ID: 20000107493507 I completely understand that review times can vary, but: My previous version (1.2.3) was reviewed and approved normally. This is a relatively small productivity app with no major policy changes. It’s been over 3 weeks in “Waiting for Review” for this specific submission, with multiple earlier submissions of the same version being “Removed” without clear explanation in the UI. My questions: Is there anything I may have done wrong in the submission process (for example, causing multiple “Removed” submissions) that could block or delay this review? Is there any other official channel I can use to get more clarity beyond contacting Developer Support (which only confirmed that it’s “Waiting for Review”)? Has anyone here experienced a similar long “Waiting for Review” state recently, and if so, how was it resolved? I’m worried that there might be some issue with this build or with my account that I’m not seeing in App Store Connect. At the same time, I don’t want to keep canceling and re‑submitting if that could make the situation worse. Any advice from Apple or other developers who have gone through something similar would be greatly appreciated. Thank you, Alan

描述：低等级会员在 7 天免费期内订阅了高级会员 预期：低级会员的 7 天免费试用结束，高级会员直接扣费生效，苹果的升级通知如下： { "extra_info": { "quantity": 1, "expiresDate": 1754627893000, "purchaseDate": 1754623693000, "transactionId": "2000000979349440", "offerDiscountType": null, "originalTransactionId": "2000000979347229", // 升级前后没有变化 "subscriptionGroupIdentifier": "21729756" }, "decodedPayload": {}, "orgin_sku_name": "unlimited.minutes.per.year.v3", "payment_platform": "app_store", "decodedPayload_Renew": { "productId": "unlimited.minutes.per.year.v3", "autoRenewStatus": 1, "originalTransactionId": "2000000979347229" }, "decodedPayload_Trans": { "type": "Auto-Renewable Subscription", "price": 228000, "bundleId": "ai.plaud.ios.plaudzh", "currency": "CNY", "quantity": 1, "productId": "unlimited.minutes.per.year.v3", "signedDate": 1754623696459, "storefront": "CHN", "environment": "Sandbox", "expiresDate": 1754627293000, "purchaseDate": 1754623693000, "storefrontId": "143465", "transactionId": "2000000979349440", "appTransactionId": "704742096472000913", "transactionReason": "PURCHASE", "inAppOwnershipType": "PURCHASED", "webOrderLineItemId": "2000000107917134", "originalPurchaseDate": 1754623472000, "originalTransactionId": "2000000979347229", "subscriptionGroupIdentifier": "21729756" } } 异常 case：苹果通知升级到高级会员且继续剩余试用时间，例如：低等级会员7 天免费试用期剩余 4 天，升级到 4 天的高等级会员的免费试用，收到的通知消息如下： "extra_info": { "quantity": 1, "expiresDate": 1773109207000, "purchaseDate": 1772708455000, "transactionId": "550002836609836", "offerDiscountType": "FREE_TRIAL", "originalTransactionId": "550002832625469", //升级前后没有变化 "subscriptionGroupIdentifier": "21729756" }, "purchase_type": "upgrade", "decodedPayload": { "signedTransactionInfo": {}, "orgin_sku_name": "unlimited.minutes.per.year.v3", "payment_platform": "app_store", "decodedPayload_Renew": { "productId": "unlimited.minutes.per.year.v3", "autoRenewStatus": 1, "originalTransactionId": "550002832625469" }, "decodedPayload_Trans": { "type": "Auto-Renewable Subscription", "price": 0, "bundleId": "ai.plaud.ios.plaudzh", "currency": "CNY", "quantity": 1, "offerType": 1, "productId": "unlimited.minutes.per.year.v3", "signedDate": 1772708460325, "storefront": "CHN", "environment": "Production", "expiresDate": 1773108607000, "offerPeriod": "P7D", "purchaseDate": 1772708455000, "storefrontId": "143465", "transactionId": "550002836609836", "appTransactionId": "705330723507531368", "offerDiscountType": "FREE_TRIAL", "transactionReason": "PURCHASE", "inAppOwnershipType": "PURCHASED", "webOrderLineItemId": "550001244481732", "originalPurchaseDate": 1772507407000, "originalTransactionId": "550002832625469", "subscriptionGroupIdentifier": "21729756" } } 请问是苹果的会员试用的策略发生了变化吗

Hello, I'm currently investigating an issue related to iOS credit card autofill (Payments & Card Details) in our mobile application. Our app is built using React Native, and we are implementing card input fields using TextInput with the required autofill configuration: autoComplete="cc-number" textContentType="creditCardNumber" Despite correctly configuring these properties, credit card autofill is not being triggered on iOS devices. I would appreciate clarification on: Is credit card autofill officially supported for React Native TextInput fields using autoComplete="cc-number" and textContentType="creditCardNumber"? Are there any additional requirements (entitlements, associated domains, specific configurations, etc.) needed for payment autofill to work? Is autofill expected to work inside WKWebView contexts? Are there any known limitations or restrictions for third-party frameworks such as React Native? I would appreciate any guidance or documentation you can share regarding the expected behavior and official support for this scenario

I’ve been waiting for over a month after payment for Apple to activate my Developer account. I’ve sent countless emails and spoke to the Support on the phone and no one is able to assist me. I’m shocked how this has been dealt with.

<Apple Developer Program许可协议>已更新并需要查阅。若要更新现有App和提交新 App，账户持有人必须登录账户，查看并接受更新后的协议。 apple 会费到期 续费以后 无法获取app内购数据，经排查可能是这个协议没有签署，签署后多久可以重新获取到app内购数据。

Currently it's Sonnet 4.5. I know that 4.6 is out.

We are building an AI-powered smart glasses companion app, similar to Meta Ray-Ban. We want to provide true hands-free calling support. Right now, whenever the app tries to dial a native cellular call, iOS shows a confirmation screen that requires the user to tap to start the call. If the user always has to confirm/tap on the phone screen, there is no real point in using smart glasses for making calls. How can we initiate a native outgoing call without any confirmation dialog or extra tap, exactly like Siri does it, or like the Meta Ray-Ban glasses do when the user says “Hey Meta, call [name]” Please guide us on the correct APIs, entitlements, or integration path to achieve this behavior. Thank you.

Dear Apple Developer Support Team, I am writing to formally escalate an issue regarding my Apple Developer Program enrollment. On February 23rd, I completed the $100 enrollment payment for an Individual Apple Developer account. The amount has been successfully debited from my card, and I have received official payment confirmation emails from Apple confirming receipt of the funds. However, as of today (March 3rd), my account still reflects that payment needs to be completed, and the enrollment remains inactive. This is my first-time enrollment as an individual developer. Given that payment has already been processed and acknowledged by Apple, I am concerned about the lack of activation and the absence of any communication regarding the delay. Additionally, I have submitted multiple support requests over the past five days but have not received any response or update. This delay is affecting my development and release timelines. I kindly request: Immediate confirmation of payment reconciliation on your end Clarification on the current status of my enrollment An estimated timeline for activation Escalation of this case to the appropriate billing or developer enrollment team Please let me know if any further documentation (transaction ID, invoice number, Apple ID details) is required from my side. I would appreciate your urgent assistance in resolving this matter. Kind regards, Gowtham Potureddi

Hello, My app has been stuck in review for over a month. I can see other people in this forum are having the same issue. What can we do to speed this up? What's particularly frustrating is that even people in the support team are not able to get an update from the review team. Can someone please give us some information? App id: 6758049144

I'm using MusicKit for DRM track playback in my iOS app and a third party library to play local user-owned music on the file system and from the music library. This app is also supporting accessory devices that offer Bluetooth remote media control. The wish is to achieve parity between how the remote interacts with user owned music and the DRM / cloud / Apple Music tracks in my application music player. Track navigation, app volume (rather than system volume), and scrubbing need to work consistently on a mix of tracks which could alternate DRM and cloud status within one album or playlist. Apple Music queue and track pickers are not useful tools in my app. How can I support playing DRM and Apple Music tracks while not surrendering the remote control features to the system?

In many cases I’ll be talking to folks with a memory management problem and I’ll say “You should investigate this with the standard memory debugging tools.” They then turn around and ask me “What are those tools?” Well, this is what I mean: Zombies — This lets you quickly detect when an object is used after it’s been deallocated. Learn more about it in the Finding zombies section of the Instruments Help and in Investigating crashes for zombie objects. There was also an excellent WWDC video about this, namely, WWDC 2010 Session 311 Advanced Memory Analysis with Instruments. This is no longer available in the video archive but if you can find a copy it’s well worth a watch. Address Sanitizer — This is a lower-level tool that finds a variety of common memory management issues, including use after free and buffer overruns. Learn more about this in Diagnosing memory, thread, and crash issues early and the various articles it links to. There’s also a good discussion of this tool, and other Xcode runtime diagnostic tools, in WWDC 2017 Session 406 Finding Bugs Using Xcode Runtime Tools (also no longer available from Apple). Hardware memory tagging — If you have access to a device with hardware memory tagging — starting with the A19 or M5 processors — consider enabling Memory Integrity Enforcement (MIE). For the details, see Enabling enhanced security for your app or watch Secure your app with Memory Integrity Enforcement. Even if you don’t want to do that for your production app, enable it just for development by checking Hardware Memory Tagging in the Options tab of Xcode’s scheme editor. Older tools — There are a variety of older tools that might be useful in some specific circumstances. See the Enabling the Malloc Debugging Features section of the Memory Usage Performance Guidelines for more information about these. Of specific interest is libgmalloc, which is documented in a UNIX man page. For some practical examples of how to identity a memory management crash report and then investigate that crash with these tools, take a look at WWDC 2018 Session 414 Understanding Crashes and Crash Logs. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Revision History: 2026-03-02 Added a discussion of hardware memory tagging. 2023-05-09 Added a link to Investigating crashes for zombie objects. 2023-03-22 Removed another WWDC session video link. Made minor editorial changes. 2020-10-23 Fixed some formatting errors. 2019-10-30 Removed the link to WWDC 2010 Session 311 Advanced Memory Analysis with Instruments because it’s not long available in the archive. Refreshed all the other links. 2019-01-22 Fixed the link to libgmalloc. 2018-11-02 Updated to include a reference to WWDC 2018 Session 414 Understanding Crashes and Crash Logs. 2017-11-16 First posted.

My app, which I submitted for review on February 4th and has never been published before, is still showing as "waiting for review." It has been rejected twice before. What is the reason? What is the solution? When will you respond? App ID: 6758409782

Hello i ordered on Apple Developer Program on 26 Feb. I got an Email ( Thank you for your order. Here's a summary of your order request, which will be processed within 2 business days) but its been 2 weeks already and no reply. I opened 2 support cases already thru support from the apple developer support site and no answer either . I dont know what else to do, i dont want to have to dispute thru my bank because i want to be an apple developer, but im losing hope at this point. Please help me to activate my account

Our app with Apple ID 6752634390 has been in status Waiting for Review since Feb 09 which has been more than one month. And we have sent email via Contact Us two times already but no progress yet. Any one has any idea if there is anything we can do to move on?

Hi team, I am having an issue with paying for my apple developer enrolment program. Error message is: Your payment authorisation failed on card XXXX. Please verify your information and try again, or try another payment method. Things I have tried and has not worked: Multiple company visa card Multiple personal visa card Ensuring billing address matches my visa cards Turn off VPN Try my personal IOS device My company and personal cards should work because I have paid for other products and apple products with it. I do not think this is an isolated incident and that Apple should look into this immediately to prevent blocking developer enrolment. Other similar threads: https://developer.apple.com/forums/thread/817892?page=1#878707022 https://www.reddit.com/r/applehelp/comments/1m5fj6q/how_to_fix_your_payment_authorization_failed_on/ https://developer.apple.com/forums/thread/814065

I’m seeing a visual glitch in SwiftUI List on iOS 26 when row order changes after a swipeActions action. Setup: List + ForEach of items Items are sorted dynamically by isSelected (unselected first, selected last) Swipe action toggles isSelected Row should animate to new position Problem: On swipe select/unselect, the row sometimes appears to disappear briefly, then reappear in the new position Most visible when unselecting an item from the bottom selected group (it should move to top) Sometimes there is a temporary “empty gap” near the top during the move In some row styling setups, row corner masking also looks wrong during animation What I tried: Different animations (default, easeInOut, spring) Adding/removing small dispatch delay before state change Moving section header content outside List Using custom row backgrounds/corners vs system row styling Keeping stable IDs in ForEach Behavior still appears with native List + swipeActions on iOS 26. So my question is: Is this a known issue/regression with List row move animations on iOS 26? Recommended pattern to keep native swipe actions but avoid this visual artifact? This worked smoothly on iOS 18 with the same approach, and the visual glitch appears only after moving to iOS 26.

Hello, I enrolled in the Apple Developer Program and placed the $99 order. Shortly after, I received the email saying: “Thank you for your order. Your order request will be processed within 2 business days.” However, it has now been over two weeks and my membership has still not been activated. I also contacted Apple Developer Support about a week ago through the contact form, but unfortunately I have not received any reply so far. When I visit developer.apple.com, I still see the page prompting me to complete or place the order, even though I already placed it and received the confirmation email. Could someone from Apple please check the status of my enrollment or advise what I should do next? Thank you.

I dutifully upgraded my software (beta) on Feb. 24 when prompted. I could not get the computer to reboot, then after about 5 hours on the phone with, I think, 4 techs, they told me the only solution was to wait for the next update - I could not go backwards to the regular version. So $1,299 later I have a new Mac Mini M4! I have to work, so it was the only solution. What do I win?

I would really like to be able to categorize my contacts. I work for a grocery store and have contacts from various companies. I would like to be able to categorize them by company or group them as I see fit. Currently, I don't see a way to do this. Please add this in a future update. Having all contacts just alphabetically is not efficient enough. Also, I would like to be able to manually adjust the size of widgets. i.e. If I want more stocks to be visible, I would like to be able to lengthen the height/width of the widget beyond what it currently allows to view more information. Thank you. If you have any follow-up questions, please let me know. Torrey