PayU Latam: Add support for merchantBuyerId #3308
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
dtykocki
approved these changes
Aug 23, 2019
Unit tests: 4229 tests, 70420 assertions, 0 failures, 0 errors, 0 pendings, 2 omissions, 0 notifications 100% passed test/remote/gateways/remote_payu_latam_test.rb: 30 tests, 72 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed CE-95
jasonxp
force-pushed
the
ce-95-payu-latam-add-merchant-buyer-id-gsf
branch
from
5e98609
to
f9e7abf
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.
Like with all other PayU Latam buyer options, the
merchant_buyer_idfield can be passed at the top level of theoptionshash, or under thebuyerkey.