Mobile terminal incorporated with a credit card

• US 20030004876A1
• Filed: 06/29/2001
• Published: 01/02/2003
• Est. Priority Date: 06/29/2001
• Status: Abandoned Application

• Current Assignee: Leumi Partners Ltd. (Private Equity)
• Original Assignee: Leumi Partners Ltd. (Private Equity)
• Inventors: Jacobson, David
• Application Number:
  US09/897,780
• Publication Number:
  US 20030004876A1
• Time in Patent Office: Days
• US Class Current: 705/41
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/32 using wireless devices
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G07F 7/0886 the card reader being portable for interacting with a POS or ECR in realizing a payment transaction
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: H04M 15/48 Secure or trusted billing, e.g. trusted elements or encryption
• CPC Class Codes: H04M 17/00 Prepayment of wireline communication systems, wireless communication systems or telephone systems using a coded card to authorise calls from a telephone set H04M1/675
• CPC Class Codes: H04M 17/02 Coin-freed or check-freed systems , e.g. mobile- or card-operated phones, public telephones or booths
• CPC Class Codes: H04M 17/026 Constructional features
• CPC Class Codes: H04M 17/106 using commercial credit or debit cards
• CPC Class Codes: H04M 2017/14 using commercial credit/debit cards, e.g. VISA, AMEX
• CPC Class Codes: H04M 2215/0156 Secure and trusted billing, e.g. trusted elements, encryption, digital signature, codes or double check mechanisms to secure billing calculation and information
• CPC Class Codes: H04M 2215/32 Involving wireless systems

Abstract

Payment device including a mobile terminal and a financial data storage element, wherein the mobile terminal and the financial data storage element are logically associated, and wherein the financial data storage element is coupled to the mobile terminal.

Claims

1. Payment device comprising:

a mobile terminal; and

at least one financial data storage element,

wherein said mobile terminal and said at least one financial data storage element are logically associated, and

wherein said at least one financial data storage element is coupled to said mobile terminal.

2. The payment device according to claim 1, wherein said at least one financial data storage element is associated with said mobile terminal, through a look-up table located in a remote authorizing node.

3. The payment device according to claim 1, wherein said at least one financial data storage element is a card and wherein credit card information is stored on a magnetic stripe embedded in said card.

4. The payment device according to claim 1, wherein said at least one financial data storage element is a smart card, said smart card including an integrated circuit chip and wherein credit card information is stored on said integrated circuit chip.

5. The mobile terminal according to claim 3, wherein at least portions of said credit card information are selected from the list consisting of:

credit card number;

credit card type;

user secret code; and

user information.

6. The payment device according to claim 1, wherein said at least one financial data storage element is a card and wherein credit card information is stored in a credit card storage medium coupled to said card.

7. The payment device according to claim 6, wherein said credit card storage medium is selected from the list consisting of:

electrically erasable programmable read only memory;

static random access memory;

dynamic random access memory; and

synchronous dynamic random access memory

8. The payment device according to claim 1, wherein said at least one financial data storage element can be detached from said mobile terminal.

9. The mobile terminal according to claim 1, wherein said mobile terminal is associated with a mobile ID.

10. The mobile terminal according to claim 9, wherein said mobile ID is selected from the list consisting of:

mobile identification number;

universal personal telecommunications number;

terminal identifier; and

personal identification number.

11. The payment device according to claim 1, wherein said mobile terminal further comprises at least one card release button and at least one card slot,

wherein said at least one card release button is coupled to said at least one financial data storage element through at least one release mechanism,

wherein said at least one financial data storage element draws out of said at least one card slot, when said at least one card release button is depressed, and

wherein said at least one financial data storage element remains in a drawn in position within said at least one card slot, when said at least one financial data storage element is depressed.

12. The payment device according to claim 11, wherein said at least one card release button is located on a side of said mobile terminal, wherein said side is selected from the list consisting of:

right;

left;

top;

bottom;

front; and

rear.

13. The payment device according to claim 11, wherein said at least one card slot is located on a side of said mobile terminal, wherein said side is selected from the list consisting of:

right;

left;

top;

bottom;

front; and

rear.

14. The payment device according to claim 11, wherein said at least one financial data storage element is substantially rectangular.

15. The payment device according to claim 11, wherein said at least one financial data storage element is a segment of a circle, said at least one financial data storage element rotates about a hinge.

16. The payment device according to claim 1, wherein said at least one financial data storage element is coupled to said mobile terminal through a hinge and said at least one financial data storage element rotates about said hinge.

17. The payment device according to claim 16, wherein said hinge is located at an intersection of sides of said mobile terminal, selected from the list consisting of:

front and top;

front and bottom;

front and right;

front and left;

rear and top;

rear and bottom;

rear and right;

rear and left;

right and top;

right and bottom;

left and top; and

left and bottom.

18. The payment device according to claim 16, wherein said mobile terminal further comprises a stop located in the vicinity of said hinge, and a spring element is coupled between said at least one financial data storage element and said mobile terminal,

wherein said at least one financial data storage element toggles to an extended position by a spring force of said spring element, and said at least one financial data storage element remains in said extended position against said stop, and

wherein said at least one financial data storage element toggles to a retracted position by another spring force of said spring element and said at least one financial data storage element remains in said retracted position against a side of said mobile terminal.

19. The payment device according to claim 16, wherein said at least one financial data storage element is coupled to said hinge by a credit card holder, said credit card holder comprises a card holder slot, each of said at least one financial data storage element and said card holder slot includes a stop,

wherein said credit card holder rotates about said hinge and said at least one financial data storage element partially slides out of said card holder slot and remains in an extended position against said stop, and

wherein said at least one financial data storage element slides into said card holder slot and said credit card holder rotates about said hinge to a retracted position.

20. The payment device according to claim 16, wherein said at least one financial data storage element is coupled to said hinge by a right arm and a left arm.

21. The payment device according to claim 16, wherein the shape of said at least one financial data storage element is substantially a parallelogram.

22. The payment device according to claim 16, wherein said at least one financial data storage element further comprises a right protrusion and a left protrusion, and said mobile terminal further comprises a right latch and a left latch,

wherein said at least one financial data storage element is in a retracted position when said left protrusion is in a recess of said left latch, and said at least one financial data storage element is in an extended position when said right protrusion is in another recess of said right latch.

23. The payment device according to claim 16, wherein said mobile terminal is a flip-phone, said at least one financial data storage element is located between a flipping cover and a headset of said mobile terminal, and said flipping cover rotates about said hinge.

24. The payment device according to claim 1, wherein said at least one financial data storage element is coupled to said mobile terminal through a telescopic rod, said telescopic rod comprising an outer telescopic rod coupled to said mobile terminal, and a plurality of inner telescopic rods rotating inside said outer telescopic rod and axially moving relative to said outer telescopic rod, said at least one financial data storage element is coupled to an outer one of said inner telescopic rods.

25. The payment device according to claim 1, wherein an inner edge of said at least one financial data storage element is coupled to said mobile terminal through a plurality of telescopic rods, the longitudinal axis of said telescopic rods is substantially perpendicular to the longitudinal axis of said mobile terminal.

26. The payment device according to claim 1, wherein said mobile terminal further comprises at least one card slot, said at least one card slot further comprises a right recess and a left recess, said at least one financial data storage element further comprises a credit card protrusion,

wherein said at least one financial data storage element is in an extended position when said credit card protrusion is inside said right recess, and said at least one financial data storage element is in a retracted position when said credit card protrusion is inside said left recess.

27. The payment device according to claim 1, wherein said at least one financial data storage element is coupled to said mobile terminal by a four-bar linkage.

28. The payment device according to claim 1, wherein said at least one financial data storage element is coupled to said mobile terminal by at least one mobile terminal magnet and at least one credit card magnet, and

wherein said at least one mobile terminal magnet is coupled to said mobile terminal and said at least one credit card magnet is coupled to said at least one financial data storage element.

29. The payment device according to claim 1, wherein said at least one financial data storage element is stored in at least one pocket coupled to said mobile terminal.

30. The payment device according to claim 29, wherein said at least one pocket is made of a material selected from the list consisting of:

flexible plastic;

rigid plastic; and

textile.

31. The payment device according to claim 1, wherein said at least one financial data storage element is coupled to said mobile terminal, by a credit card hinge assembly, said credit card hinge assembly coupled to said mobile terminal by a primary hinge, said credit card hinge assembly further comprising a credit card holder, said credit card holder further comprising a secondary hinge,

wherein said at least one financial data storage element is in a first extended position, when said credit card hinge assembly is rotated about said primary hinge, and

wherein said at least one financial data storage element is in a second extended position, when said credit card hinge assembly is rotated about said primary hinge, said credit card holder is rotated about said secondary hinge, whereby said at least one financial data storage element is detached from said credit card hinge assembly.

32. Card holder for coupling at least one financial data storage element to a mobile terminal,

wherein said card holder is coupled to said mobile terminal;

and

wherein said at least one financial data storage element is logically associated with said mobile terminal.

33. The card holder according to claim 32, wherein said card holder comprises at least one mobile terminal magnet coupled to said mobile terminal, and at least one credit card magnet coupled to said at least one financial data storage element.

34. The card holder according to claim 32, wherein said card holder comprises at least one pocket coupled to said mobile terminal.

35. The card holder according to claim 34, wherein said at least one pocket is made of a material selected from the list consisting of:

flexible plastic;

rigid plastic; and

textile.

36. The card holder according to claim 32, wherein said card holder is a credit card hinge assembly, said credit card hinge assembly coupled to said mobile terminal by a primary hinge, said credit card hinge assembly further comprising a credit card holder.

38. The flipping cover according to claim 37, wherein said credit card information is stored on a magnetic stripe embedded in said flipping cover.

39. The flipping cover according to claim 37, wherein said credit card information is selected from the list consisting of:

credit card number;

user secret code; and

user information.

40. The flipping cover according to claim 37, wherein said credit card information is stored in a credit card storage medium coupled to said flipping cover.

41. The flipping cover according to claim 40, wherein said credit card storage medium is selected from the list consisting of:

electrically erasable programmable read only memory;

static random access memory;

dynamic random access memory; and

synchronous dynamic random access memory

37. Flipping cover detachably attached to a flip-phone type mobile terminal, said flipping cover comprising credit card information,

wherein said credit card information is logically associated with said flip-phone type mobile terminal.

42. Method for authenticating a user who performs a transaction, by employing a financial data storage element coupled to a mobile terminal, the method comprising the steps of:

initiating communication with said mobile terminal, according to a mobile ID of said mobile terminal;

requesting a user secret code;

receiving said user secret code from said mobile terminal at a remote authorizing node; and

determining the authenticity of said user.

43. The method according to claim 42, further comprising a preliminary step of determining said mobile ID.

44. The method according to claim 43, wherein said mobile ID is determined by referring to a look-up table located in said remote authorizing node.

45. The method according to claim 43, wherein said mobile ID is determined according to user information embedded in transaction data.

46. The method according to claim 44, wherein said look-up table includes a list of unauthorized credit card numbers, and a plurality of fields in a record associated with each of a plurality of credit card numbers.

47. The method according to claim 46, wherein the type of said fields is selected from the list consisting of:

said user secret code;

said mobile ID;

unique audio data;

unique alphanumeric data;

unique visual data; and

account status.

48. The method according to claim 47, wherein said account status field comprises information selected from the list consisting of:

non-authenticated-limit-value;

authenticated-limit-value; and

transaction code.

49. The method according to claim 43, further comprising a preliminary step of transmitting credit card information to said remote authorizing node.

50. The method according to claim 49, wherein said step of transmitting is performed via a network.

51. The method according to claim 49, further comprising a preliminary step of retrieving credit card information which is stored in a credit card storage medium.

52. The method according to claim 51, wherein said step of retrieving is performed by passing said credit card storage medium through a card reader slot of a card reader.

53. The method according to claim 51, wherein said step of retrieving is performed by interfacing said credit card storage medium with a data transfer interface.

54. The method according to claim 42, further comprising a step of authorizing said transaction by generating a transaction authorization code for said transaction, when said user is authentic, and denying said transaction when said user is not authentic.

55. The method according to claim 54, further comprising a step of transmitting said transaction authorization code to said mobile terminal, for further reporting to a service unit.

56. The method according to claim 54, further comprising a step of transmitting said transaction authorization code to a service unit.

57. The method according to claim 55, wherein said step of transmitting is performed via a network.

58. The method according to claim 57, wherein said step of transmitting is performed via a network.

59. The method according to claim 42, further comprising a step of comparing a received credit card number with a list of unauthorized credit card numbers, before said step of determining.

60. The method according to claim 59, wherein said remote authorizing node authorizes said transaction when said received credit card number does not match a number in said list of unauthorized credit card numbers, and

wherein said remote authorizing node denies said transaction when said received credit card number matches said number in said list of unauthorized credit card numbers.

61. The method according to claim 59, further comprising a step of comparing a transaction value with a non-authenticated-limit-value, wherein said non-authenticated-limit-value is stored in a look-up table.

62. The method according to claim 61, wherein said remote authorizing node authorizes said transaction when said transaction value is less than said non-authenticated-limit-value, and

wherein said remote authorizing node denies said transaction when said transaction value is greater than said non-authenticated-limit-value.

63. The method according to claim 59, further comprising a step of comparing a transaction value with a non-authenticated-limit-value and an authenticated-limit-value, wherein said non-authenticated-limit-value and said authenticated-limit-value are stored in a look-up table.

64. The method according to claim 63, wherein said remote authorizing node performs said step of determining when said transaction value is between said non-authenticated-limit-value and said authenticated-limit-value, and denies said transaction when said transaction value is greater than said authenticated-limit-value.

65. The method according to claim 42, wherein said step of determining further comprises a step of comparing a received secret code with a retrieved secret code.

66. The method according to claim 65, wherein said remote authorizing node authenticates said user when said received secret code matches said retrieved secret code, and

wherein said remote authorizing node does not authenticate said user when said received secret code does not match said retrieved secret code.

67. The method according to claim 42, wherein said remote authorizing node determines whether said user responds to said communication initiation.

68. The method according to claim 67, wherein said remote authorizing node authorizes said transaction when said user responds to said communication initiation, and

wherein said remote authorizing node denies said transaction when said user does not respond to said communication initiation.

69. The method according to claim 42, wherein said step of determining further comprises a step of comparing received voice characteristics with retrieved voice characteristics.

70. The method according to claim 69, wherein said remote authorizing node authorizes said transaction when said received voice characteristics match said retrieved voice characteristics, and

wherein said remote authorizing node denies said transaction when said received voice characteristics do not match said retrieved voice characteristics.

71. The method according to claim 42, wherein said step of determining further comprises a step of comparing at least one received alphanumeric character with at least one retrieved alphanumeric character.

72. The method according to claim 71, wherein said remote authorizing node authorizes said transaction when said at least one received alphanumeric character matches said at least one retrieved alphanumeric character, and

wherein said remote authorizing node denies said transaction when said at least one received alphanumeric character does not match said at least one retrieved alphanumeric character.

73. The method according to claim 42, wherein said step of determining further comprises a step of comparing a processed image with a retrieved image.

74. The method according to claim 73, wherein said remote authorizing node authorizes said transaction when said processed image matches said retrieved image, and

wherein said remote authorizing node denies said transaction when said processed image does not match said retrieved image.

75. The method according to claim 42, further comprising a step of determining a transaction code for said transaction, after said step of retrieving.

76. The method according to claim 75, further comprising a step of receiving said transaction code from a service unit, by said remote authorizing node.

77. The method according to claim 76, further comprising a step of comparing said received transaction code with a stored transaction code.

78. The method according to claim 77, wherein said remote authorizing node authorizes said transaction when said received transaction code matches said stored transaction code, and

wherein said remote authorizing node denies said transaction when said received transaction code does not match said stored transaction code.

79. The method according to claim 42, further comprising a step of producing a retrieved authentication secret code, by applying an authorizing time function to a retrieved user secret code, before said step of requesting.

80. The method according to claim 79, further comprising a step of producing an authentication secret code, by applying a mobile terminal time function to an entered user secret code, after said step of requesting.

81. The method according to claim 80, further comprising a step of receiving said authentication secret code from said mobile terminal, by said remote authorizing node.

82. The method according to claim 81, further comprising a step of comparing said retrieved authentication secret code with said received authentication secret code.

83. The method according to claim 82, wherein said remote authorizing node authorizes said transaction when said received authentication secret code matches said retrieved authentication secret code, and

wherein said remote authorizing node denies said transaction when said received authentication secret code does not match said retrieved authentication secret code.

84. The method according to claim 80, wherein said authorizing time function is substantially identical with said mobile terminal time function.

85. Method for authenticating a user who performs a transaction, by employing a financial data storage element coupled to a mobile terminal, the method comprising the steps of:

determining a first authentication code according to credit card information stored in a credit card storage medium;

receiving a user secret code by said mobile terminal, from said user;

determining a second authentication code according to said user secret code; and

comparing said first authentication code with said second authentication code.

86. The method according to claim 85, further comprising a preliminary step of retrieving said credit card information.

87. The method according to claim 85, further comprising a step of transmitting said second authentication code to a service unit, before said step of comparing.

88. The method according to claim 85, further comprising a step of reporting said second authentication code to said user, after said step of determining said second authentication code.

89. The method according to claim 88, further comprising a step of receiving said second authentication code by a service unit, from said user, after said step of reporting.

90. The method according to claim 85, further comprising a step of completing said transaction after said step of comparing, when said first authentication code matches said second authentication code.

91. The method according to claim 85, further comprising a step of denying said transaction after said step of comparing, when said first authentication code does not match said second authentication code.

92. The method according to claim 85, wherein said step of receiving said user secret code is performed, when a transaction value is greater than a predetermined value.

93. The method according to claim 85, wherein said first authentication code is determined by applying a service unit time function to a retrieved user secret code.

94. The method according to claim 93, wherein said second authentication code is determined by applying a mobile terminal time function to an entered user secret code.

95. The method according to claim 94, wherein said service unit time function is substantially identical with said mobile terminal time function.

96. The method according to claim 93, wherein a service unit retrieves said retrieved user secret code from a look-up table.

97. The method according to claim 96, wherein said look-up table includes information selected from the list consisting of:

approved credit card number list; and

local list of unauthorized credit card numbers.

98. The method according to claim 97, wherein each of a plurality of credit card numbers in said approved credit card number list, points to a different user secret code.

99. The method according to claim 85, further comprising a step of transmitting a request to said mobile terminal to enter said user secret code by said user, before said step of receiving said user secret code.

100. The method according to claim 99, wherein said step of transmitting said request is performed wirelessly.

101. The method according to claim 87, wherein said step of transmitting said second authentication code is performed according to a short range radio communication protocol.

102. The method according to claim 85, further comprising a step of requesting said user to enter said user secret code to said mobile terminal, before said step of receiving.

103. The method according to claim 102, wherein said step of requesting is performed via a service unit user interface.

104. The method according to claim 102, wherein said step of requesting is performed via said mobile terminal, according to a short range radio communication protocol.

105. The method according to claim 89, wherein said step of receiving said second authentication code is performed via a service unit user interface of said service unit.

106. The method according to claim 89, wherein said step of receiving said second authentication code is performed according to a short range radio communication protocol.

107. The method according to claim 85, further comprising a step of comparing a received credit card number with a local list of unauthorized credit card numbers when a transaction value is greater than a predetermined value, after said step of retrieving.

108. The method according to claim 107, wherein a service unit authorizes said transaction when said received credit card number does not match a number in said local list of unauthorized credit card numbers, and

wherein said service unit denies said transaction when said received credit card number matches said number in said local list of unauthorized credit card numbers.

109. The method according to claim 86, wherein said step of retrieving is performed by interfacing said credit card storage medium with a data transfer interface.

110. The method according to claim 85, wherein said credit card information is selected from the list consisting of:

credit card number;

user secret code;

user information; and

authorized list of transaction codes.

111. The method according to claim 85, further comprising a step of comparing a requested transaction code with an authorized list of transaction codes, after said step of comparing said first authentication code with said second authentication code.

112. The method according to claim 111, wherein a service unit authorizes said transaction when said requested transaction code matches a transaction code in said authorized list of transaction codes, and

wherein said service unit denies said transaction when said requested transaction code does not match said transaction code in said authorized list of transaction codes.