You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm integrating Cybersource payments into our systems and am using this gem to call the api. In the front end I have flex microform that gives me a token and I don’t have control over card details.
When I try to setup payer authentication for 3DS payments I send MerchantID, key and secret alongside with client reference code and decoded jti token from flex token and always receive 400 with "reason\":\"INVALID_DATA\",\"message\":\"Declined - One or more fields in the request contains invalid data\".
@alexmikulaninec Could you tell me exactly what is the issue and how to resolve it?
@ahmedalashii I contacted CyberSource support team and they made changes in the config for the account that was being used so that did the trick. It's not documented so it was a pain to figure out. Hope it helps.
Hi, I'm integrating Cybersource payments into our systems and am using this gem to call the api. In the front end I have flex microform that gives me a token and I don’t have control over card details.
When I try to setup payer authentication for 3DS payments I send MerchantID, key and secret alongside with client reference code and decoded
jti
token from flex token and always receive 400 with"reason\":\"INVALID_DATA\",\"message\":\"Declined - One or more fields in the request contains invalid data\"
.I'm following this example https://github.com/CyberSource/cybersource-rest-samples-ruby/blob/master/Samples/PayerAuthentication/setup-completion-with-flex-transient-token.rb
It also happens on your live console https://developer.cybersource.com/api-reference-assets/index.html#payer-authentication_payer-authentication_setup-payer-auth_samplerequests-dropdown_setup-completion-with-flex-transient-token_liveconsole-tab-request-body so I wonder if there's a bug?
Thank you.
The text was updated successfully, but these errors were encountered: