If you look at the ServerHello message, you can see the server found and accepted the cipher suite that matches the client, which also matches one of the required ciphers that apple pay supports , so something else is going on and I don't know where to look As you can see from my image, I'm communicating to the apple pay sandbox server, passing in the same supported tls protocol and cipher suite that the error would suggest -> Phase, after the server sends back the cipher spec to the client.

I've been using Wireshark to check what's going on, and I seem to be failing once the server is in the Server does support tls 1.2, since I send requests on tls 1.2 to apple pay's development server (below) Your server must support the Transport Layer Security (TLS) 1.2 protocol and one of the cipher suites listed in Table 1. To enable merchant validation, your server must allow access over HTTPS (TCP over port 443) to the Apple Pay IP addresses provided in Listing 1 below.ĭone, server is open to all ips on port 443 As listed on the apple page (), I need the following requirements met:Īll pages that include Apple Pay must be served over HTTPS. I've dug around and this 500 error is happening somewhere in the network layer. Server then calls the Start Session endpoint at the provided URL I am having trouble validating the merchant in my apple pay sandbox environment. I hope this answer your question, I'd be happy to tell you more (if I can) about Apple Pay if you need so. I'm not sure how Stripe work, but I would bet the management of Sandbox/Prod basically works the same.

The Braintree documentation is really complete and helpful, please take a look. (The entitlements is generated when you toggle capabilities). Static NSString *const MerchantID = NSString *const MerchantID = then when you init the Apple Pay sheet, you just pass the MerchantID constant and it will grab the right one.įiles, on for each configuration pointing to the right Apple pay certificate. You'll probably create a MechantID constant like that: In your app, you'll need to have (at least) 2 builds configuration, one for Sandbox/Debug, one for Production/Release. In Braintree, you'll link to the Sandbox MechantID in the Braintree Sandbox Dashboard, and to the Prod MerchantID in the Braintree Production Dashboard. Apple Pay will match this behavior, you'll have to generate two MechantID, one for the Sandbox, and then one for Prod. You're probably aware that when you use Braintree, you got a Sandbox environment, and a Production environment. I did implement Pay in a shopping app using

Apple sandbox account