HI, Before giving applepay to our UK customers , we are testing it live in our end. We have an Indian Applepay account and UK credit card. When we click on Applepay button , it gives us multiple error below: 1.) Unrecognized content security 2.) Blocked a frame with origin. 3.) status 422 4.) could not get apple pay session. elow:

https://onqanet.co.in/devra01/blocktrainV2/redirect.php response after login Authorization server returned an invalid state parameter my code is

https://onqanet.co.in/devra01/blocktrainV2/redirect.php after login response is getting Authorization server returned an invalid state parameter

When testing integrated Stripe Apple Pay for the Web, there was an error saying "Applepay is not available on this site." I don't know why. The IPhone was logged in with a Sandbox Apple Id and paid with a test card from the sandbox wallet.

Hello everyone, I am working on implementing Apple Pay in the web (react js) using Payment Request API, I have followed every step in the documentation. My problem is after I validatec the merchant successfully I requested the show() method and it would show me the payment sheet for few seconds then gives me a "TypeError: Type error", I have been trying to debug and solve the problem for few days now with no success :(. Here is a sample from my code: const request = new PaymentRequest(methods, details, options ); request.onmerchantvalidation = event => { const merchantSessionPromise = fetch(url).then(res => res.json()).catch(err => { console.error("Error fetching merchant session", err); }); event.complete(merchantSessionPromise); }; // Here where the problem occurs :( const response = await request.show(); const status = "success"; await response.complete(status); } catch (e) { console.error("Error completing the session", e); } Thank you in advance for all of the help

Our app is somewhat unique in how the pricing structure works. The customer is charged purely on time (per minute). When a customer books a job, the system will produce an estimated time & price based on a number of various inputs. For e.g. customer is given an estimate of $30 @ $1.00 per minute x 30 mins. Currently, the customer saves credit details to their account and payment is taken after the actual work for the customer is completed and we know the actual mins the job took to complete. E.g. $45 @ $1.00 per minute x 45 mins. Thus being a $15 difference between the estimated price and the actual price. In some examples, the final price ends up being less than the estimate. (Stripe is the payment gateway we use) So my question is, does Apple Pay have the capability to take payment AFTER the job is completed and we know the final minutes & cost of the job, or must the payment be taken when the customer schedules the booking in the app and the payment be based on the estimate?

Hi, We have to upgrade an ApplePay Merchant Identity certificate which is due to expire soon and we’re wondering what’s the best approach for doing that. We’ve already generated the new certificate on the Apple Developer website and now we’ve got two ApplePay Merchant Identity certs for our Merchant Identifier (the old and the new one, both valid). Can we keep both or we should revoke the old one once we’ve deployed our client application with the new one? What about the client application, should we keep both Merchant Identity certificates in its keystore or only the new one? Cheers Giovanni D'Ascola

Hi there, I'm on shopify currently and the instructions are quite vague for verifying a domain on apple developer. I'm pretty new to this but okay at figuring things out and this has stumped me. What I've tried to do is upload a txt document to the files on shopify and created a redirection to the link apple provided. Didn't work - if there are any pointers you could send my way, that would be great! Thanks so much for reading and have a great day.

I'm trying to get Apple Pay going on a Shopify site using Authorize.net. I have the text file I need to upload to /.well-known/apple-developer-merchantid-domain-association.txt. Shopify doesn't allow that sort of thing. I know Google will offer a meta tag to add to the header as an alternative when the text file isn't an option. I can't seem to find another method with Apple in this situation. Has anyone found a way around this?

Hello! I've seen numerous posts about this situation with a variety of answers and none of them seem to apply to our situation. We are implementing Apple Pay on our web site (or at least trying to). We go through the process of having the browser retrieve a session ID from Apple via a call to our server that then gets the session from Apple. But then we pass the session object to completeMerchantValidation and the payment window disappears and triggers a cancel event. I have double checked that the DNS PTR for the IP our server uses to make the request to Apple matches the domain we have validated with Apple. The session object we get back from Apple appears to be valid and contains attributes such as merchantSessionIdentifier, merchantIdentifier, signature, etc. On the iPhone XR I'm testing with, I've tried an Apple ID registered with the sandbox and a test card in the wallet as well as my Apple ID with a real credit card in the wallet. I've switched back and forth between Apple IDs and removed the cards and readded them numerous times. I do have FaceID enabled. I've tried this with the page coded for Apple Pay JS API and with it coded for the Payment Request API. They both trigger the cancel event when completeMerchantValidation is called. I've put a zillion debug statements in my code to trace every little step it takes. But now I'm at a dead end. I even made a purchase via Apple Pay on the Etsy web site just to make sure it wasn't something wrong with the phone itself. If anyone could please point me in the right directions I'd be very appreciative. Code can be provided if necessary. Thank you in advance.

It ask me to verify merchant ID domain again despite I already did it. What can cause this? When I try to verify it again I see that verification file content is being changed. And I am able to verify it with the new file. But every couple of months it ask me to verify it again. Appreciate any help.

Hi everyone, We are integrating Apple Pay on the Web, and we're trying to get the automatic renewal of the domain verification working according to the documentation: https://developer.apple.com/documentation/apple_pay_on_the_web/maintaining_your_environment Initially the domain verification is successful, but then the automatic renewal does not work. We keep getting the emails with the subject "Your domain will expire soon.", but they only say "We were unable to automatically to reverify your domain." without any further details. We confirmed that the site's SSL certificate has already been renewed by the time Apple attempted the renewal of verification, the certs are renewed 30 days before their expiry (using Let's Encrypt). So according to the docs, at least the renewal attempts 15, and then 7 days before the expiry should be successful. One example domain is this one: https://www.kayak.com/.well-known/apple-developer-merchantid-domain-association.txt, but we have the same issue for all our other domains as well. Does anyone have suggestions how to troubleshoot this further? (I tried creating a support ticket, but they basically replied that they're non-technical, and just linked me to the documentation. I've seen others complaining about this too, but couldn't find a conclusive solution, so I thought I'd signal boost and create a fresh topic to see if there are any more recent findings about this problem.) Thanks! Regards, Mark

Hi, Could you pelase confirm which character encoding is the default for the Apple Pay in Web POST responses that include PaymentMethod info https://developer.apple.com/documentation/apple_pay_on_the_web/applepaypaymentmethod. We want to make sure that no character is misrepresented when we display contents from the displayName. Many thanks, Laura

Hello I keep receiving the '401 Unauthorized' error while trying to register another partner merchant (.../paymentservices/registerMerchant). Does is it have anything to do with the type of Apple developer account, I suppose it should be somehow permitted to have access to this API method. If it's the case - might anyone please share where exactly in the Apple account I could check it? In Membership details the Entity Type is set as Company / Organisation What are the other nuances that I might be missing out here? Some details on the set up: domain already verified both processing & merchant certificates issued

Hello! A few questions about testing Apple Pay: How to test Apple Pay with a Merchant registered in region that testing is not provided for (in this case Germany)? Does the testing account needs to be a separate Apple ID from my usual Apple ID? Can Browserstack or some other simulator be used for testing Apple Pay (payment method in a website, not app)?

We have had this issue for nearly 1 year now - and any help would be greatly appreciated. When a customer arrives at the cart they see the Apple pay option and various shipping methods. Orders over £25 qualify for free 48 hrs delivery and orders over £50 its 24 hrs shipping option. These are manual shipping methods we have in place and set up for all UK customers. Our issue is that we also have calculated rates for UPS via Shipstation and easypost and for some reason these appear 1st (Due to the way the ecom platform core code functions) in the apple pay prompt and it auto selects the 1st option and it is a UPS at around £10. As it is an express payment method our customers are maybe in a hurry and they do not notice this and the fact that the shipping method needs to be manually selected even if your order qualifies for free shipping. We are aware that this causes frustration for our customers and a very time consuming process for us as we refund the difference many times a week. Our developers are stuck and provided the following notes - I have implemented this sorting using different approaches, but it looks like changing the order of the shipping options is causing an issue with apple pay. I can't properly test the apple pay button. I can reorder the shipping options on the cart page, this seems to work for the regular checkout but it creates a problem with apple pay. I've tried multiple ways to reorder the list here, but it breaks apple pay. Re the stripe code that the client mentioned - I could be wrong here - but I think shipping options never actually get passed to stripe - only the cart total and the cart items - that's it - null variable for shipping options. There is a changeShippingOptions function in the Stripe code, but i've tested updating the address and shipping options during the cart/checkout process but that part of the code doesn't get called. Regarding the last point raised, all the shipping methods available do show in the apple pay prompt as they would in the regular checkout, so I am not sure what they mean by this. This is in contrast to what stripe have advised - Apologies for the delay in our response on this one, but the shipping options are sequential in the sense that they display in order of how they were passed with the code. Changing your code to include the "free" option first will then make that the default when a customer enters your payment form: shippingOptions: [ // The first shipping option in this list appears as the default // option in the browser payment interface. { ^^ the code above is an example of this. A huge show of appreciation to anyone that can provide any advice or suggestions on this. https://www.waterstreetgallery.co.uk/ This is the stripe script that enables Apple pay In particular the line - var firstShippingOption = shippingOptions[0]; - I think is what is pulling in the options, we just need to tell it to prioritise Some methods over others. An alteration to the code below was written by our developers that showed the shipping methods in an array but when they replaced it the Apple pay would not complete and after about 25 seconds payment not complete. Any suggestions would be much appreciated 😀 `

Hi, I'm trying to integrate Apple Pay on our production website. I managed to complete the implementation on my local machine and successfully tested it with an Apple sandobx account. However, when we ported the integration to our production environment, the merchant validation step fails with this error: "Could Not Create SSL/TLS Secure Channel". Some information: we checked multiple times that the merchant ID, domain name and all other parameters we send for merchant validation are correct Our production server supports TLS1.2 and the cipher suites required by Apple pay to work The merchant domain validation has been done The TLS certificate we send for the merchant validation has been created in compliance with the Apple documentation guidelines and the server process has the right permissions to access it We explicitly set the security protocol as TLS 1.2 in the code We tried turning off the firewall but it didn't change anything Our server uses .NET version 4.5.2 We searched all the web for a solution but we can't seem to find one. It looks like a server configuration/networking issue since, as I said, it works perfectly on my local machine. Any insight on the matter would be greatly appreciated. Thanks

Our client's site uses Apple Pay, and once a month we get a series of email notifying us that the domain verification is about to expire: Your website domain that uses Apple Pay has an SSL Certificate that expires on Oct 11, 2020. We were unable to automatically to reverify your domain. To ensure uninterrupted use of Apple Pay on your website, revalidate your domain by Oct 11, 2020 in Certificates, Identifiers & Profiles. The site uses Let's Encrypt to automatically renew its SSL cert monthly. Every time that happens, we need to log into the Apple Developer tools, navigate to Certificates, Identifiers, and Profiles -> Identifiers -> Merchant IDs -> ID -> Merchant Domains, then download the file and drop it onto the server with SFTP. It's a pain. Is there a way to automate this process (or better yet, stop it from happening)? I can't imagine monthly-renewing SSL certificates is a particularly uncommon thing.

Hello, Am attempting to configure Apple Pay. When creating the Apple Pay Merchant Identity Certificate using the CSR provided by Cybersource the following error is being thrown- CSR algorithm/size incorrect. Expected: RSA(2048).