# US 2020/0402027 A1 · Value transfer card management system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0402027 A1
- Document ID: US20200402027A1
- Status: Published application
- Kind: A1
- Application number: 16/445,531
- Filed: 2019-06-19
- Published: 2020-12-24
- Earliest claimed: 2019-06-19
- Assignees: The Toronto-Dominion Bank
- Applicants: The Toronto-Dominion Bank
- Inventors: Raj Kumar Choudhary
- Web page: https://patentgrep.com/patent/US20200402027A1

## CPC

- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/3263: {characterised by activation or deactivation of payment capabilities}
- G06Q 20/341: {Active cards, i.e. cards including their own processing means, e.g. including an IC or chip}
- G06Q 20/351: {Virtual cards}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

In an aspect, a computing system is configured to: obtain, from a transfer rail server, stored card data, the stored card data identifying one or more entities having a stored representation of a value transfer card; obtain, from the transfer rail server, data indicating a time of last use of the value transfer card by one or more of the identified entities; identify a dormant entity based on the data indicating the time of last use of the value transfer card by the one or more of the identified entities; send, to a client device associated with the value transfer card, a notification providing a prompt to disable the value transfer card for the dormant entity; receive a command; and disable the value transfer card for the dormant entity to prevent further use of the value transfer card by the dormant entity.

## Claims

### Claim 1

A computing system comprising:
a communications module;
a processor coupled to the communications module; and
a memory coupled to the processor, the memory storing processor-executable instructions which, when executed, configure the processor to:
obtain, via the communications module and from a transfer rail server, stored card data, the stored card data identifying one or more entities having a stored representation of a value transfer card;
obtain, via the communications module and from the transfer rail server, data indicating a time of last use of the value transfer card by one or more of the identified entities;
identify a dormant entity based on the data indicating the time of last use of the value transfer card by the one or more of the identified entities;
send, via the communications module and to a client device associated with the value transfer card, a notification of the dormant entity, the notification providing a prompt to disable the value transfer card for the dormant entity;
receive, via the communications module and from the client device, a command in response to the notification; and
when the command includes a request to disable the value transfer card for the dormant entity, disable the value transfer card for the dormant entity to prevent further use of the value transfer card by the dormant entity.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein identifying a dormant entity based on the data indicating the time of last use comprises performing a threshold-based comparison based on a time of last use and a current date.

### Claim 3 (depends on 2)

The computing system of claim 2, wherein the threshold-based comparison is performed based on a first threshold and wherein the instructions further configure the processor to:
when the command is not a request to disable the value transfer card for the dormant entity:
obtain, from the transfer rail server and via the communications module, further data indicating an updated time of last use of the value transfer card by one or more of the identified entities; and
determine that the dormant entity for which the notification was sent has entered a further dormancy period by performing a threshold-based comparison based on the updated time of last use, the current date, and a second threshold, wherein the second threshold represents a longer time period than the first threshold.

### Claim 4 (depends on 3)

The computing system of claim 3, wherein the instructions further configure the processor to:
in response to determining that the dormant entity has entered a further dormancy period, automatically disable the value transfer card for the dormant entity.

### Claim 5 (depends on 3)

The computing system of claim 3, wherein the instructions further configure the processor to:
in response to determining that the dormant entity has entered a further dormancy period, send a further notification to the client device associated with the value transfer card, the further notification providing a further prompt to disable the value transfer card for the dormant entity.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein the command is a snooze command and wherein the instructions further configure the processor to, after receiving the snooze command:
following a snooze period, determine, by obtaining further data from the transfer rail server, that the dormant entity has remained dormant during the snooze period; and
send a further notification of the dormant entity to the client device associated with the value transfer card, the further notification providing a further prompt to disable the value transfer card for the dormant entity.

### Claim 7 (depends on 6)

The computing system of claim 6, wherein the snooze command includes the snooze period and wherein the snooze period is based on input received at the client device.

### Claim 8 (depends on 1)

The computing system of claim 1, wherein the instructions further configure the processor to:
receive, from the client device, input of a threshold for identifying a dormant entity, and wherein the identifying is based on the threshold.

### Claim 9 (depends on 1)

The computing system of claim 1, wherein the instructions further configure the processor to:
provide user interface data to the client device, the user interface data causing the client device to display a user interface that includes an entity listing identifying entities having a stored representation of a value transfer card, the entity listing including the dormant entity and the user interface including a dormant card indication in association with the dormant entity.

### Claim 10 (depends on 1)

The computing system of claim 1, wherein the dormant entity is an entity having stored a tokenized representation of the value transfer card, and wherein notifications of dormant entities are only sent for entities having stored tokenized representations of the value transfer card.

### Claim 11

A method comprising:
obtaining, from a transfer rail server, stored card data, the stored card data identifying one or more entities having a stored representation of a value transfer card;
obtaining, from the transfer rail server, data indicating a time of last use of the value transfer card by one or more of the identified entities;
identifying a dormant entity based on the data indicating the time of last use of the value transfer card by the one or more of the identified entities;
sending, to a client device associated with the value transfer card, a notification of the dormant entity, the notification providing a prompt to disable the value transfer card for the dormant entity;
receiving, from the client device, a command in response to the notification; and
when the command includes a request to disable the value transfer card for the dormant entity, disabling the value transfer card for the dormant entity to prevent further use of the value transfer card by the dormant entity.

### Claim 12 (depends on 11)

The method of claim 11, wherein identifying a dormant entity based on the data indicating the time of last use comprises performing a threshold-based comparison based on a time of last use and a current date.

### Claim 13 (depends on 12)

The method of claim 12, wherein the threshold-based comparison is performed based on a first threshold and wherein the method further includes:
when the command is not a request to disable the value transfer card for the dormant entity:
obtaining, from the transfer rail server, further data indicating an updated time of last use of the value transfer card by one or more of the identified entities; and
determining that the dormant entity for which the notification was sent has entered a further dormancy period by performing a threshold-based comparison based on the updated time of last use, the current date, and a second threshold, wherein the second threshold represents a longer time period than the first threshold.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
in response to determining that the dormant entity has entered a further dormancy period, automatically disabling the value transfer card for the dormant entity.

### Claim 15 (depends on 13)

The method of claim 13, further comprising:
in response to determining that the dormant entity has entered a further dormancy period, sending a further notification to the client device associated with the value transfer card, the further notification providing a further prompt to disable the value transfer card for the dormant entity.

### Claim 16 (depends on 11)

The method of claim 11, wherein the command is a snooze command and wherein the method further includes, after receiving the snooze command:
following a snooze period, determining, by obtaining further data from the transfer rail server, that the dormant entity has remained dormant during the snooze period; and
sending a further notification of the dormant entity to the client device associated with the value transfer card, the further notification providing a further prompt to disable the value transfer card for the dormant entity.

### Claim 17 (depends on 11)

The method of claim 11, wherein the snooze command includes the snooze period and wherein the snooze period is based on input received at the client device.

### Claim 18 (depends on 11)

The method of claim 11, further comprising:
receiving, from the client device, input of a threshold for identifying a dormant entity, and wherein the identifying is based on the threshold.

### Claim 19 (depends on 10)

The method of claim 10, further comprising:
providing user interface data to the client device, the user interface data causing the client device to display a user interface that includes an entity listing identifying entities having a stored representation of a value transfer card, the entity listing including the dormant entity and the user interface including a dormant card indication in association with the dormant entity.

### Claim 20

A non-transitory computer-readable storage medium comprising processor-executable instructions which, when executed, configure a processor to:
obtain, from a transfer rail server, stored card data, the stored card data identifying one or more entities having a stored representation of a value transfer card;
obtain, from the transfer rail server, data indicating a time of last use of the value transfer card by one or more of the identified entities;
identify a dormant entity based on the data indicating the time of last use of the value transfer card by the one or more of the identified entities;
send, to a client device associated with the value transfer card, a notification of the dormant entity, the notification providing a prompt to disable the value transfer card for the dormant entity;
receive, from the client device, a command in response to the notification; and
when the command includes a request to disable the value transfer card for the dormant entity, disable the value transfer card for the dormant entity to prevent further use of the value transfer card by the dormant entity.
