-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCO wrapped_key field missing #55
Comments
This error can be due to a configuration issue on the Cybersource backend, or because of a payload data mismatch. Can you provide the request data being sent? |
Hi Michael, I look into the model ptsv2payments_payment_information_fluid_data and I found that this class is auto generated by the swagger without the field 'key'. The issue is that no exist the field 'key' described in CreatingAuthReqVisaCheckout. REQUEST JSON: Also it is important that our REST API map correctly the field 'key' with the field 'wrappedKey' described in our SOAP/SOAPI schema v1.171: <xsd:complexType name="EncryptedPayment"> Please feel free to ping me internally to discus this. Best Regards |
Using Python Client v0.0.21
Exception when calling PaymentsApi->create_payment: (400)
Reason: Bad Request
HTTP response headers: HTTPHeaderDict({'Content-Type': 'application/json', 'Content-Length': '236', 'x-response-time': '362ms', 'Connection': 'keep-alive', 'Strict-Transport-Security': 'max-age=31536000', 'v-c-correlation-id': '7d73fcaa-59e5-4aa3-9c1e-b8832002a41a'})
HTTP response body: {"submitTimeUtc":"2020-11-05T12:53:05Z","status":"INVALID_REQUEST","reason":"MISSING_FIELD","message":"Declined - The request is missing one or more fields","details":[{"field":"encrypted_payment_wrapped_key","reason":"MISSING_FIELD"}]}
The text was updated successfully, but these errors were encountered: