Payeezy: Pull cardholder name from billing address #5006
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DustinHaefele
approved these changes
Jan 12, 2024
Thanks! They're failing because Ruby needs to be updated |
If payment method doesn't have name then pull it from the billing address for credit card cardholder name. Remote: 52 tests, 212 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 98.0769% passed Unit: 51 tests, 235 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed
almalee24
force-pushed
the
update_payeezy_card_name
branch
from
044a49d
to
acb138e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If payment method doesn't have name then pull it from the billing address for credit card cardholder name.
Remote:
52 tests, 212 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 98.0769% passed
Unit:
51 tests, 235 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed