CyberSourceRest: support TMS store/unstore, and void of captures/refunds #5369
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
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.
Description
This pull request enhances the
CyberSourceRestgateway to support Token Management Service (TMS) token creation and unstoring, providing closer parity with theCyberSourcegateway SOAP API implementation. This requires expanding the API url path to support not only thepts/(payments) API, but also thetms/(token) API as well. This also requires extending thecommitmethod to support not only HTTPPOSTbut also other HTTP verbs, likeDELETE, which is the verb used for unstoring.The
voidmethod is also extended to support voiding of not just authorizations, but also captures, payments, and refunds.Unit Tests
Remote Tests
Rubocop