Visa Click to Pay

Merchants and Payment Service Providers

Release Notes

Visa Click to Pay

25.08

Documentation Changes

The following changes were made to documentation:

  • Added an emailAddress field to the Consumer object in the checkout() parameters and modified the mobileNumber and consumerIdentity fields' descriptions.
  • Clarified that when checking out with a new card and the Consumer Identity already exists, the checkout() method launches a Visa-hosted user interface to facilitate identity validation via a one-time passcode, similar to calling the idLookup(), initiateIdentityValidation() and completeIdentityValidation() methods.
  • In the authenticationResult field of the Authentication Response and the payloadRequested field of Authentication Preferences, changed the NOT_AUTHENTICATED value to NON_AUTHENTICATED.
  • Clarified that the pendingEvents and authenticationMethods fields in the Digital Card Data structure are identified as future enhancements; they are not currently implemented.
  • Clarified that the verificationMethod field in the Verification Data structure can contain string 01 for EMV 3-D Secure ACS.
  • In the Identity Lookup Examples section, provided an example for mobile number lookup.
  • In the Unbind App Instance example, changed the invocation code for consistency with other examples.

25.07

Interface Changes

The following changes were made to the interface:

  • Added support for Merchant Recognition Tokens (MRTs) and External Identity tokens in the isRecognized(), getSRCProfile(), and checkout() JavaScript methods, including new optional parameters (recognitionToken and idToken) in the isRecognized() method.
  • The checkout() method returns a system-generated recognition token representing a device or app bound to the SRC Profile if the consumer consented to be remembered.
  • Deprecated the shippingAddress and panExpirationYear in the "Unencrypted Payload Contents."

25.03

Interface Changes

The following changes were made to the interface:

  • Added support to allow mobile phone number to be used for Consumer Identity in the checkout() and identityLookup() JavaScript methods. The consumerIdentity structure's contents have been modified.
  • Added support to allow mobile phone number to be used for Masked Consumer Identity in the checkout() and getSrcProfile() JavaScript methods and Get Payload API. The maskedConsumerIdentity structure's contents have been modified.

Documentation Changes

The following changes were made to documentation:

  • Clarified that the consumer parameter checkout() is conditional; required when linking a new card.
  • Revised the values that can be in the dynamicDataType field of the PaymentOptions structure in the init() and checkout() parameters.
  • Revised the values that can be in the dynamicDataType field of the dynamicData structure in the unencrypted payload.
  • Added a "Checkout input when existing card is selected - Issuer OTP / Online Banking Version:" example for the checkout() API.
  • Added "Requirements to Initiate Authentication" section to the checkout() API description.
  • Provided additional information related to consumer identity in the "Requirements When Checking Out With a New Card" section of the checkout() API description.
  • Revised verificationEntity field values.
  • Added additional Method Results fields.
  • Updated the Identity Lookup Example.

25.01

Documentation Changes

The following changes were made to documentation:

  • Clarified that the the format of PhoneNumber structure's fields, countryCode and phoneNumber, follow the ITU E.164 recommendation. Only digits ( [0-9] ) are allowed and the combined fields' total length does not exceed 15 digits; leading zeroes for either field must be dropped.
  • Clarified the formats for the maskedMobileNumber and maskedConsumerIdentity fields.

24.10

Documentation Changes

The following changes were made to documentation:

  • Clarified that the windowRef checkout parameter is optional and provides additional context for the use of this parameter.
  • Clarified that the authenticationMethods field is an array containing one or more authentication method structures.
  • Clarified that the digitalCardData structure contains an authenticationMethods field, not an authenticationMethod field.
  • Clarified that the status field's value in the Masked Consumer structure can be ACTIVE, SUSPENDED, or LOCKED.

24.09

Documentation Changes

The following changes were made to documentation:

  • Clarified that the parameters provided to the identityLookup() method are in the consumerIdentity structure.
  • Removed extraneous values from the type parameter in the consumerIdentity structure.
  • Clarified that the name fields and mobile number field in the masked and raw Masked Consumer and Consumer structures are not returned by the getSrcProfile() method.
  • Clarified that the status in Digital Card Data only supports the ACTIVE status.

24.07

Interface Changes

The following changes were made to the interface:

  • Added a lastUsedCardTimestamp return parameter to the Identity Lookup JavaScript API.
  • Deprecated the authenticationContext Checkout parameter. All Authentication Context fields are deprecated; use the equivalent fields in DPA Transaction Options instead.
  • Added the following fields to DPA Transaction Options: authenticationPreferences, acquirerBIN, merchantName, recurringData, and acquirerMerchantId.
  • Added authenticationPreferences and recurringData structures.
  • Deprecated the following fields in DPA Transaction Options: transactionInstruction, numberOfPayments, purchaseDate, recurringEndDate, recurringFrequency, and authenticatedCredentialRequested.
  • Added the 3DS enum value to the authenticationMethodType field in Authentication Method and deprecated the MANAGED_AUTHENTICATION enum.

Documentation Changes

The following changes were made to documentation:

  • Changed the descriptive name of the identityLookup JavaScript API from "Identity Lookup Account by Consumer ID" to "Identity Lookup Using Consumer Identity."
  • Updated description for transactionAmount in DPA Transaction Options.
  • Updated examples for "Checkout input when new card is added – 3DS version" and "Checkout input when existing card is selected – 3DS version."

24.04

  • Clarified that the mobileNumber field in the checkout() parameters is required when adding a new card.
  • Changed the name of the mobileNumber field in the Masked Consumer structure to maskedMobileNumber and noted that it is not returned by the getSrcProfile() method.
  • Added an optional encryptedBillingAddress field to the checkout() method's parameters.
  • Added the IDENTITY_VALIDATION_REQUIRED error to the checkout() method.

Unified Click to Pay

24.10

Documentation Changes

The following changes were made to documentation:

  • Added clarifications for Cardholder Authentication Methods (3DS, Passkey, and CVV2)
  • Added clarifications for First Time User and Add Card scenarios for Visa

24.07

  • Initial Release of Unified Click to Pay