This repository was archived by the owner on Apr 29, 2024. It is now read-only.
Support Cybersource Tokenization #260
Merged
Conversation
This file contains hidden or 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
|
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
ellenwei
reviewed
Aug 23, 2023
gateways/cybersource/cybersource.go
Outdated
| createdTokens[sleet.TokenTypePaymentIdentifier] = paymentInformation.InstrumentIdentifier.ID | ||
| } | ||
| if paymentInformation.ShippingAddress != nil { | ||
| createdTokens[sleet.TokenTypeShippingAddress] = paymentInformation.InstrumentIdentifier.ID |
There was a problem hiding this comment.
paymentInformation.ShippingAddress.ID
There was a problem hiding this comment.
Already fixed, I just noticed this as I was reading it a second time 😅
ellenwei
approved these changes
Aug 23, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 PR upgrade the CyberSource client to support tokenization using the CyberSource Token Management Service (TMS).
Client consumers can request to tokenize the information in an authorization request by setting the CyberSourceTokenization option with a list of token types they want to create. They can then retrieve the resulting tokens from the CreatedTokens field in the authorization response.
The external API was designed to be processor-agnostic, without using CyberSource-specific terms. While only the token types relevant to CyberSource were defined, they are designed to be generic and reusable for other processors and new token types.
Tests
I added two new unit tests to verify that the presence of the tokenization option in the request results in the addition of tokenization fields in the CyberSource authorization request.
I added an integration test to verify that a CyberSource account is configured for tokenization and can successfully tokenize all supported token types.