-
Notifications
You must be signed in to change notification settings - Fork 3
merge token method documentation visa and mastercard #227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
peterklogborg
wants to merge
3
commits into
master
Choose a base branch
from
allow-authorization-request-tokens-without-specifing-m4m-or-vts
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
110 changes: 110 additions & 0 deletions
110
website/content/gateway/api_reference/deprecated/deprecated.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,110 @@ | ||
| --- | ||
| title: "deprecated" | ||
| date: 2026-01-27T09:37:22+01:00 | ||
| anchor: "deprecated" | ||
| weight: 360 | ||
| --- | ||
| ## Deprecated | ||
| This section included snippets of the old documentation. As long as its available in this section its | ||
| still a valid way to work with the api. | ||
| ### M4m and Vts snippet from 2025 | ||
| #### Method: token | ||
|
|
||
| * `token[m4m]`: Mastercard Digital Enablement Service (MDES) for Merchants (M4M) | ||
| * `token[vts]`: Visa Token Service (VTS) | ||
|
|
||
| Requirement of some parameters depends on the initiator of the transaction; a parameter might be required for cardholder-initiated transactions (CITs) and otherwise optional. See the details for each parameter. | ||
|
|
||
| {{% notice %}} | ||
| **Notice**: Signing is required to use the `token` payment method. | ||
| {{% /notice %}} | ||
|
|
||
| #### Method: token[m4m] | ||
|
|
||
| The required values are found in either the MDES `transact` response or the Secure Card on File (SCOF) `checkout` response. | ||
|
|
||
| {{% description_list %}} | ||
| {{% description_term %}}token[m4m][tan] {{% regex %}}[0-9]{12,19}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Token Account Number (TAN) of the token to charge. | ||
|
|
||
| Found in `encryptedPayload.encryptedData.accountNumber` (MDES) or `encryptedPayload.token.paymentToken` (SCOF). | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[m4m][expire_month] {{% regex %}}[0-9]{2}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Expiry month of token to charge. | ||
|
|
||
| Found in `encryptedPayload.encryptedData.applicationExpiryDate` (MDES) or `encryptedPayload.token.tokenExpirationMonth` (SCOF). | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[m4m][expire_year] {{% regex %}}20[0-9]{2}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Expiry year of token to charge. | ||
|
|
||
| Found in `encryptedPayload.encryptedData.applicationExpiryDate` (MDES) or `encryptedPayload.token.tokenExpirationYear` (SCOF). | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[m4m][tav] {{% regex %}}[:base64:]{28}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Token Authentication Value (TAV). Also known as token cryptogram and Digital Secure Remote Payments (DSRP) cryptogram. | ||
|
|
||
| Only DSRP cryptograms are supported. The value must start with `[A-P]` to be a DSRP cryptogram. | ||
|
|
||
| Found in `encryptedPayload.encryptedData.de48se43Data` (MDES) or `encryptedPayload.dynamicData.dynamicDataValue` (SCOF). | ||
| {{% regex_optional %}}Required for CITs. For MITs it shall only be included on the first, tokenized transaction or if there is a change to the token.{{% /regex_optional %}} | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[m4m][rcai] {{% regex %}}[:base64:]{1..150}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Remote Commerce Acceptor Identifier. | ||
|
|
||
| Merchant identifier such as business website URL or reverse domain name (e.g. com.example.www). The identifier must be encoded as Base64. | ||
|
|
||
| Found in `customOutputData.remoteCommerceAcceptorIdentifier` (SCOF). (Not available in MDES.) | ||
| {{% regex_optional %}}Optional.{{% /regex_optional %}} | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[m4m][3dsecure][v2] {{% regex %}}dictionary{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}See [Authentication: [3dsecure][v2]](#authentication-3dsecure-v2). | ||
| {{% regex_optional %}}Optional{{% /regex_optional %}} | ||
| {{% /description_details %}} | ||
| {{% /description_list %}} | ||
|
|
||
| #### Method: token[vts] | ||
|
|
||
| The required values are found in the VTS provision token response. | ||
|
|
||
| {{% description_list %}} | ||
| {{% description_term %}}token[vts][tan] {{% regex %}}[0-9]{12,19}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Token Account Number (TAN) of the token to charge. | ||
|
|
||
| Found in `tokenInfo.encTokenInfo`. | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[vts][expire_month] {{% regex %}}[0-9]{2}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Expiry month of token to charge. | ||
|
|
||
| Found in `tokenInfo.expirationDate.month`. | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[vts][expire_year] {{% regex %}}20[0-9]{2}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Expiry year of token to charge. | ||
|
|
||
| Found in `tokenInfo.expirationDate.year`. | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[vts][eci] {{% regex %}}0[57]{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Electronic Commerce Indicator. | ||
|
|
||
| Found in `cryptogramInfo.eci`. | ||
| {{% regex_optional %}}Required for CITs; otherwise optional (defaults to `07`).{{% /regex_optional %}} | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[vts][tav] {{% regex %}}[:base64:]{28}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}Token Authentication Value (TAV). Also known as token cryptogram and Token Authentication Verification Value (TAVV). | ||
|
|
||
| Found in `cryptogramInfo.cryptogram`. | ||
| {{% regex_optional %}}Required for CITs; otherwise optional.{{% /regex_optional %}} | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}token[vts][3dsecure][v2] {{% regex %}}dictionary{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}}See [Authentication: [3dsecure][v2]](#authentication-3dsecure-v2). | ||
| {{% regex_optional %}}Optional{{% /regex_optional %}} | ||
| {{% /description_details %}} | ||
| {{% /description_list %}} |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thejspr so i have added a 'deprecated' documentation section - which may should have been called legacy.
Situated beneath changes which include m4m and vts token in its entirety instead of using strike through.