You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Model/PtsV2PaymentsPost201ResponseConsumerAuthenticationInformation.cs
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ public partial class PtsV2PaymentsPost201ResponseConsumerAuthenticationInformati
39
39
/// <param name="AcsUrl">URL for the card-issuing bank’s authentication form that you receive when the card is enrolled. The value can be very large. .</param>
40
40
/// <param name="AuthenticationPath">Indicates what displays to the customer during the authentication process. This field can contain one of these values: - `ADS`: (Card not enrolled) customer prompted to activate the card during the checkout process. - `ATTEMPTS`: (Attempts processing) Processing briefly displays before the checkout process is completed. - `ENROLLED`: (Card enrolled) the card issuer’s authentication window displays. - `UNKNOWN`: Card enrollment status cannot be determined. - `NOREDIRECT`: (Card not enrolled, authentication unavailable, or error occurred) nothing displays to the customer. The following values can be returned if you are using rules-based payer authentication. - `RIBA`: The card-issuing bank supports risk-based authentication, but whether the cardholder is likely to be challenged cannot be determined. - `RIBA_PASS`: The card-issuing bank supports risk-based authentication and it is likely that the cardholder will not be challenged to provide credentials, also known as _silent authentication_. For details about possible values, see `pa_enroll_authentication_path` field description and \"Rules-Based Payer Authentication\" in [CyberSource Payer Authentication Using the SCMP API.] (https://apps.cybersource.com/library/documentation/dev_guides/Payer_Authentication_SCMP_API/html/) .</param>
41
41
/// <param name="AuthorizationPayload">The Base64 encoded JSON Payload of CB specific Authorization Values returned in the challenge Flow .</param>
42
-
/// <param name="AuthenticationTransactionId">Payer authentication transaction identifier passed to link the check enrollment and validate authentication messages. .</param>
42
+
/// <param name="AuthenticationTransactionId">Payer authentication transaction identifier is used to link the check enrollment and validate authentication messages. For Rupay, this field should be passed as request only for Resend OTP use case. .</param>
43
43
/// <param name="CardholderMessage">Text provided by the ACS/Issuer to Cardholder during a Frictionless or Decoupled transaction.The Issuer can provide information to Cardholder. For example, “Additional authentication is needed for this transaction, please contact (Issuer Name) at xxx-xxx-xxxx.”. The Issuing Bank can optionally support this value. .</param>
44
44
/// <param name="Cavv">Unique identifier generated by the card-issuing bank for Visa, American Express, JCB, Diners Club, and Discover transactions after the customer is authenticated. The value is in base64. When you request the card authorization service, CyberSource automatically converts the value, not the field name, to the format required by your payment processor. .</param>
45
45
/// <param name="CavvAlgorithm">Field that is returned only when the CAVV is generated, which occurs when paresStatus contains the values Y (successful authentication) or A (attempted authentication). If you use the ATOS processor, send the value of this field in the `cavv_algorithm` request field of the authorization service. This field contains one of these values: - `2`: Visa, American Express, JCB, Diners Club, and Discover - `3`: Mastercard .</param>
@@ -164,9 +164,9 @@ public partial class PtsV2PaymentsPost201ResponseConsumerAuthenticationInformati
164
164
publicstringAuthorizationPayload{get;set;}
165
165
166
166
/// <summary>
167
-
/// Payer authentication transaction identifier passed to link the check enrollment and validate authentication messages.
167
+
/// Payer authentication transaction identifier is used to link the check enrollment and validate authentication messages. For Rupay, this field should be passed as request only for Resend OTP use case.
168
168
/// </summary>
169
-
/// <value>Payer authentication transaction identifier passed to link the check enrollment and validate authentication messages. </value>
169
+
/// <value>Payer authentication transaction identifier is used to link the check enrollment and validate authentication messages. For Rupay, this field should be passed as request only for Resend OTP use case. </value>
0 commit comments