PayConex gateway - third_party_token

Answered

Follow

Steve Rittler

December 15, 2016 19:26

Question about the third_party_token in the gateway docs for the PayConex gateway. ( https://docs.spreedly.com/payment-gateways/pay-conex/ )

<payment_method>third_party_token</payment_method>

Is that meant to be the place I'd put the encrypted PAN info transferred to us from one of their magstripe & SRED devices (they work like a keyboard wedge)? https://www.bluefin.com/wp-content/uploads/2015/05/SREDKey-Datasheet.pdf

I hope so - because that would sure be sweet to be able to use their swipe and encrypt device, pass the encrypted blob to Spreedly, Spreedly calls PayConex, PayConex decrypts and processes, and then everything just magically works like any other card.

...and just like that I'll stop bugging you about p2pe!

 

0

• 

  Permanently deleted user December 16, 2016 18:15

  Hi Steve,

  The example call you see on the Gateway Guide shows the supported payment method types on the PayConex gateway.

  Have you seen our article on Third Party Vaulting? The scenario you are referring to is a 'card-present' transaction which doesn't require Third Party Vaulting. I can't tell based on the information you provided thus far if you are wanting to do both, a) take a physical card, pass encrypted card data via a swipe machine to Spreedly and store it, then b) pass the same data to PayConex and store it there as well for redundancy (TPV.) 

  Information about our Card Present Transaction beta program can be found here. Hope that helps!

  0

  Comment actions Permalink

Please sign in to leave a comment.