-
Notifications
You must be signed in to change notification settings - Fork 53
Apple Pay Direct
The first step of the workflow consists of validating the merchant. To do that the page needs to be served on https. If not, the Apple Pay button will not show and there will be a notice: “Server not compliant with Apple requirements” with a link to the documentation on how to prepare the server.
The plugin serves the validation file that Apple requires, but can fail in this scenario:
Server does not allow access to ./ folders .In this case the user has to put manually in the domain level, a folder named ./well-known with this file in it https://www.mollie.com/.well-known/apple-developer-merchantid-domain-association
Note also that some servers will not see this file as a text file, in that case the suggestion is to put a .htaccess file within the folder with: ForceType text/plain.
”If the validation file is reachable worldwide, but the validation error persists, check with your server hosting as there can be issues regarding timeouts or proxy configuration.”
Users can change the shipping contact information, and the system will recalculate the shipping fees.
Errors on missing data should appear on the Apple sheet, and the user should be able to correct it and restart the process.
Users can choose among the different shipping options available and the system will recalculate the total amount taking taxes into consideration too.
After authorization the WooCommerce order is created, so in case something fails in the payment, the user will be advised that something went wrong in the Apple sheet to fix it if possible, or it will close.