To add to my ApplePay confusion

[lesliekirk]

I had the opportunity to actually peek inside a store owner's Auth.net account and read a little more about their ApplePay offering. Imagine my surprise when I got to the Manage Your Apple Certificate Signing Request (CSR) page and it asked for an Apple Merchant ID (as provided by Apple). So I'm thinking that before a store owner even attempts to add ApplePay to their store, they should get one of these from Apple? Or is this a developer type key that Miva has embedded in the module?

I suspect other Auth.net users may see those requirements and have the same questions. So some points of clarification in the Miva Docs would be nice (beyond the "No settings are needed for Authorize.net").

[Rick Wilson]

We're still working on the docs, but I should say in general this is the rule of thumb on this feature. If you're using compatible Hardware (as you've found on the device list from Apple) and using Auth.net as your gateway, it literally should "just work" once enabled. You don't need to do any of those certs, etc... we handle all of that.

If it doesn't "just work" and you're using supported devices, either your page templates aren't secure, the item isn't added correctly, you're blacklisted by Apple (but you get a warning in Admin for that) or your processor that Auth.net connects to doesn't support ApplePay. It's worth noting since Braintree doesn't offer Gateway only, the processor problem won't exist at Braintree.

[lesliekirk]

We're still working on the docs, but I should say in general this is the rule of thumb on this feature. If you're using compatible Hardware (as you've found on the device list from Apple) and using Auth.net as your gateway, it literally should "just work" once enabled. You don't need to do any of those certs, etc... we handle all of that.

If it doesn't "just work" and you're using supported devices, either your page templates aren't secure, the item isn't added correctly, you're blacklisted by Apple (but you get a warning in Admin for that) or your processor that Auth.net connects to doesn't support ApplePay. It's worth noting since Braintree doesn't offer Gateway only, the processor problem won't exist at Braintree.

Thanks for the FYI. Considering what I just went though after the store owner (was) moved from the First Data to the Payeezy Gateway, I'm happy they are now with Auth.net.

[lesliekirk]

We're still working on the docs, but I should say in general this is the rule of thumb on this feature. If you're using compatible Hardware (as you've found on the device list from Apple) and using Auth.net as your gateway, it literally should "just work" once enabled. You don't need to do any of those certs, etc... we handle all of that.

If it doesn't "just work" and you're using supported devices, either your page templates aren't secure, the item isn't added correctly, you're blacklisted by Apple (but you get a warning in Admin for that) or your processor that Auth.net connects to doesn't support ApplePay.

I'm going to have to go back through and check everything again on the site I'm trying to set this up on, as I am now being told:

I got the prompt on the screen and it would not process after I put in the ID TOUCH on the button.

[lesliekirk]

Should I reach out to Brennan? I just tried it myself and I'm also getting message saying it can't process the payment after I do the ID Touch.

[Rick Wilson]

Yes, Brennan's the right stop.

[K Series Parts]

so I was running into that issue and it was because our credit card processor did not accept Apply Pay. I was already in the process of changing to Chase Paymentech and this morning did the change over and Apply Pay works without an issue. I didn't need to do any setup in Authorize for it, it just worked like Rick said. So if you test it and it doesn't work, it is probably more because of your credit card processor than anything else.

It does work, had it up for four hours and two customers that made purchases with it.

[lesliekirk]

so I was running into that issue and it was because our credit card processor did not accept Apply Pay. I was already in the process of changing to Chase Paymentech and this morning did the change over and Apply Pay works without an issue. I didn't need to do any setup in Authorize for it, it just worked like Rick said. So if you test it and it doesn't work, it is probably more because of your credit card processor than anything else.

It does work, had it up for four hours and two customers that made purchases with it.

Yes, Brennan is looking into that for us. Again, it needs to be noted in the docs...