CVV codes

Follow

Josh Reading

July 12, 2018 14:16

We are currently having issues with a Migs gateway merchant based in Dubai which we have already setup

 

We can submit and successfully vault a card and generate a card token but when using this token against the gateway get the following error

 

E5431-07041430: Invalid Field : Field in error: 'order.paymentDevice.secureCode', value 'null' - reason: A CSC value is required for the transaction source used for this transaction

 

 

From what we can tell we need to send the CSC/CVV value each time but this is apparently not being sent when we use the card token

 

Alternatively is there a way to send the CVV/CSC each time when we try to take payment?

 

We have checked the docs but are unsure on how to proceed forward

0

• 

  Permanently deleted user July 13, 2018 16:40

  Hi Josh,

  To reiterate the email exchange that we had:

  At Spreedly, we never retain the CVV, rather it is only cached. If you add a payment method and include the CVV, it will remain for 3 minutes or until a transaction is completed, whichever occurs first.
  
  After which, the CVV will be redacted automatically. The only exception is if you pass the `continue_caching` parameter.
  
  Typically, gateways will require the CVV in the first authorization, and then the payment method can be used by the merchant in subsequent transactions without the CVV. Though this varies by gateway, processor, and even by merchant, so I cannot say this definitively.
  
  If you do need to include the CVV with every transaction, you'll need to capture that data from the cardholder and use `recache` to update the CVV to the payment method.

  Additionally, it may be possible to turn off the CVV requirement at the gateway/merchant account level, but that will vary.

  Let me know if you have additional questions.

  0

  Comment actions Permalink

Please sign in to leave a comment.