FINANCIAL TRANSACTION METHOD AND SYSTEM HAVING AN UPDATE MECHANISM
First Claim
1. Method of managing a payment device in a financial transaction between an issuer node and a payment device via a terminal across a payment network, update information of the financial transaction routed through the payment network to the payment device being subject to errors and/or a bandwidth limitation, each financial transaction being routed at an application layer from the issuer node to the terminal, and components of the financial transaction being transferred from the terminal to the payment device, the payment device being issued by an issuer or an agent of the issuer, at least a first component of the financial transaction being delivery of the update information and being transferred by the terminal to the payment device, the at least one first component of the financial transaction requiring at least one operation of recording the update information in non-volatile memory on the payment device conditional on at least a second component of the financial transaction, the second component including an outcome requested by the issuer or the agent of the issuer, said method comprising the payment device executing the steps of:
- a) on receiving the update information, provisionally storing the update information on the payment device without losing prior values corresponding to the update information; and
b) on receiving the at least one second component, applying the update information to non-volatile memory on the payment device only if 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.
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. Method of managing a payment device in a financial transaction between an issuer node and a payment device via a terminal across a payment network, update information of the financial transaction routed through the payment network to the payment device being subject to errors and/or a bandwidth limitation, each financial transaction being routed at an application layer from the issuer node to the terminal, and components of the financial transaction being transferred from the terminal to the payment device, the payment device being issued by an issuer or an agent of the issuer, at least a first component of the financial transaction being delivery of the update information and being transferred by the terminal to the payment device, the at least one first component of the financial transaction requiring at least one operation of recording the update information in non-volatile memory on the payment device conditional on at least a second component of the financial transaction, the second component including an outcome requested by the issuer or the agent of the issuer, said method comprising the payment device executing the steps of:
-
a) on receiving the update information, provisionally storing the update information on the payment device without losing prior values corresponding to the update information; and b) on receiving the at least one second component, applying the update information to non-volatile memory on the payment device only if 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. - 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 a payment device via a terminal across a payment network, update information of the financial transaction routed through the payment network to the payment device being subject to errors and/or a bandwidth limitation, each financial transaction being routed at an application layer from the issuer node to the terminal, and components of the financial transaction being transferred from the terminal to the payment device, the payment device being issued by an issuer or an agent of the issuer, at least a first component of the financial transaction being delivery of the update information and being transferred by the terminal to the payment device, the at least one first component of the financial transaction requiring at least one operation of recording the update information in non-volatile memory on the payment device conditional on at least a second component of the financial transaction, the second component including an outcome requested by the issuer or the agent of the issuer, wherein the payment device is adapted so that:
-
a) on receiving the update information, the payment device provisionally stores the update information on the payment device without losing prior values corresponding to the update information; and b) on receiving the at least one second component, the payment device applies the update information to non-volatile memory on the payment device only if 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. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
-
25. A payment device having volatile and non-volatile 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 adapted to process each financial transaction delivered at an application layer from the issuer node to the terminal, whereas components of the financial transaction are transferred from the terminal to the payment device, the payment device being issued by an issuer or an agent of the issuer, at least a first component of the financial transaction being delivery of update information and being received by the payment device from the terminal, the at least one first component of the financial transaction requiring at least one operation of recording the update information in non-volatile memory on the payment device conditional on at least a second component of the financial transaction, the second component including an outcome requested by the issuer or the agent of the issuer, wherein the payment device is adapted so that:
-
a) on receiving the update information, the payment device provisionally stores the update information on the payment device without losing prior values corresponding to the update information; and b) on receiving the at least one second component, the payment device applies the update information to non-volatile memory on the payment device only if 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.
-
Specification