merge token method documentation visa and mastercard #227
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
thejspr
reviewed
Jan 19, 2026
| * `clicktopay`: Click to Pay | ||
| * `token[m4m]`: Mastercard Digital Enablement Service (MDES) for Merchants (M4M) | ||
| * `token[vts]`: Visa Token Service (VTS) | ||
| * `token`: Visa and Mastercard |
Contributor
There was a problem hiding this comment.
Historically, I think we have add new fields/sections separately, and marked existing ones as deprecated. Then only once we fully deprecate them in the API, we go and remove the documentation. This way, parthers can still see documentation for their current integrations.
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.
issue: https://github.com/clearhaus/issues-pci/issues/5716
we dont want parters to have to specify if its m4m scof or vts when its a token auth