-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Ebanx: Add support for Stored Credentials #5223
Conversation
72eb60b
to
eb6b2f4
Compare
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.
One question, but the code looks great, and the test coverage is excellent.
@@ -50,6 +50,7 @@ def purchase(money, payment, options = {}) | |||
add_address(post, options) | |||
add_customer_responsible_person(post, payment, options) | |||
add_additional_data(post, options) | |||
add_stored_credentials(post, options) |
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 is possibly just me still learning stored credentials, but should this be added to authorize or captures as well? Or does this only work on a full purchase? Particularly for initial transactions.
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.
I forgot to add it in authorize but let be double check if we need it for capture
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.
I've added it to Authorize since this is only for ws/direct API
which is just Purchase & Authorize
eb6b2f4
to
be25155
Compare
Remote 39 tests, 95 assertions, 2 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 94.8718% passed
be25155
to
b789edf
Compare
No description provided.