From 106fd4642521cd42b43ef6472e198859698ebb49 Mon Sep 17 00:00:00 2001 From: Mikkel Thingholm Date: Tue, 2 Jun 2026 14:11:17 +0200 Subject: [PATCH 1/2] Add payload and assurance data parameters for click to pay payment method --- .../authorizations_methods/token.md | 21 +++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/website/content/gateway/api_resources/authorizations/authorizations_methods/token.md b/website/content/gateway/api_resources/authorizations/authorizations_methods/token.md index 85a8c26..26716a2 100644 --- a/website/content/gateway/api_resources/authorizations/authorizations_methods/token.md +++ b/website/content/gateway/api_resources/authorizations/authorizations_methods/token.md @@ -24,6 +24,23 @@ Requirement of some parameters depends on the initiator of the transaction; a pa Click to Pay token payment method for both Visa and Mastercard CITs. {{% description_list %}} + +If 3-D Secure authentication was performed `ONBEHALF` as part of the Click to Pay flow, the following parameters can be provided: + +{{% description_term %}}clicktopay[payload] {{% regex %}}[\:json\:] {{% /regex %}} {{% /description_term %}} +{{% description_details %}} Full decrypted payload serialized as JSON, supplied as a string. The encrypted payload can be found in the `encryptedPayload` field in the Click to Pay checkout response. + +Example: `{"token":{"paymentToken":"",...}, "dynamicData":[{...}],...}` +{{% /description_details %}} + +{{% description_term %}}clicktopay[assurance_data] {{% regex %}}[\:json\:] {{% /regex %}} {{% /description_term %}} +{{% description_details %}} Full assurance data serialized as JSON, supplied as a string. The assurance data can be found in the `assuranceData` field in the Click to Pay checkout response. + +Example: `{"verificationData":[{"verificationType":"", "verificationMethod":"", "methodResults":{...},...},...], "eci":"",...}` +{{% /description_details %}} + +If 3-D Secure authentication was performed separately, the following parameters can be sent: + {{% description_term %}}clicktopay[tan] {{% regex %}}[0-9]{12,19}{{% /regex %}}{{% /description_term %}} {{% description_details %}}Token Account Number (TAN) of the token to charge. {{% /description_details %}} @@ -53,7 +70,7 @@ Click to Pay token payment method for both Visa and Mastercard CITs. #### Method: token -Token payment method for both For both Visa Token Service (VTS) and Mastercard Digital Enablement Service (MDES) +Token payment method for both Visa Token Service (VTS) and Mastercard Digital Enablement Service (MDES) The required values are found in: - the VTS provision token response. @@ -105,7 +122,7 @@ The required values are found in: {{% description_term %}}token[tav] {{% regex %}}[:base64:]{28}{{% /regex %}}{{% /description_term %}} -{{% description_details %}}Token Authentication Value (TAV) also know as token cryptogram. +{{% description_details %}}Token Authentication Value (TAV) also known as token cryptogram. Visa specific name: Token Authentication Verification Value (TAVV). From 76c3063304fd6c1f70a1ab23dda4acae279d0162 Mon Sep 17 00:00:00 2001 From: Mikkel Thingholm Date: Thu, 4 Jun 2026 09:08:58 +0200 Subject: [PATCH 2/2] Enhance Click to Pay documentation by adding details for two interfaces --- .../authorizations_methods/token.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/website/content/gateway/api_resources/authorizations/authorizations_methods/token.md b/website/content/gateway/api_resources/authorizations/authorizations_methods/token.md index 26716a2..80e2415 100644 --- a/website/content/gateway/api_resources/authorizations/authorizations_methods/token.md +++ b/website/content/gateway/api_resources/authorizations/authorizations_methods/token.md @@ -23,10 +23,11 @@ Requirement of some parameters depends on the initiator of the transaction; a pa Click to Pay token payment method for both Visa and Mastercard CITs. -{{% description_list %}} -If 3-D Secure authentication was performed `ONBEHALF` as part of the Click to Pay flow, the following parameters can be provided: +Click to Pay can be used through two interfaces. +The first interface uses the payloads from the checkout response: +{{% description_list %}} {{% description_term %}}clicktopay[payload] {{% regex %}}[\:json\:] {{% /regex %}} {{% /description_term %}} {{% description_details %}} Full decrypted payload serialized as JSON, supplied as a string. The encrypted payload can be found in the `encryptedPayload` field in the Click to Pay checkout response. @@ -37,9 +38,19 @@ Example: `{"token":{"paymentToken":"",...}, "dynamicData":[{...}],...}` {{% description_details %}} Full assurance data serialized as JSON, supplied as a string. The assurance data can be found in the `assuranceData` field in the Click to Pay checkout response. Example: `{"verificationData":[{"verificationType":"", "verificationMethod":"", "methodResults":{...},...},...], "eci":"",...}` + +{{% regex_optional %}}Required for all Visa transactions. For Mastercard, required only when 3‑D Secure authentication was performed `ONBEHALF` {{% /regex_optional %}} +{{% /description_details %}} + +{{% description_term %}}clicktopay[3dsecure] {{% regex %}}dictionary{{% /regex %}}{{% /description_term %}} +{{% description_details %}}See [Authentication: [3dsecure]](#authentication-3dsecure-v2). +{{% regex_optional %}}Optional. Should be sent if 3D-Secure authentication was done separately{{% /regex_optional %}} {{% /description_details %}} +{{% /description_list %}} -If 3-D Secure authentication was performed separately, the following parameters can be sent: +The second interface uses raw values: + +{{% description_list %}} {{% description_term %}}clicktopay[tan] {{% regex %}}[0-9]{12,19}{{% /regex %}}{{% /description_term %}} {{% description_details %}}Token Account Number (TAN) of the token to charge.