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

SafeCharge: Support tokens #4948

Merged
merged 1 commit into from
Nov 28, 2023
Merged

SafeCharge: Support tokens #4948

merged 1 commit into from
Nov 28, 2023

Conversation

almalee24
Copy link
Contributor

Remote:
34 tests, 96 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed

Unit:
29 tests, 160 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed

@almalee24 almalee24 requested a review from a team November 7, 2023 19:41
Copy link
Contributor

@aenand aenand left a comment

Choose a reason for hiding this comment

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

Looks good! Can you update the commit message with a description of what you are adding and is this possible to test with some unit tests?


def add_network_token(post, payment, options)
post[:sg_CAVV] = payment.payment_cryptogram
post[:sg_ECI] = options[:three_d_secure] && options[:three_d_secure][:eci] || '05'
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be the ECI for the network token or the 3DS ECI value?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh that's a good question, probably the network token. Since this is not related to the ticket and it will need some additional testing I'll create a ticket for it.

@almalee24
Copy link
Contributor Author

Looks good! Can you update the commit message with a description of what you are adding and is this possible to test with some unit tests?

Yes, I'll do that.

@almalee24 almalee24 force-pushed the safe_charge_use_token branch 2 times, most recently from 1875239 to a72ea3d Compare November 10, 2023 19:56
Copy link
Contributor

@aenand aenand left a comment

Choose a reason for hiding this comment

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

LGTM :shipit:

Allow processing payments sith tokens. A token is returned by SafeCharge
in the previous response to represent the customers' credit card.

Remote:
34 tests, 96 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

Unit:
30 tests, 160 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed
@almalee24 almalee24 merged commit 7108e98 into master Nov 28, 2023
5 checks passed
@almalee24 almalee24 deleted the safe_charge_use_token branch November 28, 2023 16:38
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