Comments for EPX http://epx.com/blog Fri, 23 Jul 2010 11:30:30 +0000 http://wordpress.org/?v=2.9.2 hourly 1 Comment on The Tokenization Bandwagon Is Music to Our Ears by skendus http://epx.com/blog/?p=89&cpage=1#comment-417 skendus Fri, 23 Jul 2010 11:30:30 +0000 http://epx.com/blog/?p=89#comment-417 Thank you for your feedback Steve. Thank you for your feedback Steve.

]]> Comment on The Tokenization Bandwagon Is Music to Our Ears by Steve Sommers http://epx.com/blog/?p=89&cpage=1#comment-415 Steve Sommers Fri, 23 Jul 2010 01:20:01 +0000 http://epx.com/blog/?p=89#comment-415 First, I wish to thank you for giving Shift4 credit for coining the term tokenization -- most competitors leave this tidbit of information out. In the above posting you make the reference: "Shift4's process of code generation within the merchant’s environment, and their data flow is significantly different from EPX’s off-premises approach, but more or less aims at the same purpose." This statement is incorrect. Shift4 uses a SaaS model. Merchant software is not required for the tokenization process, and in this simplified "no component" model, tokens are generated only within our data center. While we do offer software components that can be installed within the merchant environment, these pieces are used for creating secure VPNs to our data centers with load balancing, fail over and offline tokenization capabilities in the event of an Internet failure. These components are not required and "code generation within the merchant environment" only occurs during offline conditions. We have found that depending on TCP-IP/SSL alone does not provide our customers with the fault tolerance and the assured delivery they demand. First, I wish to thank you for giving Shift4 credit for coining the term tokenization — most competitors leave this tidbit of information out.

In the above posting you make the reference: “Shift4’s process of code generation within the merchant’s environment, and their data flow is significantly different from EPX’s off-premises approach, but more or less aims at the same purpose.”

This statement is incorrect. Shift4 uses a SaaS model. Merchant software is not required for the tokenization process, and in this simplified “no component” model, tokens are generated only within our data center. While we do offer software components that can be installed within the merchant environment, these pieces are used for creating secure VPNs to our data centers with load balancing, fail over and offline tokenization capabilities in the event of an Internet failure. These components are not required and “code generation within the merchant environment” only occurs during offline conditions. We have found that depending on TCP-IP/SSL alone does not provide our customers with the fault tolerance and the assured delivery they demand.

]]> Comment on More Merchants Taking Advantage of “Pin-Less” Debit Transactions to Lower Transaction Costs by Tweets that mention Home - Electronic Payment Exchange (EPX) Blog - Secure, cost-effective payment processing -- Topsy.com http://epx.com/blog/?p=50&cpage=1#comment-8 Tweets that mention Home - Electronic Payment Exchange (EPX) Blog - Secure, cost-effective payment processing -- Topsy.com Wed, 30 Dec 2009 18:36:35 +0000 http://epx.com/blog/?p=50#comment-8 [...] This post was mentioned on Twitter by EPX Electronic Pymnt, Fred Campos. Fred Campos said: RT @EPX_Payments: More Merchants Taking Advantage of “Pin-Less” Debit Transactions 2 Lower Transaction Costs: http://bit.ly/7BBkNV [...] [...] This post was mentioned on Twitter by EPX Electronic Pymnt, Fred Campos. Fred Campos said: RT @EPX_Payments: More Merchants Taking Advantage of “Pin-Less” Debit Transactions 2 Lower Transaction Costs: http://bit.ly/7BBkNV [...]

]]>