Improved

Support more specific error responses for enhanced security validation failures

On July 10th, when a payment method tokenization request fails enhanced security validation, Spreedly will return a specific error key and message instead of the generic errors.invalid_enhanced_authentication_params. The new keys are:

  • errors.missing_tokenization_parameters
  • errors.invalid_tokenization_timestamp
  • errors.expired_tokenization_certificate
  • errors.invalid_tokenization_certificate
  • errors.invalid_tokenization_signature
  • errors.replayed_tokenization_nonce
  • errors.unknown_tokenization_validation_failure