I am using a sandbox account and I set the United States in the region column (Settings>General>Language & Region>Region to the US). I added test cards like (American Express and Visa) and the cards were added successfully. But I am trying to pay then I get an error like "Payment Not Completed". Note: I am trying from India.

I am using a sandbox account and I set the United States in the region column (Settings>General>Language & Region>Region to the US). I added test cards like (American Express and Visa) and the cards were added successfully. But I am trying to pay then I get an error like "Payment Not Completed". Note: I am trying from India.

I'm using a sandbox account and I set United States in the region column (Settings>General>Language & Region>Region to US) . I added test cards like (American Express and Visa) and the cards added successfully. But I am trying to pay then I get an error like "Payment Not Completed". Note: I am trying from India. I don't know any problem of the country.

Dear Team, We are facing an issue while development of Apple Pay UIWallet Extension. Kindly let us know below points to make it easy integration or development of apple pay wallet UIextension. What are the steps to open / recognise wallet to open NonUI Extension or UIExtension. Is there any dependancy on PNO data. Once Dynamic card details fetched from service is it Manual provision or Backend service need to be integrate. Thanks in Advance, Rajesh Addanki.

please can i get testflight code?

We are essentially implementing a membership card feature wherein the card details originates from a third-party provider and gets stored in the Apple Wallet. We are utilizing the Passkit Generator ( https://www.npmjs.com/package/passkit-generator ) for this purpose. The challenge, or rather issue, is that when this card is saved to Apple Wallet and tapped on the NFC reader, it only shows "Invalid Card." When we attempted to gather information from the third-party provider regarding this issue on both Android and iOS, they stated: "For IOS we do not have any experience to share with, rather than the fact we have implemented the VAS protocol under an NDA signed with Apple. Related to Passkit we do not have any experience with it." We require your assistance to identify any potential issues.

Hello, I am seeking help to use AMEX cards provided in https://developer.apple.com/apple-pay/sandbox-testing/ and add them to apple pay/wallet and have them authorised to be used in app with the sandbox account that I am using, can you help? Issue detailed: It seems that the AMEX cards that are provided in the sandbox link can only be added to the SANDBOX account wallet and shortly after they get removed form it then marked as Unavailable after an attempt to get authorised Please see screenshots of adding a AMEX card, Added & then Activating and after unavailable All these cards have the same issue and are Amex the last on the list you can see in the first picture is saying activation and in the picture under Unavailable. Pre-Conditions to set account and wallet & reproduce Should have a SandBox account The Sandbox users is set in US The region of the device is set to US The card that is attempted to be added is AMEX from the provided list iOS versions 17.4.1 to 17.6 version possibly earlier too Device iPhone 11 and others Steps to reproduce: Open wallet Tap on Add Card Add the Required test data Name/Card/ Date and CID Tap on Agree & wait Then Card is added Wait for the process and for the card to be activated Actual Result 1.The card is never shown as activated instead its marked as Unavailable 2. Amex Cant be added as a Default card assuming because its marked as Unavailable Expected Result The Amex card can be added and activated for use Set as default should possibly not be a problem Extra: if the user is using AMEX card from previous cards that are saved the card can get stuck on Activating.

https://developer.apple.com/documentation/appstoreservernotifications/app_store_server_notifications_version_1 It says that v1 is deprecated, but we have a lot of servers use v1, and we have to no time to update server code to move v1 to v2. So my question is, even v1 is deprecate, but if we don't need the new notification types in v2, can we still receive v1 notifications? cuz I can't find anywhere says when v1 will stop sending.

In our testing, we found that Apple Wallet Express Transit card is not being disabled when the default contactless app has been changed to a third party contactless payment app. In this case, even if the user has changed his default setting, he has to disable his Express Transit card in Apple Pay settings as well. This leads to frictions in the consumer journey: Consumers tapping their card on an express terminal, expecting to pay their transit through the 3rd party app, will end up paying through Apple Pay. Will Apple provide a fix for this in a subsequent iOS version and disable Express Transit together with the change of default app?

Hi there, We're experiencing difficulties setting up Apple Pay for our native macOS app written in Swift. The main issue seems to be with the "Apple Pay Merchant Identity" configuration. When setting up the Merchant ID on the Apple Developer portal (https://developer.apple.com/account/resources/certificates/list), the only available platform listed is iOS. There's no option for us to add macOS to the supported platforms. Our app uses PKPaymentAuthorizationController to present the Apple Pay sheet, but it fails immediately with a "Payment Not Completed" error. The macOS Console.app shows: com.apple.PassKit.PaymentAuthorizationUIExtension - Payment failed with fatal error <private> PKPeerPaymentService XPC Error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.passd.peer-payment was invalidated: failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.passd.peer-payment was invalidated: failed at lookup with error 159 - Sandbox restriction.} We've verified that our code works correctly on iOS, but we can't get it functioning on macOS. It seems like adding Apple Pay to a macOS app might not be fully supported, although the developer docs outline support for macOS. Additionally, we suspect this could be an issue with sandboxing. Are there additional steps or configurations required for Apple Pay on macOS that differ from iOS? Any guidance on properly setting up Apple Pay for a native macOS app would be greatly appreciated.

Hello, I'm trying to build a wallet UI extension for card push provisioning of Apple Pay. I try to add a user authentication step to the wallet app extension. I went through the documentations and app demo, but all the guidelines are based on swift UI, while I want to reuse the code from my Angular containing app (html, css, typescript) compiled to iOS native app with capacitor. Does anyone have any experience how this can be done? Do I need to separate the authentication logic in my Angular project and compile it to a separate iOS native app using capacitor? Thank you in advance.

Greetings,  Some background: We have a setup where we have more than 100 domains where we want to enable ApplePay. At the moment we use normal web merchants  and are able to support only 99domains, but are moving towards the registerMerchant API ( https://developer.apple.com/documentation/applepaywebmerchantregistrationapi/registermerchantrequest) so that we can create multiple internal merchant IDs to support more than a 100 domains.  One more important thing to note here is that we have 2 merchants for web, Merchant A and merchant B, and they are linked to different payment gateways and we need to support both due to some business logic. So theoretically, if we have 140 domains, we want to register all 140 of these under both web merchants (A & B). Since each merchant can support 99, we plan on distributing the 140 domains across the merchant by using the registerMerchant API where we'll be creating internal merchant identifiers, for example, Merchant.A.1, Merchant.A.2, Merchant.B.1, and Merchant.B.2. Thus, we will be able to support all 140 domains on both. While setting up, we noticed that we got a txt file for merchant A and B. We placed the txt file under the .wellknown path for merchant A and used the registerMerchant API to add a domain under merchant.A.1 and it worked. A few questions around this: When we try to register the same domain under Merchant B, it works too even though the txt file is missing there for Merchant B. is this because domains are verified on an account level and not merchant level? And can we rely on this behaviour to always work? Can we say that registering all our 140 domains with merchant A, would ensure that when we try to verify them under Merchant B, it'll automatically work ( ofcourse we need to call the registerMerchant API,I am trying to understand the actual verification process) When these domains are near expiration, the current re-verification process calls the same path to re-verify the domain. When using multiple merchants, which merchant txt file would be expected? Both? or just the original one? Please let me know if there are any better ways of doing what we are trying to achieve and if they are documented anywhere. Thank you!

Greetings, We are using the paymentSession API to create sessions using the merchant ID and domain for our apple pay integration. We noticed that on production env, things work as expected and invalid domains don't create session. But while using this api on sandbox, we noticed that even invalid TLDs and unregistered domains are allowed to create sessions. is this expected? if yes, is it possible to make sure sandbox works the same way as production? We are trying to validate the working on internal merchant identifier and the discrepancy is making it harder to do so. The API link - https://apple-pay-gateway.apple.com/paymentservices/paymentSession Thank you!

My provisioning code works in my main app, but when I try to use it in my app clip it fails with this: The operation couldn’t be completed. (PKPassKitErrorDomain error 2.) I'm having an issue due to how vague this particular error is and how little documentation exists to explain it? I've been looking around the PassKit and Apple Pay documentation for more specific information. But I'm not certain what to do just yet. After provisioning and receiving the digital wallet token, adding the request to the wallet produces the unsupportedVersionError. My initial thought is because the appClip bundle identifier does not match the identifier that the issuer expects, but I'm not entirely sure. I have the entitlement necessary to provision passes on apples end.

I'm developing an App Clip to add cards to Apple Wallet，and I want to check if card already added to PassKit library.For example, to show "Apple Pay enabled" checkmark on a card's UI. when I call these codes: PKPassLibrary *passLibrary = [[PKPassLibrary alloc] init]; NSArray<PKPass *> *paymentPasses = [passLibrary passesOfType:PKPassTypePayment]; the paymentPasses returns an empty array.I want to know if App Clip can access passes, and how can I get the entitlements to query the pass library.

After setting up the code and panel as per the documentation of app store connect and revenue cat, when I try to fetch the product from my app, it shows following error: PlatformException(2, There was a problem with the App Store., {readable_error_code: STORE_PROBLEM, userCancelled: false, underlyingErrorMessage: An unknown error occurred, code: 2, message: There was a problem with the App Store., readableErrorCode: STORE_PROBLEM}, null)

We now want to take this a step further adding Rewards Enrollment via the terminal. So scenario is: customer pays with apple pay on adyen terminal we check if the customer has the NFC pass in the wallet if so, they earn points (regular flow which is working) if not, wallet asks if you want to onboard into the program. We use personalization.json for for this and a webservice from us We have everything setup, but the personalization isn’t working. We follow all these steps: https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/PassKit_PG/PassPersonalization.html The issue is that we never receive a POST request from wallet on the /personalize route we needed to set up. It simply never triggers. We tried to do it manually from wallet using the ‘Add Personal Info’ button that appears now (because we added personalization.json to the pkpass bundle), but this triggers a message ‘Unable to personalise pass’, while it should show the personalization fields with our logo on top. See 2 attchements, one with the error, second one how it should look after clicking the ‘Add Personal Info’ button.

is there any avaiable demo for java? Acutally, i use code below to decrypt wrappedKey : Cipher oaepFromInit = Cipher.getInstance("RSA/ECB/OAEPWithSHA-256AndMGF1Padding", new org.bouncycastle.jce.provider.BouncyCastleProvider()); OAEPParameterSpec oaepParams = new OAEPParameterSpec("SHA-256", "MGF1", new MGF1ParameterSpec("SHA-1"), PSource.PSpecified.DEFAULT); PKCS8EncodedKeySpec pkcs8KeySpec = new PKCS8EncodedKeySpec(privKey); KeyFactory keyFactory = KeyFactory.getInstance("RSA"); Key privateKey = keyFactory.generatePrivate(pkcs8KeySpec); oaepFromInit.init(Cipher.DECRYPT_MODE, privateKey, oaepParams); return oaepFromInit.doFinal(wrappedKeyBytes); But this code can't decrypt wrappedKey, always occur error: Exception in thread "main" org.bouncycastle.jcajce.provider.util.BadBlockException: unable to decrypt block at org.bouncycastle.jcajce.provider.asymmetric.rsa.CipherSpi.getOutput(Unknown Source) at org.bouncycastle.jcajce.provider.asymmetric.rsa.CipherSpi.engineDoFinal(Unknown Source) at javax.crypto.Cipher.doFinal(Cipher.java:2168) at Caused by: org.bouncycastle.crypto.InvalidCipherTextException: data wrong at org.bouncycastle.crypto.encodings.OAEPEncoding.decodeBlock(Unknown Source) at org.bouncycastle.crypto.encodings.OAEPEncoding.processBlock(Unknown Source) ... 5 more publicKeyHash value match my publicKey and privateKey, and I can use my publicKey and privatekey to encrypt and decrypt my own text in same algorithm.

Good day, A few months ago, we started noticing that we are getting occasional ApplePay SDK Data decryption errors when we attempt to decrypt the SDK Data payload that comes back from the ApplePay SDK. We are using the C# BouncyCastle Dotnet package to handle the EllipticCurve decryption. We find on average that about 2% of all our deposits are failing because the library fails to decrypt the ApplePay SDK Data payload with the error: "Mac check in GCM failed". It appears like ApplePay is maybe sending faulty payloads to us on occasion? Unless there is an issue with the BouncyCastle library? This is causing only a few transactions to fail per day, but we still need a solution for this. Is anyone having the same issue or is there a contact from Apple I can get in touch with directly to share examples to assist with troubleshooting this? Kind regards, Reon Fourie

Hi , I'm trying to verify my domain , I uploaded the verification file and when I open the file by browser it works.But the verification status remains “Pending”. My domain has a firewall and is whitelisted, perhaps the request from Apple was intercepted? 17.0.0.0/8 has already been activated in the whitelist. How can solve this problem?