Skip to content
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

Credorax: Add support for gateway card validation #5332

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rachelkirk
Copy link
Contributor

This change allows the cardholder_name_inquiry flag to be sent. If set to true, it will trigger first and last name data to be sent for c22, and c23. $0 auth transactions to validate cards also require the value for a9 to be set to 5.

Remote Tests:
52 tests, 176 assertions, 6 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 88.4615% passed
*6 failing tests also failing on master

Unit Tests
83 tests, 399 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed

@rachelkirk rachelkirk requested a review from a team November 11, 2024 20:47
@@ -164,6 +164,7 @@ def authorize(amount, payment_method, options = {})
add_3ds_2_optional_fields(post, options)
add_echo(post, options)
add_submerchant_id(post, options)
add_cardholder_name_inquiry(post, options)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this should come after add_stored_credential in the order of sub-methods?

The reason being that a9 is also set in that submethod, either by applying the transaction_type that is passed in, or defaulting to 9 if it's a CIT.

In this current order, I think there's a risk that the a9 value we're setting would get overwritten 😬

This change allows the `cardholder_name_inquiry` flag to be sent. If set to true, it will trigger first and last name data to be sent for c22, and c23. $0 auth transactions to validate cards also require the value for a9 to be set to 5.

Remote Tests:
54 tests, 176 assertions, 6 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
88.4615% passed

Unit Tests
83 tests, 399 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants