Financial transaction method and system having an update mechanism
First Claim
1. A method of managing a payment device in a financial transaction between an issuer node and the payment device via a terminal across a payment network, the payment device being issued by an issuer or an agent of the issuer, the financial transaction being routed at an application layer from the issuer node to the terminal, comprising:
- determining, by the issuer node, Issuer Authentication Data and extended Issuer Authentication Data associated with the payment device, wherein the extended Issuer Authentication Data comprises one or more updates to one or more updated values stored in a non-volatile memory of the payment device;
packaging, by the issuer node, the extended Issuer Authentication Data in a first component configured to be executed by the payment device prior to receipt of a second component, wherein the first component comprises a first byte capacity;
packaging, by the issuer node, the Issuer Authentication Data in a second component configured for completing the financial transaction and applying the Issuer Authentication Data, wherein the second component comprises a second byte capacity which is less than the first byte capacity of the first component;
routing, by the issuer node, the first component through the payment network to the payment device;
causing the payment device, upon receiving the first component, to provisionally store the extended Issuer Authentication Data in a volatile memory of the payment device without losing prior values corresponding to the extended Issuer Authentication Data stored in the non-volatile memory of the payment device; and
causing the payment device, upon receiving the second component, to apply the extended Issuer Authentication Data to the non-volatile memory on the payment device to replace the prior values with the one or more updated values when the payment device has issued a confirmation that the financial transaction has been completed in accordance with the outcome requested by the issuer or the agent and upon successful verification of the Issuer Authentication Data.
1 Assignment
0 Petitions
Accused Products
Abstract
A payment device and method and system for using the payment device is described capable of utilizing a pre-authorized amount on existing infrastructure, including POS terminals or for using offline pre-paid products on this infrastructure. The updates for the pre-authorized or offline prepaid products can be sent by the issuer and applied by the card contemporaneously with the card'"'"'s processing of the issuer authentication data but without requiring any additional bytes in the issuer authentication data. The updates performed by the issuer can be larger and more extensive than could be achieved by using any available space in the issuer authentication data.
-
Citations
25 Claims
-
1. A method of managing a payment device in a financial transaction between an issuer node and the payment device via a terminal across a payment network, the payment device being issued by an issuer or an agent of the issuer, the financial transaction being routed at an application layer from the issuer node to the terminal, comprising:
-
determining, by the issuer node, Issuer Authentication Data and extended Issuer Authentication Data associated with the payment device, wherein the extended Issuer Authentication Data comprises one or more updates to one or more updated values stored in a non-volatile memory of the payment device; packaging, by the issuer node, the extended Issuer Authentication Data in a first component configured to be executed by the payment device prior to receipt of a second component, wherein the first component comprises a first byte capacity; packaging, by the issuer node, the Issuer Authentication Data in a second component configured for completing the financial transaction and applying the Issuer Authentication Data, wherein the second component comprises a second byte capacity which is less than the first byte capacity of the first component; routing, by the issuer node, the first component through the payment network to the payment device; causing the payment device, upon receiving the first component, to provisionally store the extended Issuer Authentication Data in a volatile memory of the payment device without losing prior values corresponding to the extended Issuer Authentication Data stored in the non-volatile memory of the payment device; and causing the payment device, upon receiving the second component, to apply the extended Issuer Authentication Data to the non-volatile memory on the payment device to replace the prior values with the one or more updated values when the payment device has issued a confirmation that the financial transaction has been completed in accordance with the outcome requested by the issuer or the agent and upon successful verification of the Issuer Authentication Data. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A system for managing a payment device in a financial transaction between an issuer node and the payment device via a terminal across a payment network, the payment device being issued by an issuer or an agent of the issuer, the financial transaction being routed at an application layer from the issuer node to the terminal, comprising:
-
the issuer node, configured for, determining Issuer Authentication Data and extended Issuer Authentication Data, associated with the payment device, wherein the extended Issuer Authentication Data comprises one or more updates to one or more updated values stored in a non-volatile memory of the payment device; packaging the extended Issuer Authentication Data in a first component configured to be executed by the payment device prior to receipt of a second component, wherein the first component comprises a first byte capacity; packaging the Issuer Authentication Data in a second component configured for completing the financial transaction and applying the Issuer Authentication Data, wherein the second component comprises a second byte capacity which is less than the first byte capacity of the first component; routing the first component through the payment network to the payment device;
the payment device, configured for,upon receiving the first component, to provisionally store the extended Issuer Authentication Data in a volatile memory of the payment device without losing prior values corresponding to the extended Issuer Authentication Data stored in the non-volatile memory of the payment device; and upon receiving the second component, to apply the extended Issuer Authentication Data to the non-volatile memory on the payment device to replace the prior values with the one or more updated values when the payment device has issued a confirmation that the financial transaction has been completed in accordance with the outcome requested by the issuer or the agent and upon successful verification of the Issuer Authentication Data. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
-
25. A payment device having a volatile memory and a nonvolatile memory, the payment device being for use in a financial transaction between an issuer node and the payment device via a terminal across a payment network, the payment device being issued by an issuer or an agent of the issuer, the financial transaction being routed at an application layer from the issuer node to the terminal, wherein the payment device is configured for:
-
receiving, from the issuer node, a first component through the payment network to the payment device, wherein, the issuer node determined Issuer Authentication Data and extended Issuer Authentication Data, associated with the payment device, wherein the extended Issuer Authentication Data comprises one or more updates to one or more updated values stored in a non-volatile memory of the payment device, and wherein the issuer node packaged the extended Issuer Authentication Data in a first component configured to be executed by the payment device prior to receipt of a second component, wherein the first component comprises a first byte capacity, and wherein the issuer node packaged the Issuer Authentication Data in a second component configured for completing the financial transaction and applying the Issuer Authentication Data, wherein the second component comprises a second byte capacity which is less than the first byte capacity of the first component; upon receiving the first component, provisionally storing the extended Issuer Authentication Data in a volatile memory of the payment device without losing prior values corresponding to the extended Issuer Authentication Data stored in the non-volatile memory of the payment device; and upon receiving the second component, applying the extended Issuer Authentication Data to the non-volatile memory on the payment device to replace the prior values with the one or more updated values when the payment device has issued a confirmation that the financial transaction has been completed in accordance with the outcome requested by the issuer or the agent and upon successful verification of the Issuer Authentication Data.
-
Specification