-
Notifications
You must be signed in to change notification settings - Fork 4.6k
fix(connectors): [TSYS] change order of order_number in tsys auth request body #9579
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
Conversation
Changed Files
|
|
This PR LGTM. I have tested all the flows. Working as expected. I have attached the curls and responses in the description. |
|
Hey @bsayak03, are there any other actions required on my side to get this merged? Thanks! |
No, its in review. Should get merged asap @mattiapitossi |
| expiration_date: ccard | ||
| .get_card_expiry_month_year_2_digit_with_delimiter("/".to_owned())?, | ||
| cvv2: ccard.card_cvc, | ||
| order_number: item.connector_request_reference_id.clone(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this change needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is primarily to be coherent with the above definition of the structure, but it's not strictly necessary as the serialization will follow the struct definition. Let me know if you prefer to keep the previous one
Type of Change
Description
This PR fixes the request body order of the TSYS contract for the auth request
Additional Changes
Motivation and Context
fixes #9375
How did you test it?
Unfortunately, I'm not able to test this changes against an actual sandbox as I've been in touch with TYSY and they only provide test credentials for certification purpose. Also this PR mention that there are not test credential for this project.
I was able to reproduce mentioned in the issue by using the Sandbox inside the developer portal:

That's because orderNumber is the wrong group as per API specification and should be placed in a different order. If we try to put (as in the PR) right after cvv2, the request is successful:

cURL:
Response:
cURL:
Response:
Authorize :
cURL:
Response:
Capture:
cURL:
Response:
cURL:
Response:
cURL:
Response:
Checklist
cargo +nightly fmt --allcargo clippy