ReadMe states Card Present is supported

[madskunker]

I find no references to the Card Present Portico APIs. Am I missing something or is the ReadMe out of alignment with the actual code?

[slogsdon]

Hi @madskunker! Apologies for the delay on this. I believe we touched base on this via email, but I'm following up here to close the loop and to provide the information for any others.

As it stands, the SDK can accept Card Present track data via our Secure Submit single-use tokenization service, but there isn't currently a way to pass the necessary CardPresent and ReaderPresent flags for those transactions to qualify as Card Present. Up until recently, our Node.js SDK has not received a lot of traffic beyond some basic Card Not Present use cases, so it hasn't been much of an issue.

This is something that should be clarified in the README, but once #15 is merged in, track data will also be able to be passed in a transaction which would make the README change not necessary.

[madskunker]

Shane, We have branched and have made the required changes for Card Present and for Lodging. Once we are certified I will send the changes to you for consideration for adding into your git Jeff Johnson “The true sign of intelligence is not knowledge but imagination” - Einstein On May 12, 2017, at 10:39 AM, Shane Logsdon <notifications@github.com<mailto:notifications@github.com>> wrote: Hi @madskunker<https://github.com/madskunker>! Apologies for the delay on this. I believe we touched base on this via email, but I'm following up here to close the loop and to provide the information for any others. As it stands, the SDK can accept Card Present track data via our Secure Submit single-use tokenization service, but there isn't currently a way to pass the necessary CardPresent and ReaderPresent flags for those transactions to qualify as Card Present. Up until recently, our Node.js SDK has not received a lot of traffic beyond some basic Card Not Present use cases, so it hasn't been much of an issue. This is something that should be clarified in the README, but once #15<#15> is merged in, track data will also be able to be passed in a transaction which would make the README change not necessary. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#17 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ANCL0uWF8_dQHS2NFT9ToZsnFpuXRhIVks5r5H0bgaJpZM4NMG8D>.