- Verifying the Domain for Apple Pay using Demandware
- Answers
- Настройка приема оплаты через Apple Pay
- Подключение Ю.Кассы
- Создание аккаунта разработчика Apple
- Обмен сертификатами с Apple
- Верификация домена в Apple
- Генерация сертификата для интернет-магазина
- Merchant verification failed for domain
- Answers
- Merchant verification failed for domain
- Answers
- Integrating Apple Pay
- Available with Premium, Growth, Scale, and Enterprise vendor plans
- Step 1:
- For Checkout Embed Forms and Checkout Pop-Up Widgets ONLY!
Verifying the Domain for Apple Pay using Demandware
I am currently trying to verify my domain for Apple Pay so that we may begin Sandbox testing as soon as possible. Apple Developer directs us to upload the file at [domain].demandware.net/.well-known/apple-developer-merchantid-domain-association
We have created out Payment Processing Certificate, our Merchant Identity Certificate, and Merchant ID. We have staged Apple Pay in Business Manager Staging, including registering the Sandbox domain.
Is the /.well-known/ path one that we must create ourselves? This seems to be the only step that does not have clear direction.
Thank you in advance for any support!
did you get the answer or solved it?
As I am facing the same issue
Answers
The part of the path that you are responsible for is: [domain]
This is an example (broken ‘h_ttps’ to avoid moderation; simply remove the space) when done right:
I understand [domain] will by my business domain. I am more concerned with the part following /.well-known/ as this is not a page or pathway we can locate. Salesforce support says this step is not necessary for domains hosted with Demandware, which appears to conflict with Apple Developer support. Is there a clear answer here for Demandware users?
> Is there a clear answer here for Demandware users?
I would not expect demandware users to have much luck w/salesforce-centric support here. devForums are typically dev-to-dev.
Источник
Настройка приема оплаты через Apple Pay
Для настройки данного способа оплаты необходимо следующее:
- Ваш сайт должен поддерживать HTTPS;
- Должна быть подключена Ю.Касса со способом подключения по API и настроен способ оплаты «Ю.Касса (API)» в Moguta.CMS
- Для настройки и функционирования Apple Pay нужно будет купить подписку на аккаунт разработчика за 99$ в год (прим.: цена указана на момент написания данной инструкции)
- Для подготовки электронных сертификатов понадобится устройство на операционной системе MacOS (iMac, iMac Pro, MacBook, и т.д.)
Подключение Ю.Кассы
Как настроить и подключить Ю.Кассу по методу API вы можете узнать из нашей инструкции http://wiki.moguta.ru/nastroyki-oplaty/integratsiya-s-yandeks-kassa-api
Создание аккаунта разработчика Apple
Как завести аккаунт разработчика Apple можно узнать из инструкции Яндекс (см. раздел 1 «Регистрация в Apple Developer Program») https://kassa.yandex.ru/files/manual_connection_Apple_Pay(website).pdf
Обмен сертификатами с Apple
1. Авторизуйтесь в личном кабинете developer.apple.com;
2. Перейдите в раздел «Certificates, IDs & Profiles»;
3. Начните создание сертификата кнопкой «Create a Certificate»;
4. Прокрутите список вниз и выберите «Apple Pay Payment Processing Certificate»;
5. Придумайте имя и название идентификатора. Имя произвольное, оно нигде использоваться при настройке не будет. Идентификатор желательно задавать по советам Apple: merchant. . . Например для сайта moguta.ru будет выглядеть так: merchant.ru.moguta;
6. В разделе «Apple Pay Payment Processing Certificate» нажмите «Create Certificate»;
7. Выберите вариант «No», чтобы обозначить, что оплаты будут не в Китае;
8. Прикрепите файл .csr, полученный от Яндекс, и нажмите Download, чтобы скачать сертификат от Apple в формате .cer;
9. Отправьте .cer файл в Яндекс и дождитесь ответа о том, что они со своей стороны всё настроили.
Верификация домена в Apple
1. В разделе «Apple Pay Payment Processing on the Web» нажимаем «Add Domain в Merchant Domains»;
2. Укажите домен вашего сайта;
3. Нажмите ‘Download’, чтобы получить текстовый файл. Сохраните его на сервере так, чтобы он был доступен по ссылке https:// /.well-known/apple-developer-merchantid-domain-association.txt
4. Нажмите «Verify», и Apple проверит доступность этого файла. Если всё верно, то домен будет одобрен;
Генерация сертификата для интернет-магазина
1. Нажимаем «Create Certificate» в разделе «Apple Pay Merchant Identity Certificate»;
2. Откройте на устройстве с MacOS приложение «Связка ключей» (Keychain Access);
3. Выберите «Связка ключей» -> «Ассистент сертификации»->»Запросить сертификат у бюро сертификации. «;
4. Заполните поля «E-mail» и «Общее имя» (произвольное), e-mail БС не нужен. Выберите «Запрос: Сохранен на диске»;
5. Сохраните файл;
6. Загрузите сохраненный файл в Apple;
7. Скачайте получившийся сертификат merchant_id.cer по кнопке «Download»;
8. Откройте в «Связка ключей», загрузите туда полученный сертификат, найдите его через поиск по общему имени и экспортируйте закрытый ключ в формате «Обмен персональной информацией (.p12)»;
9. Задайте пароль;
10. Откройте приложение «Терминал» (Terminal.app);
11. Для получения файла приватного ключа введите следующую команду:
openssl pkcs12 -in .p12 -out ApplePay.key.pem -nocerts -nodes
12. Терминал запросит пароль, введите тот который вы задавали при экспорте сертификата;
13. Для получения файла сертификата введите следующую команду:
Источник
Merchant verification failed for domain
We have a domain that originally validated successfully when uploading the .well-known/apple-developer-merchantid-domain-association.txt and I am currently successfully transacting Apple Pay payments.
Now we need to renew/verify again as the validation expires on the 10/01/2019 and I get the following error…
Verification failed for domain — Unable to establish a secure connection to ‘https://
If I browse the .well-known URL all appears fine.
I have used Qualys SSL Labs https://www.ssllabs.com/ssltest/ who have rated the SSL A with Extended Validation.
The only difference I can see from when we previously verified and now is that we have a new SSL and the insecure TLS 1.0 is now disabled.
The issuer of the certificate is “COMODO RSA Extended Validation Secure Server CA”
Any help would be really appreciated.
Answers
Just a quick update for anyone else having the same issues…
I was completely unable to get the Apple Merchant Domain Validation proses to work using the latest certificate for COMODO RSA Extended Validation Secure Server CA.
I cross checked all certificate requirements from the Apple Pay documentation with Comodo directly and everything suggests that it should work — however it fails every time. I can only assume that Apple don’t trust Comodo certificates or hasn’t updated it’s domain validation tool.
My work around was to install a temporary 3 month certificate from letsencrypt.org and used it to validate the domain with Apple. Once validated I put back my Comodo certificate (my temporary certificate was only visible for 30 seconds).
Additionally, was able validate with TLS 1.0 disabled.
I don’t see this as a long-term solution but may help others in the same predicament.
Источник
Merchant verification failed for domain
We have a domain that originally validated successfully when uploading the .well-known/apple-developer-merchantid-domain-association.txt and I am currently successfully transacting Apple Pay payments.
Now we need to renew/verify again as the validation expires on the 10/01/2019 and I get the following error…
Verification failed for domain — Unable to establish a secure connection to ‘https://
If I browse the .well-known URL all appears fine.
I have used Qualys SSL Labs https://www.ssllabs.com/ssltest/ who have rated the SSL A with Extended Validation.
The only difference I can see from when we previously verified and now is that we have a new SSL and the insecure TLS 1.0 is now disabled.
The issuer of the certificate is “COMODO RSA Extended Validation Secure Server CA”
Any help would be really appreciated.
Answers
Just a quick update for anyone else having the same issues…
I was completely unable to get the Apple Merchant Domain Validation proses to work using the latest certificate for COMODO RSA Extended Validation Secure Server CA.
I cross checked all certificate requirements from the Apple Pay documentation with Comodo directly and everything suggests that it should work — however it fails every time. I can only assume that Apple don’t trust Comodo certificates or hasn’t updated it’s domain validation tool.
My work around was to install a temporary 3 month certificate from letsencrypt.org and used it to validate the domain with Apple. Once validated I put back my Comodo certificate (my temporary certificate was only visible for 30 seconds).
Additionally, was able validate with TLS 1.0 disabled.
I don’t see this as a long-term solution but may help others in the same predicament.
Источник
Integrating Apple Pay
Available with Premium, Growth, Scale, and Enterprise vendor plans
Paykickstart vendors can easily enable Apple Pay as a payment method for customer purchases by following the steps below.
IMPORTANT:
At this time, Apple Pay ONLY works via Stripe integrations, we will be expanding to other payment gateways later.
Apple Pay will only display on Apple-supported devices and browsers.ie: IOS or Mac devices using Safari.
Step 1:
After enabling Stripe for a campaign, The next step will be Enabling Apple Pay for the campaign if you choose to take Apple Pay as a payment option for those particular products in the campaign.
Then make sure Stripe is enabled, then you can also enable the Apple Pay option.
After saving, Apple Pay will be added to the related product checkouts for this campaign.
Normal Checkout page(URL) checkouts will show the Apple pay option automatically.
IMPORTANT : For enabling Apple Pay on Embed and Pop-up checkout forms, please see below.
For Checkout Embed Forms and Checkout Pop-Up Widgets ONLY!
Unfortunately, Apple Pay cannot work automatically with embed and pop-up checkout forms. Vendors will need to speak with their web host to make the following additional changes.
For example, if your embed form/widget is placed on https://example.com/product-page, make that file available at https://example.com/.well-known/apple-developer-merchantid-domain-association.
Otherwise, Apple Pay will not work on embeds and pop-up checkouts.
*Note: If you choose to not set this up for embeds/pop-ups, they will still function as normal, but Apple pay will not be shown on embed/pop-up checkouts.
Источник