Secure Deviceless Entry

We are going live with Merchant Services mid-April and plan on incorporating Secure Deviceless Entry.  From what I've seen so far it seems pretty straightforward but I think there's one more patch coming to address a couple of bugs.  If there's one "gotcha", is that it cannont be used to save card-on-file.  I'll let you know more as we test.

-Henry

Henry, how has the Secure Deviceless Entry panned out for you guys?

Hi Clarke!

Atlanta Ballet has SDE in v15.2.33.  I understand it is "better" in .34.

However, to the best of my knowledge, some things will always be true.  There is a mandatory disclaimer on every transaction, and the user must agree to terms and services each time they use SDE.  I can confirm, SDE cannot be used to save a card to a patron record via the transaction tab.  SDE also cannot be used to add a new card to a payment plan.  Basically, SDE is always a single-use solution and is not intended to be a replacement for EMV devices.  It is helpful for the user who rarely needs to process credit cards, but IMHO it is currently too clunky for any users regularly processing credit card transactions.

In v15.2.33, it is VERY slow.  Each step takes 15-30 seconds.  And for TATL, we need to manually close the window which provides a notification that the payment was processed successfully.  That window is supposed to close on its own and I *think* they fixed that defect in v15.2.34.  (TAO has a custom project in TEST which has prevented us from doing another version upgrade.  I'm eagerly awaiting their all-clear so I can get the latest service pack.)  I'm hoping SDE will be even better in 15.2.35 than what was promised for 15.2.34.  I'll be sure to let you now when we get there.

Hope that helps!  :-)

Hi Clarke!

Atlanta Ballet has SDE in v15.2.33.  I understand it is "better" in .34.

However, to the best of my knowledge, some things will always be true.  There is a mandatory disclaimer on every transaction, and the user must agree to terms and services each time they use SDE.  I can confirm, SDE cannot be used to save a card to a patron record via the transaction tab.  SDE also cannot be used to add a new card to a payment plan.  Basically, SDE is always a single-use solution and is not intended to be a replacement for EMV devices.  It is helpful for the user who rarely needs to process credit cards, but IMHO it is currently too clunky for any users regularly processing credit card transactions.

In v15.2.33, it is VERY slow.  Each step takes 15-30 seconds.  And for TATL, we need to manually close the window which provides a notification that the payment was processed successfully.  That window is supposed to close on its own and I *think* they fixed that defect in v15.2.34.  (TAO has a custom project in TEST which has prevented us from doing another version upgrade.  I'm eagerly awaiting their all-clear so I can get the latest service pack.)  I'm hoping SDE will be even better in 15.2.35 than what was promised for 15.2.34.  I'll be sure to let you now when we get there.

Hope that helps!  :-)

Thanks, Dana!

We went live May 1.  I will echo most of what Dana said.  We're not using SDE as much as I anticipated, but it does help in a pinch with some users that need just the bare bones.  We have found for most of the Alliance Theatre staff they really needed devices, not as much for the High Museum of Art.  We just went on 15.2.35 last night so I'll let you know what I hear about that.  I believe it still registers the transaction as ecommerce, as opposed to MOTO, so that can be a little tricky.

Thanks, Henry. This is all useful information for us.