I am trying to add Apple Pay option using Stripe; however, the instructions says that I have to save the file “apple-developer-merchantid-domain-association”
in the folder: https: //example. com /.well-known /apple-developer-merchantid-domain-association
I have tried to do a bit of research on this but couldn’t find any solution.
This is why wix.com is no competitor to “real” hosting providers. Such a basic functionality… this is not only required for Apple Pay but also for many other services like Thunderbird autoconfiguration, SSL, MTA-STS, etc. - just to name a few. I tell anyone to stay away from wix because of such limitations. Also because wix just dont care. There are some requests open for multiple years now and they clearly stated this wont be implemented because of “security reasons” lol
I was able to follow the guide on the below post to set up a backend .js with my file contents and a URL redirect to get my custom file in my .well-known directory working for my needs.
Apple pay via wix payments is sadly only an option in the US , Canada and parts of Europe. Unfortunately for the rest of the world we are still stuck with some pretty antiquated payment solutions (basically stripe light and paypal)… it feels like Wix is only really invested in the US market. For example Hong Kong has had apple pay for almost 10 years and yet still no payment option for us in Wix. Same issue for google pay. We also have no BNPL options at all. Would honestly love wix payments over here but Wix is too US focused. Any idea when the rest of the world will be taken into consideration?
It looks like there is no other solution then saying farewell to Wix.
We can’t say to all our students and employees that Apple is not welcome anymore in the building. Only android and this because we use Wix as webhosting for our website.
Without saying goodby to Wix I only see one solution.
Getting an other webhosting solution beside Wix and change de DNS settings.
Pointing https:// domainname .com to the new hosting solution and https:// www.domainname .com to the wix website. And placing a redirect on the new hosting solution zo it translates https:// domainname .com/index.html to https:// www.domainname .com
It doubles the hosting cost for only one or very small text 2 files. But it should work.
Then we can bypass the flaws in Wix. But it should not be necessary.
The .well-known folder is very well known and used many years on the internet.
Only Wix does not recognize the existence and needs of the folder.
Haven’t tried it yet, but i’m going to look into this for mta-sts
Since you have to create a mts-sts. subdomain. I think you can just create an A-Record to an external provider and create the well-known folder and mta-sts file there.
I don’t have information about the reasons for being unavailable, but I wonder if it’s possible with the following workaround
I’ve not personally tested this, so cannot attest to whether it works.
That being said, I’ve used similar workarounds for similar needs.
EDIT: Simon confirms it doesn’t work, so hidden it below
Original idea
In dev mode, expose a site API from thehttp-functions.js file. You’ll want something similar to the below:
import { ok } from "wix-http-functions";
export function get_wellknown() {
let body = `{
"applinks": {
"apps": [],
"details": [{
"appID": "ABCDE12345.com.example.app",
"paths": ["/path1/*", "/path2/*"]
}]
}
}`;
return ok({
headers: {
"Content-Type": "application/json"
},
body: body
});
}
Where body represents the contents of the .well-known file (I believe .well-known is JSON)
Then, from the site dashboard, visit the SEO settings, and create a URL Redirect from the URL Redirect Manager, where old URL is /.well-known and new URL is the relative URL of the API endpoint /_functions/wellknown
This should allow you to serve the data needed. It’s worth noting that some services have no problem with the redirect and will be perfectly fine with the data, while others are not happy with the redirect.
It’s also worth doing your own research into this and ensuring all of the JSON data can be exposed this way (ensuring nothing sensitive is exposed if it should not be)
I tried this but apple and android won’t accept redirects to charge Apple Pay, and because my business is not on the countries accepted that Wix payments is enabled, we are stuck.
Also for developing apps that need some sort of connection to our domain this is a problem as well..
MTA-STS also needs this without redirects. All of them do not accept redirects because they are not secure methods.
As mentioned, (and seen here) it’s not available out of the box, and no known workarounds. That said, I’ve shared the conversation with the team already