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
Apple Pay
RSS for tagDiscuss how to integrate Apple Pay into your app for secure and convenient payments.
Post
Replies
Boosts
Views
Activity
According to the documentation provided in
https://developer.apple.com/design/human-interface-guidelines/technologies/apple-pay/checkout-and-payment/#customize-the-payment-sheet under Displaying a website icon section, we can use icon configured for bookmarks or URL fields to display on the payment sheet but if the developer need to explicitly configure the icon using Apple Pay JS or any other way to display in summary view on payment sheet.
I'm encountering an issue with the Apple Pass Store card type backfield hyperlink not working when opened from double-clicking the power button. The value contains an HTML tag with a reference to our webpage. Everything works fine when we open it from the Wallet app, but the hyperlink doesn't seem to work when opened from the power button double-click. Has anyone else experienced this issue or have any suggestions for troubleshooting? Any help would be greatly appreciated. Thank you!
We are developing an app with the "Add card to Wallet" feature and facing an issue while adding a card to Apple Watch via the Wallet app with an app extension.
Steps to reproduce:
Open Wallet on iPhone
Tap on “Add Card”
Select card from Issuer app at "Add to Wallet" screen and complete provisioning
Now 'Add card to Watch screen' is displayed on phone
Continue provisioning on Watch
Expected result: Card is added to Watch successfully without requiring CVV/CVC.
Actual result: User is requested for CVV to add card to watch
In-app-provisioning works fine from the app with iPhone and watch.
Is it possible to skip entering the CVV step because our users don't know it?
Hello everyone, this is my first post.
I have a question, I understand that it is possible to generate nfc passes and add them to the apple wallet after obtaining the Apple certificate.
Apple asks which physical reader is compatible for reading the pass, but is it possible to use an Android or iOS mobile application to read the pass ?
Have a nice day.
Kind regards,
I am trying to do a mass enablement of a merchant ids for a psp.
The ids have been approved by apple. I am attempting to add more using the Post Request: https://apple-pay-gateway.apple.com/paymentservices/registerMerchant
(https://developer.apple.com/documentation/applepaywebmerchantregistrationapi/register_merchant) but am always getting a Refuse to connect error.
What authentication is required to get a 200 successful response?
Hi,
We’re trying to use the Apple Pay Register Merchant API and are getting an unauthorised error when we try to access the the Request for API form
Error Message:
Sorry, you cannot view this page.
The Apple ID you signed in with does not have permission to view this page.
If you’re currently a member of the Apple Developer Program, you or your Account Holder may need to update your account by agreeing to the latest license agreement in order to access this page. To view your current membership status and benefits, visit your account.
But our account is already a part of Apple Developer Program.
Hi,
I'm trying to create merchant tokens in ApplePay sandbox environment, so then I can use them to invalidate token API call and lifecycle notifications testing.
When processing test payment I use Apple Pay payment request taken directly from Apple's demo website (I skipped non important part of JSON)
{
...
"recurringPaymentRequest": {
"paymentDescription": "A description of the recurring payment to display to the user in the payment sheet.",
"regularBilling": {
"label": "Recurring",
"amount": "4.99",
"paymentTiming": "recurring",
"recurringPaymentStartDate": "2023-08-11T11:20:32.369Z"
},
"trialBilling": {
"label": "7 Day Trial",
"amount": "0.00",
"paymentTiming": "recurring",
"recurringPaymentEndDate": "2023-08-11T11:20:32.369Z"
},
"billingAgreement": "A localized billing agreement displayed to the user in the payment sheet prior to the payment authorization.",
"managementURL": "https://applepaydemo.apple.com",
"tokenNotificationURL": "https://applepaydemo.apple.com"
},
...
}
Payment is successful, but merchantTokenIdentifier in decrypted ApplePay token is always empty, regardless of test card used, I tried Visa, MasterCard, Amex.
Anyone have an idea what I'm missing and how to get that merchant token?
Is it even possible to test merchant tokens (lifecycle notifications) in sandbox?
So creating a IOS-DEVELOPMENT certificate is pretty straight forward... and I suspect some of the other types as well ... but when I try to create a PASS_TYPE_ID certificate it fails with some response messages...
"STATUS" : "404"
"code" : "NOT_FOUND"
"title" : "The specified resource does not exist"
"detail" : "There is no identifier with ID 'null' on this team"
So it would appear it's expecting more attributes to be set in the payload that are specific to creating that type of certificate. Which of course makes sense. There has to be a way of assigning it to a Pass Type ID that you have created. (It would be nice if the API could at least list existing Pass IDs, or even create them - but I've not seen how yet).
But for the life of me I can't find or figure out the syntax for this.
Anyone have any luck?
I'm implementing Wallet Extension for adding credit card on wallet, I created both extension, UI and NonUI, but the "From apps on your iPhone" option never shows to me.
My extensions have the same entitlements of main app, with the com.apple.developer.payment-pass-provisioning.
My NonUI status function implementation:
final class MBFApplePayNonUIExtensionHandler: PKIssuerProvisioningExtensionHandler {
override func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) {
let status = PKIssuerProvisioningExtensionStatus()
status.requiresAuthentication = true
status.passEntriesAvailable = true
status.remotePassEntriesAvailable = true
completion(status)
}
....
I tried this to:
final class MBFApplePayNonUIExtensionHandler: PKIssuerProvisioningExtensionHandler {
override func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) {
let status = PKIssuerProvisioningExtensionStatus()
status.requiresAuthentication = true
completion(status)
}
....
Extensions .plists:
NonUI:
NSExtension
NSExtensionPointIdentifier
com.apple.PassKit.issuer-provisioning
NSExtensionPrincipalClass
MBFApplePayNonUIExtensionHandler
UI:
NSExtension
NSExtensionMainStoryboard
MBFApplePayUIExtension
NSExtensionPointIdentifier
com.apple.PassKit.issuer-provisioning.authorization
What am I missing?
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.
Trying to get Apple Pay with PayPal to work in our Wordpress WooCommerce platform. We've done all of the registration, and have uploaded the apple-developer-merchantid-domain-association data file to .well-known but the file can not be read. It is 644 permission and we have removed the extension per Apple Support, but the link is still not readable and gives a 404 error. If I add a dat or txt extension, it is readable to a web browser, but Apple still doesn't see the file as it doesn't want the extension.
I even tried an order with Apple Pay but it failed. PayPal is useless and just send us to Apple, and Apple doesn't seem to have much on it either. Searching the support files I only find 5 year old posts.
Google Pay works without issue, *** do credit cards and PayPal. Just no Apple Pay.
The instructions are pretty basic:
Download and host live domain association file
Host a domain association file for each high-level domain and subdomain that show the Apple Pay button.
Download the domain association file for your live environment.
Host the file on your live site for each domain and subdomain you want to register, at /.well-known/apple-developer-merchantid-domain-association. For example:
https://example.com/.well-known/apple-developer-merchantid-domain-association
https://subdomain.example.com/.well-known/apple-developer-merchantid-domain-association
The Shortcuts app offers the possibility to trigger shortcuts/intends when a wallet credit card is used and a new transaction is created.
I would like to add transaction details to one of my apps and use such a shortcut for it. Other apps do the exact same thing, so this should not be a problem.
Adding a shortcut to my app was not a big deal. However, how can this be tested on simulator?
When trying to add a new automatization in the Shortcuts app using a wallet transaction as trigger I cannot finish the setup dialog since the Next button is disabled. I assume this is because no card is configured.
When trying to add a card in Wallet I just receive that this was not successful.
I have connected the simulator to a Sandbox Apple ID account using a region which supports Apple Pay (US). Using a real account does not solve the problem.
Any idea how to get this working?
Using real transaction within a store could obviously not be the solution for debugging.
I had a new apple pass integration working and now I cannot even get it to attempt to register. I'm trying to dig through the console log, but the amount of messages is crazy and I cannot seem to find anything specific to my failing pass. I did accidentally hit apple with about 200 push notifications requesting to update a pass on the same device, so I suppose it's possible something got blocked or disabled, but I can find no sign of that either. Any idea on what might have gone wrong or how I can better diagnose the problem. I've spend hours rereading doc and search the web, but now I'm tossing my hands up and asking for help
Lets say I got two preferred device languages( english first,italian second). I got a PKAddPassButton, which label gets the english localization on first install, but if I change the device language to Italian and relaunch the application, the buttons label has the english translation despite changing the first preffered device language to italian. I need to re install the application to get the italian string on the button. Is there anything I may be doing wrong?
We got failed in our In-App Provisioning and cannot add our VISA credit card to ApplePay Wallet when performing our End-to-End test in production using the test flight. Would like to seek your help to investigate the problem. Thanks
I am building a functionality where I am offering some discount to user based on some coupon code. The management of Coupon I am handling at my website and after applying coupon user can see the updated pricing. Now if the user proceed with the payment using ApplePay as per Apple docs https://developer.apple.com/design/human-interface-guidelines/apple-pay
> Display the active coupon or promotional code, or give people a way to enter it.
For example, if people can enter a code before the payment sheet appears, displaying it on the sheet can reassure them that the code works as they expect. Alternatively, allowing code entry on the payment sheet can be particularly beneficial in an express checkout flow.
Looking into this it is not clear to me weather it is a good practice to follow or a strict guideline. What could be the consequences if I don't show any coupon discount related information on ApplePay payment page
I am developing a mobile gaming app where players can either collect the app's virtual currency through winning tournaments or by purchasing virtual currency, which will be used to purchase real prizes and gift cards/vouchers. The application will be cross-platform where players can access their account on other platforms outside of the mobile app.
My question is whether the purchase of the virtual currency would be treated as an IAP or not since there is a physical value of the virtual currency outside of the app because it can be used to purchase gift cards and other real prizes?
Any guidance would be greatly appreciated it. Thanks!
Suddenly I keep getting the following error:
"HTTP Status 400 \u2013 Bad Requestbody {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}HTTP Status 400 \u2013 Bad Request"
Apple Merchant Identifier certificate and Apple Payment Processing certificate are fine. Everything was working fine some days ago.
The domain has been successfully registered as well.
Hello, we recently added Apple Pay to our application, and we have some controls for subscriptions with transactionId. I have a question: If a user updates their subscription via the App Store, can we still use the same transactionId, or should we take another approach? Thank you.