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

Support stored credentials in Cybersource #3185

Merged

Conversation

therufs
Copy link
Contributor

@therufs therufs commented Apr 2, 2019

There are still a few failing remote tests; these seem to fail in the current version as well.

@therufs therufs self-assigned this Apr 2, 2019
@therufs therufs requested a review from a team April 2, 2019 18:27
Copy link
Contributor

@curiousepic curiousepic 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! I'm wondering if we need any guards around stored cred hash fields being nil or not present, but otherwise 👍

@therufs therufs force-pushed the ECS-218-cyber-source-stored-creds branch from ef6e613 to 4287527 Compare April 8, 2019 15:17
@therufs therufs merged commit 4287527 into activemerchant:master Apr 8, 2019
Copy link

@przemyslawhaptas przemyslawhaptas left a comment

Choose a reason for hiding this comment

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

Hey @therufs, thank you for the PR!
I've been trying to make CyberSecure work with Stored Credentials and there are two things bugging me, could you give me a hand?

  1. Since there are payment flows that use #purchase instead of #authorize + #capture combo, what is the reason Stored Credentials support wasn't introduced in this PR? Is it because you just needed to support authorize in your project or perhaps this is a complete solution and there is some reason purchase shouldn't use Stored Credentials at all?
  2. I wasn't able to get a ccAuthReply_paymentNetworkTransactionID field from any #authorize call, does it work on your side? The only gateway method that returns the field in its response is #store, am I missing something here?

Thanks!

:initial_transaction => true,
:network_transaction_id => ''
}
assert response = @gateway.authorize(@amount, @credit_card, @options)

Choose a reason for hiding this comment

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

@therufs as I understand it, one of the points of the first request is to obtain the network_transaction_id to be used with subsequent ones, correct? Unfortunately, it seems to not be the case, at least not with my cybersource account. Would you mind checking if the response has the field on your side?

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.

3 participants