We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The travel legs departureDate field is stored as an integer while expecting a format of MMDDYY on Cybersource backend site.
This results in bad requests for departureDates starting with a month below 10, e.g.:
Date 2024-02-01 (YYYY-MM-DD) results to integer 20124 instead of 020124.
Sending the resulting departureDate to the CyS API returns a validation error saying that the field should be in MMDDYY format.
Supported format for this field is MMDDYY.: departure_date
PR following.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The travel legs departureDate field is stored as an integer while expecting a format of MMDDYY on Cybersource backend site.
This results in bad requests for departureDates starting with a month below 10, e.g.:
Date 2024-02-01 (YYYY-MM-DD) results to integer 20124 instead of 020124.
Sending the resulting departureDate to the CyS API returns a validation error saying that the field should be in MMDDYY format.
PR following.
The text was updated successfully, but these errors were encountered: