Ebanx: Add network token support #5263
Merged
+102
−3
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
Buitragox
commented
Sep 13, 2024
| @@ -187,7 +195,8 @@ def test_partial_refund | |||
| def test_failed_refund | |||
| response = @gateway.refund(@amount, '') | |||
| assert_failure response | |||
| assert_match('Parameter hash not informed', response.message) | |||
| assert_equal 'Parameters hash or merchant_payment_code not informed', response.message | |||
| assert_equal 'BP-REF-1', response.error_code | |||
There was a problem hiding this comment.
The error description for error BP-REF-1 changed. The docs appear to be outdated.
Buitragox
commented
Sep 13, 2024
| response = @gateway.purchase(@amount, @network_token, @options) | ||
| assert_failure response | ||
| assert_equal 'Field network_token_expire_date is invalid', response.message | ||
| assert_equal 'BP-DR-136', response.error_code |
There was a problem hiding this comment.
Error codes for network tokens are not present in the docs.
Buitragox
force-pushed
the
OPPS-29_ebanx_network_tokens
branch
from
d4bcb5e
to
2ac1399
Compare
Buitragox
force-pushed
the
OPPS-29_ebanx_network_tokens
branch
from
2ac1399
to
489c8a1
Compare
Summary: ------------------------------ Add network token support to ebanx gateway. Remote Test: ------------------------------ The test "test_successful_purchase_passing_processing_type_in_header" fails because of an invalid integration key. This test adds a header that routes the request to a different environment where the integration key is not valid. Documentation about this can be found [here](https://developer.ebanx.com/docs/integration/guides/integration-guide#header). 43 tests, 106 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 97.6744% passed Unit Tests: ------------------------------ 6026 tests, 80391 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed RuboCop: ------------------------------ 801 files inspected, no offenses detected
Buitragox
force-pushed
the
OPPS-29_ebanx_network_tokens
branch
from
489c8a1
to
60145d9
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.
Summary:
Add network token support to ebanx gateway.
Remote Test:
The test "test_successful_purchase_passing_processing_type_in_header" fails because of an invalid integration key.
This test adds a header that routes the request to a different environment where the integration key is not valid.
Documentation about this can be found here.
43 tests, 106 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 97.6744% passed
Unit Tests:
6026 tests, 80391 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed
RuboCop:
801 files inspected, no offenses detected