CVV and third party payment method token

Follow

Marc Smith

December 21, 2016 10:21

I wonder if you could clarify something around CVV, third party payment tokens and transacting directly with the gateway.

 

The flow I'm interested in (due to a unusual use case)  is:

 

1. Create a Spreedly payment method token

2. Create a third-party payment token via Spreedly

3. Send a purchase directly to the gateway using the third-party payment token (i.e. not through Spreedly) without having to send the cvv.

 

So I guess the questions are:

 

1. Do you send the cvv when the third party payment token request is made?

 

2. If so then can a payment be made with the third party token without the need to resend the cvv for the first transaction?

 

3. If so then I'd this true of all the gateways it a subset and how can we discover which sorry this behavior?

 

4. If not, is this functionality that you would feasibly be able to implement and would consider doing so?

0

• Official comment

  

  Permanently deleted user December 22, 2016 21:24

  Hi Marc,

  When you vault a payment with a third party through Spreedly using the `store` call, the response will contain a Spreedly payment method token representing the third party version. You would then need to use that token through Spreedly in order to transact. We do not support item #3 in your workflow above and do not have plans to.  The remaining questions regarding CVV would be determined at the gateway level. You can comment here or use our form to let us know what gateway you're using, I'd be happy to take a closer look at that integration for you. 

   

  Comment actions Permalink

Please sign in to leave a comment.