Device binding

This feature allows the Merchant to ask the Issuer to approve the binding between a COF digital card and a device.

The objective of this feature is to increase the assurance level of the digital card through end user verification.

The Issuer can optionally define rules to decline bindings from devices considered insecure. If a device matches one or more rules, D1 automatically declines the binding request. If the Issuer does not define any rules, binding requests are not declined and the Level of Trust remains YELLOW.

The following table lists the available rules. For more details, see the D1 onboarding phase.

Rule name	Description
Device types not trusted	The Issuer can select device types it does not trust. For example, devices of type WATCH.
Device manufacturer	The Issuer can list device manufacturers it does not trust.
Device manufacturer - OS version	If known, the Issuer can specify an OS version it does not trust.
Device manufacturer - FW version	If known, the Issuer can specify a firmware version it does not trust.

Caution

D1 can apply these rules only if VTS sends the required fields. Today, VTS does not guarantee any specific set of device data. Even if the Issuer defines a rule, D1 cannot ensure that the rule is applied systematically.

D1 manages this flow on behalf of the Issuer.

The following diagram shows a high-level flow and highlights the Issuer's involvement in the process.

High-level device binding flow.

The diagram references Approve with step-up authentication.

This is the same flow used for Tokenization processing, with the following exceptions:

• The Customer service ID&V method is not supported.
• The In-app ID&V method can be supported within the issuer application through the D1 SDK (please refer to the section In-app authentication for Visa CTF) or through an additional backend API that allows approval of the binding after the authentication has been completed successfully. This is depicted in the following diagram:

Note

The following field mappings apply:

• tokenReferenceID = digitalCardID
• deviceIndex = deviceReference