Post not yet marked as solved
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:
Post not yet marked as solved
https://onqanet.co.in/devra01/blocktrainV2/redirect.php
response after login
Authorization server returned an invalid state parameter
my code is
Post not yet marked as solved
https://onqanet.co.in/devra01/blocktrainV2/redirect.php
after login
response is getting
Authorization server returned an invalid state parameter
Post not yet marked as solved
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.
Post not yet marked as solved
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
Post not yet marked as solved
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?
Post not yet marked as solved
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
Post not yet marked as solved
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.
Post not yet marked as solved
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.
Post not yet marked as solved
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
Post not yet marked as solved
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
Hello forum,
I am sure that apple pay does not have any special flow for extra customer authentication like 3D Secure.
I just want some confirmation. But as far as the apple pay docs , there is no mention of this.
Thanks and Regards,
Chethan N
Post not yet marked as solved
Hello, I created a testing account and added a testing Amex card in my wallet, now I'm trying to test apple pay on my website, but it has very strange behavior, when I click the pay with apple button, popup for choosing cards opens and closes immediately, what can cause this problem and any idea how can I fix it?
Post not yet marked as solved
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).
Post not yet marked as solved
Apple notification type Is there a way to receive real-time payment information other than general product refund data?
Post not yet marked as solved
Last year I started going down the path of getting the Apple Pay, merchant ID and everything setup with my personal AppleID, until I decided to make a corporate ID instead of using my personal.
But I had already got the CSR from my merchant provider (authorize.net), and used it to generate a certificate with my personal AppleID.
But now I am trying to get the CSR setup on my corporate account. But it keeps saying "this CSR has already been used". I've spoken with Authorize.net and they are telling me that they cannot give me a new CSR for the new MerchantID I've created. They want me to have you Apple remove the association so I can reuse the CSR. I tried to say that didn't seem right, but here I am.
Anybody ever dealt with this? Can the CSR be disassociated? I have already deleted the merchantID from my personal account.
Post not yet marked as solved
Does anyone have any information regarding when/if the new Mint (http://mint.intuit.com) Apple Card integration will be extended to other financial aggregators?
Post not yet marked as solved
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
Post not yet marked as solved
I am goin to create an app and i want to apply apple pay on it. But i have some question about it.
Can I transfer the fund that my app collected through Apple pay to my bank account if i am not living in U.S?
If can, does I have to paid any fee?
Why are we getting the below emails and how can we fix this?? Our certificate expires in 2023 and there have been no organizational changes of any kind..
Dear #####,
Your website domain that uses Apple Pay has an SSL certificate that expires on
Jun 5, 2022. After automatically trying to reverify your domain, we found that
this SSL certificate has not been updated. Your domain is automatically checked
30 days, 15 days, and 7 days before this expiration date.
If you have an updated SSL certificate and the domain hasn’t been successfully
verified 7 days before expiration, please revalidate it manually by Jun 5, 2022
in Certificates,
Identifiers & Profiles to ensure uninterrupted use of Apple Pay
on your website.