(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2010/0133334 A1
`(43) Pub. Date:
`Jun. 3, 2010
`Vadhri
`
`US 201001.33334A1
`
`(54) SYSTEMAND METHOD TO ALLOW ACCESS
`TO AVALUE HOLDING ACCOUNT
`
`(76) Inventor:
`
`Srinivas Vadhri, Cupertino, CA
`(US)
`
`Correspondence Address:
`SCHWEGMAN, LUNDBERG & WOESSNER/
`EBAY
`P.O. BOX 2938
`MINNEAPOLIS, MN 55402 (US)
`
`(21) Appl. No.:
`
`12/327,665
`
`(22) Filed:
`
`Dec. 3, 2008
`
`Publication Classification
`
`(51) Int. Cl.
`(2006.01)
`G06O 40/00
`(52) U.S. Cl. ........................................................ 235/379
`(57)
`ABSTRACT
`This document discusses, among other things, a system and
`method of allowing access to a value holding account. In
`various example embodiments, the value holding account is
`associated with a first account code that allows access to the
`value holding account. Some example embodiments include
`receiving a request for a second account code that is based on
`the first account code, and providing the second account code
`based on receiving the request for the second account code.
`The first account code may to allow access to the value hold
`ing account for a first determinable period and the second
`account code may allow access to the value holding account
`for a second determinable period that is different from the first
`determinable period.
`
`
`
`ACCOUNT ACCESS OBJECT
`REQUESTER |
`
`106
`
`108
`PROVIDER -
`
`APPL-1006
`APPLE INC. / Page 1 of 18
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 1 of 8
`
`US 2010/01.33334 A1
`
`90].
`
`80||
`
`I "OIH
`
`
`
`
`
`LOETEJO SSE OO\/ LN(\OOOV/
`
`
`
`
`
`APPL-1006
`APPLE INC. / Page 2 of 18
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 2 of 8
`
`US 2010/01.33334 A1
`
`EIN|HOV/W
`
`ENIHOV/W
`
`0 || Z.
`
`Z * OIH
`
`902
`
`ZOZ
`
`
`
`
`
`
`
`APPL-1006
`APPLE INC. / Page 3 of 18
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 3 of 8
`
`US 2010/01.33334 A1
`
`300
`
`Ya
`
`301
`USER -
`
`302
`-
`
`REQUEST A
`TEMPORARY
`ACCOUNT CODE
`
`
`
`
`
`
`
`
`
`305
`
`303
`ACCOUNT AccEss/
`OBJECT
`
`VALUE HOLDING
`ACCOUNT OR
`ASSOCIATE
`THEREOF
`
`RECEIVE THE
`REQUEST FOR
`THE TEMPORARY
`ACCOUNT CODE
`
`
`
`
`
`FURTHER
`REQUEST THE
`TEMPORARY
`ACCOUNT
`CODE
`
`310
`
`308
`
`
`
`
`
`GENERATE THE
`TEMPORARY
`ACCOUNT CODE
`
`PROVIDE THE THE
`TEMPORARY
`ACCOUNT CODE
`BASED ON
`RECEIVING THE
`REQUEST
`
`
`
`
`
`312
`
`
`
`
`
`RECEIVE THE
`TEMPORARY
`ACCOUNT CODE
`
`FIG. 3
`
`APPL-1006
`APPLE INC. / Page 4 of 18
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 4 of 8
`
`US 2010/01.33334 A1
`
`400 N.
`
`401
`USER -
`
`REQUEST ACCESS TO
`THE WALUE HOLDING
`ACCOUNT USING THE
`TEMPORARY
`ACCOUNT CODE
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`RECEIVE
`NOTIFICATION OF
`WHETHER THE
`TEMPORARY
`ACCOUNT CODE IS
`VALID
`
`
`
`
`
`
`
`y
`Acco-NACCESS
`
`405
`VALUE HOLDING )
`ACCOUNT OR
`ASSOCATE THEREOF
`
`ASSOCIATE THE
`TEMPORARY
`ACCOUNT CODE
`WITH THE FIRST
`ACCOUNT CODE
`
`404
`
`406
`
`
`
`IS THE TEMPORARY
`ACCOUNT CODE
`VALID, BASED ON
`THE FIRST ACCOUNT
`CODE'?
`
`
`
`FIG. 4
`
`APPL-1006
`APPLE INC. / Page 5 of 18
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 5 of 8
`
`US 2010/01.33334 A1
`
`500
`N
`530
`3RD PARTY SERVER
`
`510
`
`512
`N
`CLIENT MACHINE
`PROGRAMMATIC
`CLIENT
`
`508
`
`3RD PARTY
`APPLICATION
`
`WEB
`CLIENT
`
`528
`
`
`
`
`
`506
`
`504
`
`NETWORK
`(E.G.,
`INTERNET)
`
`ACCOUNT
`ACCESS
`CARD
`
`- - - - - - - - - - - - - - -m a
`
`-
`
`- - - - - -
`
`-
`
`ma as
`
`- - - - - - - m
`
`502
`
`AP SERVERS
`(PROGRAMMATIC
`INTERFACE)
`
`516
`
`WEB SERVERS
`(WEB
`INTERFACE)
`
`
`
`
`
`
`
`APPLICATION SERVER(S)
`
`MARKETPLACE
`APPLICATION(S)
`
`PAYMENT
`APPLICATION(S)
`
`
`
`DATABASE
`SERVER(S)
`
`DATABASE(S)
`
`APPL-1006
`APPLE INC. / Page 6 of 18
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 6 of 8
`
`US 2010/01.33334 A1
`
`EE20 & EE22
`
`APPLICATIONS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`PUBLICATION
`APPLICATION(S)
`
`AUCTION
`APPLICATION(S)
`
`FIXED-PRICE
`APPLICATION(S)
`
`STORE
`APPLICATION(S)
`
`REPUTATION
`APPLICATION(S)
`
`PERSONALIZATION
`APPLICATION(S)
`
`INTERNATIONALATION
`APPLICATION(S)
`
`NAVIGATION
`APPLICATION(S)
`
`MAGING
`APPLICATION(S)
`
`618
`
`620
`
`LISTING
`CREATION
`(SELLER)
`APPLICATION(S)
`
`LISTING
`MANAGEMENT
`(SELLER)
`APPLICATION(S)
`
`POST-LISTING
`MANAGEMENT
`APPLICATION(S)
`
`DISPUTE
`
`
`
`
`
`FRAUD
`
`APPLICATION(S)
`
`APPLICATION(S)
`
`MERCHANDZING
`APPLICATION(S)
`
`LOYALTY
`PROMOTION
`APPLICATION(S)
`
`
`
`
`
`
`
`
`
`
`
`
`
`ACCOUNT
`NUMBER
`APPLICATIONS
`
`FIG. 6
`
`APPL-1006
`APPLE INC. / Page 7 of 18
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 7 of 8
`
`US 2010/01.33334 A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`-712
`
`FEEDBACK
`TABLE
`
`CARD NUMBER
`TABLE
`
`USER TABLE
`
`
`
`
`
`HISTORY
`TABLE
`
`BIDS TABLE
`
`ITEMS TABLE
`
`ATTRIBUTES
`TABLE(S)
`
`714.
`
`716
`
`(1 708
`
`TRANSACTION
`TABLE
`
`ORDER TABLE
`
`
`
`FIG. 7
`
`802Y
`
`804N
`
`806 Y
`
`807 Y
`
`TEMPORARY CARD
`USER ID PERSISTENT CARD TEMPORARY CARD
`NUMBER/EXP. TIME NUMBERVEXP. TIME NUMBER/EXP. TIME HISTORY
`123456789101112113- T444455556666777102 T231517 192325272/O2-08-08,
`O8-08, 1130
`O722; T11232527293135/01-04
`08
`08
`
`1
`
`2
`
`3
`
`3.1415 16171819202 12-T/88889999.101011110
`11
`11-08, 1330
`
`12223242526272829/9T4555657585951OOI 10-TO31517192325272/O2-13-07,
`1O
`10-08,2045
`O722
`
`
`
`808
`
`FIG. 8
`
`APPL-1006
`APPLE INC. / Page 8 of 18
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 8 of 8
`
`US 2010/01.33334 A1
`
`/ 900
`
`VIDEO
`DISPLAY
`
`910
`
`
`
`
`
`APHA-NUMERC
`INPUT DEVICE
`
`912
`
`CURSOR
`CONTROL
`DEVICE
`
`914
`
`DSK DRIVE UNIT
`916
`E. t
`922
`MEDIUM
`INSTRUCTIONSH-924
`
`
`
`SIGNAL
`GENERATION
`DEVICE
`
`918
`
`PROCESSOR
`
`NSTRUCTIONS
`
`902
`924
`
`
`
`904
`924 - INSTRUCTIONS
`
`
`
`908
`
`906
`924 - NSTRUCTIONS
`
`920
`
`NETWORK
`INTERFACE
`DEVICE
`
`926
`
`FIG. 9
`
`APPL-1006
`APPLE INC. / Page 9 of 18
`
`

`

`US 2010/01.33334 A1
`
`Jun. 3, 2010
`
`SYSTEMAND METHOD TO ALLOW ACCESS
`TO AVALUE HOLDING ACCOUNT
`
`TECHNICAL FIELD
`0001. This patent document pertains generally to value
`holding accounts and more particularly, but not by way of
`limitation, to systems and methods for accessing a value
`holding account.
`
`BACKGROUND
`0002. A value holding account may hold anything consid
`ered valuable. An account holder may access his or her value
`holding account using an account code such as an account
`number including a sequence of numbers.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0003. In the drawings, which are not necessarily drawn to
`scale, like numerals describe substantially similar compo
`nents throughout the several views. Like numerals having
`different letter suffixes represent different instances of sub
`stantially similar components. The drawings illustrate gener
`ally, by way of example, but not by way of limitation, various
`embodiments discussed in the present document.
`0004 FIG. 1 is a block diagram showing an account access
`object, in accordance with an example embodiment;
`0005 FIG. 2 is a block diagram showing an account access
`card communicatively coupled to a machine, in accordance
`with an example embodiment;
`0006 FIG. 3 is a flow diagram illustrating a flow for pro
`viding a temporary account code, in accordance with an
`example embodiment;
`0007 FIG. 4 is a flow diagram illustrating a flow for
`accessing a value holding account, in accordance with an
`example embodiment;
`0008 FIG. 5 is a network diagram depicting a client
`server system, within which example embodiments may be
`deployed;
`0009 FIG. 6 is a block diagram illustrating multiple appli
`cations that, in an example embodiment, are provided as part
`of a networked system;
`0010 FIG. 7 is a high-level entity-relationship diagram,
`illustrating various tables that may be maintained within data
`bases, and that are utilized by and Support applications;
`0011
`FIG. 8 is an example card number table, in accor
`dance with an example embodiment; and
`0012 FIG. 9 shows a diagrammatic representation of a
`machine in the example form of a computer system within
`which a set of instructions, for causing the machine to per
`formany one or more of the methodologies discussed herein,
`may be executed.
`
`DETAILED DESCRIPTION
`
`Overview
`0013 Various example embodiments include a credit card
`from which a temporary card number may be requested and
`displayed so that the temporary card number can be used to
`purchase goods and/or services. The credit card may include
`a traditional 16-digit credit card number and associated expi
`ration date that can be used for account identification and/or
`account Verification. As used herein, a credit card is an
`example of an account access object. It may be noted that the
`present Subject matter is not limited to a credit cards and
`
`credit card accounts, any type of value holding account may
`be associated with an account access object. Example account
`access objects may include financial instruments such as
`check cards, gift cards, credit cards, charge cards, debit cards
`or any other physical object.
`0014 For some example embodiments, a user may make a
`request for the example temporary card number by selecting
`a selectable switch or button on the credit card. The selector
`may be implemented in Software and may be activated, for
`example, via a touch sensitive Screen. The example credit
`card may receive the request and wirelessly transmit the
`request for the temporary card number to a generator of the
`example temporary card number (e.g., a remote server). For
`Some example embodiments, the temporary card number is
`received wirelessly from the source and displayed by a liquid
`crystal display (LCD) on the credit card. The temporary card
`number may be made available using alternative or additional
`technologies (e.g., bar codes, magnetic encoding, etc.) with
`out departing from the claimed Subject matter.
`0015. In various example embodiments, both the credit
`card number and the temporary card number can be used up to
`an expiration date and/or time. The expiration date of the
`temporary card number may include a number of hours from
`the time of issue (e.g., 0.25-hours or 24-hours), while the
`expiration date of the traditional credit card number may
`include a number of years from the date of issue. By using the
`example temporary card number, a user may control the
`amount of time an account number is at risk of fraud due to
`being exposed on the internet and/or to merchants or any
`other person or machine. For example, a user's credit card
`number may be at risk for a number of years when it is used
`to make a purchase via the internet, while for the same pur
`chase, a user's temporary card number would be at risk for a
`number of hours.
`0016. The example embodiments include references to the
`accompanying drawings, which form a part of the detailed
`description. The drawings show illustrations in accordance
`with example embodiments. These example embodiments,
`which may also referred to herein as “examples.” are
`described in enough detail to enable those skilled in the art to
`practice the claimed subject matter. The example embodi
`ments may be combined, other embodiments may be utilized,
`or structural, logical and electrical changes may be made
`without departing from the scope what is claimed. The
`detailed description is, therefore, not to be taken in a limiting
`sense, and the scope is defined by the appended claims and
`their equivalents.
`
`Example Embodiments
`0017 FIG. 1 is a block diagram showing an account access
`object 104 associated with a persistent account code 102 and
`temporary account code 103, in accordance with an example
`embodiment. The double arrows 105 represent an association
`between the account access object 104 and the persistent and
`temporary account codes 102 and 103.
`0018. The account access object 104 is a physical object
`(e.g., a plastic card, a cell phone, a key chain or any other
`object) that may be presented or otherwise used to access a
`value holding account, via the persistent and temporary
`account codes 102 and 103. The account access object 104
`may include a physical financial instrument. For example, the
`account access object 104 may function as a credit card, debit
`card, gift card or the like. Using the account access object 104.
`a user may present an account code (e.g., the persistent
`
`APPL-1006
`APPLE INC. / Page 10 of 18
`
`

`

`US 2010/01.33334 A1
`
`Jun. 3, 2010
`
`account code 102) in order to charge, debit or credit the value
`holding account to which the account access object 104 cor
`responds.
`0019. The account access object 104 is to allow for the
`generation of the temporary account code 103, while the
`persistent account code 102 is to be persistent relative to the
`temporary account code 103. The persistent account codes
`102 and the temporary account code 103 are separate codes
`that may be presented to a proprietor of a value holding
`account, to access the value holding account. In some
`example embodiments, the persistent account code 102 and
`the temporary account code 103 may each include a sequence
`of alphanumeric characters.
`0020. In some example embodiments, the persistent
`account code 102 is imprinted on the account access object
`104 and encoded within a magnetic strip (not shown) or a
`barcode (not shown). Alternatively or additionally, the per
`sistent account code 102 may be made available by radio
`frequency identification (RFID) or other medium. The per
`sistent account code 102 may be associated with the account
`access object 104 in various alternative or additional fashions
`without departing from the claimed Subject matter.
`0021. The account access object 104 is shown to include a
`requester 106 and a provider 108. The requester 106 may
`allow for the request of the temporary account code 103. In
`some example embodiments, the requester 106 is selectable
`by a user to request the temporary account code 103. A
`selectable requester 106 may include a button or touchscreen
`that may be depressed to indicate a request to hardware and/or
`Software implemented logic included within the requester
`106.
`0022. Alternatively or additionally, the requester 106 may
`be communicatively coupled to a radio receiver to receive
`from a remote machine or device, a wireless request for the
`temporary account code 103. In various example embodi
`ments, the requester 106 is to forward requests for the tem
`porary account code 103 to a generator of the temporary
`account code 103. For some example embodiments the gen
`erator of the temporary account code 103 includes a machine
`(not shown) communicatively coupled to the account access
`object via a network. Without departing from the claimed
`subject matter, the provider 108 located on the account access
`object 104 may alternatively or additionally generate and
`provide the temporary account code 103.
`0023 The provider 108 is to make the temporary account
`code 103 available for use to access a value holding account.
`As stated above, the provider 108 may generate the temporary
`account code 103. The provider 108 may include hardware
`and/or Software logic configured to securely generate and
`store random numbers (e.g., and/or characters) randomly
`sequenced to form the temporary account code 103.
`0024 For some example embodiments, the provider 108 is
`to receive the temporary account code 103 after it has been
`generated externally (e.g., on a machine connected to a wire
`less network) from the account access object 104. The exter
`nally generated temporary account code 103 may be received
`wirelessly (e.g., Bluetooth, Wi-Fi, etc.), via a wireless radio
`implemented on the provider 108. Alternatively or addition
`ally, the provider 108 may receive the temporary account
`code 103 by magnetization or wired connection.
`0025. Whether the provider 108 generates or receives the
`temporary account code 103, the provider 108 is to allow the
`temporary account code 103 to be ascertained by a human or
`machine user (not shown). For some example embodiments,
`
`the temporary account code 103 to be read via liquid crystal
`diode (LCD) screen or other display technology of the pro
`vider 108. Various example embodiments may include the
`temporary account code 103 being made available wireless
`(e.g., to a cellphone screen) or physically (e.g., by Swiping a
`magnetic strip to be read by the payment machine).
`0026 FIG. 2 is a block diagram showing an account access
`card 204 that may wirelessly communicate with a machine
`214, in accordance with an example embodiment. The
`account access card 204 and its components represent
`example embodiments of the account access object 104 of
`FIG 1.
`0027 FIG. 2 is shown to include a card number portion
`208 (an example embodiment of the provider 108 of FIG. 1)
`to provide via LCD and/or imprinting, a persistent card num
`ber/expiration date 202 and a temporary card number/expi
`ration date 203 (examples of the account codes 102 and 103
`respectively of FIG. 1). Throughout this document, the word
`“persistent” when used in “persistent card number” means
`persistent relative to the temporary card number/expiration
`date 203. For example the temporary card number will always
`have an expiration date that is earlier than or equal to the
`persistent card number's expiration date.
`0028. The example card number requester 206 (an
`example embodiment of the requester 106 of FIG. 1) may
`include a physically selectable switch or selector 207 that a
`user may select to request a temporary card number/expira
`tion date 203. Alternatively or additionally, a remote machine
`211 may transmit a wireless signal 213 to the wireless radio
`210 to request the temporary card number/expiration date
`203. In some example embodiments, the remote machine 211
`may include a mobile phone, or other mobile device with
`wireless capabilities.
`0029. Once a request for the temporary card number/ex
`piration number 203 has been received, the wireless radio 210
`may transmit via wireless signal 212, the request for the
`temporary card number/expiration date 203 to the machine
`214 and receive the generated temporary card number/expi
`ration date 203 via the wireless signal 212 from the machine
`214. The wireless radio 210 may include any radio that is
`appropriate to transmit and receive the wireless signal 212,
`which may include Bluetooth, WiMax, WI-Fi or any other
`types of radio frequency signals.
`0030 The machine 214 is to receive a request for the
`temporary card number/expiration date 203 and to generate
`the temporary card number/expiration date 203 before trans
`mitting it to the account access card 204 to be presented by the
`card number portion 208 of the account access card 204. The
`machine 214 may be communicatively coupled to a wireless
`radio (not shown) that transmits and receives wireless signals
`212 on behalf of the machine 214. The machine 214 may
`include a generator 216 to receive requests and generate tem
`porary card numbers.
`0031 FIG. 3 is a flow diagram, showing a flow 300 of
`operations performed by entities for providing a temporary
`account code, in accordance with an example embodiment.
`FIG. 3 is shown to include a user 301 lane, an account access
`object 303 lane and a value holding account 305 lane.
`0032 Blocks shown in the user lane 301 represent user
`actions performed by a user of the account access card 202 of
`FIG. 2. The user may include an owner of a value holding
`account, a party authorized by an owner of the value holding
`account or a party not authorized by the owner of the value
`holding account. Further, the user may be a human user, a
`
`APPL-1006
`APPLE INC. / Page 11 of 18
`
`

`

`US 2010/01.33334 A1
`
`Jun. 3, 2010
`
`machine user or a combination of the two (e.g., a human user
`operating an access machine that interacts with the account
`access card 204).
`0033 Blocks shown in the account access object lane 303
`represent account access object actions performed by the
`account access card 204 of FIG.2. Blocks in the value holding
`account lane 305 representactions taken by a proprietor of the
`valueholding account Such as a proprietor of the machine 214
`of FIG. 2 (e.g., an account server).
`0034. It may be noted that the account access object 204 of
`FIG. 2 is a physical object, which may include circuitry (e.g.,
`a processor, memory, logic circuitry, etc.). Operations per
`formed by the various components of the account access
`object 204 and card 204 of FIG. 2 may be implemented via
`hardware, Software (e.g., stored in memory) or a combination
`of hardware and software.
`0035. The flow 300 relates to accessing a value holding
`account. Examples of value holding accounts include credit
`card accounts, charge card accounts, debit card accounts, gift
`card accounts or any other value holding account that may be
`accessed.
`0036. At block 302, the flow 300 includes the user action
`of requesting an account code. For various example embodi
`ments, the user is to request a temporary card number/expi
`ration date 203 from the account access card 204 by interact
`ing (e.g., selecting a selectable button or Switch) with the card
`number requester 206 of FIG. 2. In some example embodi
`ments, the account access card 204 is a physical financial
`instrument such as a credit card associated with a persistent
`account code Such as credit card number.
`0037. The account access card 204 may display the per
`sistent card number/expiration date 202, via a card number
`portion 208 (e.g., a provider). The persistent card number/
`expiration date 202 may be configured to allow access to a
`value holding account for a determinable period (e.g., an
`expiration time allowing several years of service) while the
`temporary card number/expiration date 203 may be config
`ured to allow access to the value holding account for a differ
`ent determinable period (e.g., an expiration time allowing 24
`hours of service). In example embodiments, the determinable
`period associated with the temporary card number is to expire
`before at or before the expiration time of the determinable
`period associated with the persistent card number.
`0038. In different example embodiments, the persistent
`card number/expiration date 202 of FIG. 2 may include a
`credit card number, a charge card number, a debit card num
`ber, a gift card number, Some combination of the above
`accounts or any other account code that may be used to access
`a value holding account.
`0039. At block 304 the flow 300 includes the account
`access object action of receiving the request for an account
`code (e.g., the temporary card number/expiration date 203).
`In an example embodiment, the requester 206 receives a
`physical selection indicating a request for the temporary card
`number/expiration date 203. The request may be generated
`via user activation of a selector 207 on the account access
`object. Alternatively or additionally, the requester 206 may
`include a wireless receiver to receive the request via a wire
`less connection.
`0040. At block 306, the flow 300 is shown to include the
`account access object action of further requesting the tempo
`rary account number from the value holding account, respon
`sive to receiving the request for the temporary account code.
`For some example embodiments, the card number requester
`
`206 is to transmit a further request for the temporary card
`number/expiration date 203 of FIG. 2 from a network
`machine (e.g., the account server 214), which is associated
`with the value holding account. The request may be wire
`lessly transmitted via wireless signal 212, based on the
`account access card 204 receiving the request for the tempo
`rary card number/expiration date 203. The account server
`214, in response to receiving the request, may cause the
`generator 216 to generate the temporary card number/expi
`ration date 203 and deliver it via wireless signal 212 to the
`account access card 204 (e.g., the provider). Such a response
`is indicated by the block 308 of FIG. 3.
`0041. At block 310, the flow 300 may include the account
`access object action of providing a user with the account
`access code (e.g., the temporary card number/expiration date
`203 of FIG. 2). The card number portion 208 may receive the
`temporary card number/expiration date 203 wirelessly from
`the machine 214 (e.g., the account server), and provide the
`received temporary card number/expiration date 203. In vari
`ous example embodiments, the card number portion 208 is to
`make the temporary card number/expiration date 203 acces
`sible via display on an LCD Screen, a barcode display, a
`magnetic encoder or any other appropriate medium. Block
`312 of the flow 300 shows the user action of receiving the
`temporary account number from the account access object.
`0042 FIG. 4 is a flow diagram showing a flow 400 for
`accessing a value holding account, in accordance with an
`example embodiment. The user lane 401, an account access
`object lane 401 and a value holding account lane 401 shown
`in FIG.4 may be substantially similar to the user lane 301, an
`account access object lane 303 and a value holding account
`lane 305 of FIG. 3.
`0043. At block 402, the flow 400 may include the user
`action of requesting access to the value holding account using
`the account code (e.g., the temporary card number/expiration
`date 203 of FIG. 2). In an example embodiment, the user may
`recite the displayed temporary card number/expiration date
`203 to a merchant who may interact with the value holding
`account or an associate thereof to request access to the value
`holding account. Various other techniques used to request
`access to the value holding account may include Swiping a
`magnetic strip (e.g., the card number portion) of the account
`access card 204 through a magnetic reader or scanning a bar
`code (e.g., the card number portion) of the account access
`card 204 with a bar code scanner. For some example embodi
`ments, the wireless radio 210 of the account access card 204
`may communicate the temporary card number/expiration
`date 203 to a remote machine (e.g., the machine 214) to access
`the value holding account.
`0044. At block 404 of the flow 400 includes the value
`holding account or an associate of the value holding account
`action of associating the account code (e.g., the temporary
`account code 203, of FIG. 2) with another account code
`assigned to the account access object (e.g., the persistent card
`number/expiration date 202). This may include a machine
`(e.g., the machine 214) accessing a table that associates per
`sistent card numbers assigned to account access cards with
`temporary card numbers that have most recently been gener
`ated for the account access cards.
`0045. At block 406 of the method 400, the flow may
`include the value holding account or an associate of the value
`holding account action of determining whether or not the
`account code (e.g., the temporary account code 203 of FIG.2)
`is a valid account code, based on another account code (e.g.,
`
`APPL-1006
`APPLE INC. / Page 12 of 18
`
`

`

`US 2010/01.33334 A1
`
`Jun. 3, 2010
`
`the persistent card number) associated with the account
`access object 403. In example embodiments, the temporary
`card number/expiration date 203 is considered valid if it is
`associated with the persistent card number/expiration date
`202 in the table referred to above.
`0046. At block 408 of the flow 400, the method may
`include the useraction of receiving notification of whether the
`account code (e.g., the temporary account code of FIG. 2) is
`considered to be valid or invalid. In some example embodi
`ments, notification may be sent to a card reader and/or to the
`account access card itself via wired and/or wireless signals. In
`an example embodiment, a valid temporary card number or
`the persistent card number may be used to access what is of
`value within the value holding account 405. For some
`example embodiments, this may include receiving authoriza
`tion to purchase goods and/or services using the persistent
`card number/expiration date 202 or the temporary card num
`ber/expiration date 203 of the account access card 204.
`0047 FIG. 5 is a network diagram depicting a client
`server system 500, within which example embodiments may
`be deployed. A networked system 502, in the example forms
`of a network-based marketplace or publication system, pro
`vides server-side functionality, via a network 504 (e.g., the
`Internet or Wide Area Network (WAN)) to one or more cli
`ents. FIG. 5 illustrates, for example, a web client 506 (e.g., a
`browser, such as the Internet Explorer browser developed by
`Microsoft Corporation of Redmond, Wash. State), and a pro
`grammatic client 508 executing on respective client machines
`510 and 512. In various example embodiments, an account
`access card 513 may be communicatively coupled to the
`network 504 via wireless connection. In some example
`embodiments, the account access card 513 is substantially
`similar to the account access card 204 of FIG. 2.
`0048. An Application Program Interface (API) server 514
`and a web server 516 are communicatively coupled to, and
`provide programmatic and web interfaces respectively to, one
`or more application servers 518. The application servers 518
`host one or more marketplace applications 520 and payment
`applications 522. The application servers 518 are, in turn,
`shown to be coupled to one or more databases servers 524 that
`facilitate access to one or more databases 526.
`0049. The marketplace applications 520 and the payment
`applications 522 may exist in a production environment,
`where the applications 520 and 522 provide functions and
`services associated with actual commercial activity relating
`to Subject matter of value and real users or entities. Alterna
`tively or additionally the marketplace applications 520 and
`the payment applications 522 may exist in a testing environ
`ment (e.g., testing of API calls) associated with fictitious
`commercial activity relating to fictitious Subject matter and
`fictitious users or entities.
`0050. The marketplace applications 520 may provide a
`number of marketplace functions and services to users that
`access the networked system 502. The payment applications
`522 may likewise provide a number of payment services and
`functions to users. The payment applications 522 may allow
`users to accumulate value (e.g., in a commercial currency,
`Such as the U.S. dollar, or a proprietary currency, Such as
`"points') in accounts, and then later to redeem the accumu
`lated value for products (e.g., goods or services) that are made
`available via the marketplace applications 520. In some
`example embodiments, the payment applications 522 may
`include one or more applications (e.g., an account number
`application, discussed below) that facilitate a user accessing a
`
`value holding account via the account access card 513 and the
`API servers 514 or the web servers 516. While the market
`place and payment applications 520 and 522 are shown in
`FIG.5 to both form part of the networked system 502, it will
`be appreciated that, in alternative embodiments, the payment
`applications 522 may form part of a payment service that is
`separate and distinct from the networked system 502.
`0051. Further, while the system 500 shown in FIG. 5
`employs client-server architecture, the present Subject matter
`is, of course, not limited to Such an architecture, and could
`equally well find application in a distributed, or peer-to-peer,
`architecture system, for example. The various marketplace
`and payment applications 520 and 522 could also be imple
`mented as standalone software programs, which do not nec
`essarily have networking capabilities.
`0.052 The programmatic client 508 accesses the various
`services and functions provided by the marketplace and pay
`ment applications 520 and 522 via the programmatic inter
`face provided by the API server 514. The programmatic client
`508 may, for example, be a seller application (e.g., the Tur
`boLister application developed by eBay Inc., of San Jose,
`Calif.) to enable sellers to author and manage listings on the
`networked system 502 in an off-line manner, and to perform
`batch-mode communications between the programmatic cli
`ent 508 and the networked system 502.
`0053. The web client 506 may access the various market
`place and payment applications 520 and 522 via the web
`interface supported by the web server 516. As described
`above, the example web client 506 (e.g., a web browser) may
`be used as an interface to submit API calls and related infor
`mation for the purpose of testing an API call.
`0054 As stated above, the account access card 513 may
`access the payment applications via the AP