AU2015204328B2 - Payment card imaging for mobile payment - Google Patents
Payment card imaging for mobile payment Download PDFInfo
- Publication number
- AU2015204328B2 AU2015204328B2 AU2015204328A AU2015204328A AU2015204328B2 AU 2015204328 B2 AU2015204328 B2 AU 2015204328B2 AU 2015204328 A AU2015204328 A AU 2015204328A AU 2015204328 A AU2015204328 A AU 2015204328A AU 2015204328 B2 AU2015204328 B2 AU 2015204328B2
- Authority
- AU
- Australia
- Prior art keywords
- payment
- credit
- image data
- transaction
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
- 238000003384 imaging method Methods 0.000 title description 6
- 238000013461 design Methods 0.000 claims description 21
- 230000006870 function Effects 0.000 claims description 17
- 238000004891 communication Methods 0.000 claims description 6
- 238000009877 rendering Methods 0.000 claims 2
- 238000012545 processing Methods 0.000 description 108
- 238000000034 method Methods 0.000 description 57
- 238000010586 diagram Methods 0.000 description 25
- 238000013475 authorization Methods 0.000 description 13
- 230000008878 coupling Effects 0.000 description 9
- 238000010168 coupling process Methods 0.000 description 9
- 238000005859 coupling reaction Methods 0.000 description 9
- 230000004044 response Effects 0.000 description 7
- 230000001413 cellular effect Effects 0.000 description 3
- 238000012552 review Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 241001522296 Erithacus rubecula Species 0.000 description 1
- VJYFKVYYMZPMAB-UHFFFAOYSA-N ethoprophos Chemical compound CCCSP(=O)(OCC)SCCC VJYFKVYYMZPMAB-UHFFFAOYSA-N 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
Landscapes
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Abstract A contactless payment module (60) comprising a key module (130) that contains a unique subscriber identification code and transactional information, a memory (132) configured to store payment image data, a contactless interface (134) configured to transmit at least one of the unique subscriber identification code and the transactional information during execution of a transaction, and a memory interface (136) configured to output the payment image data during the execution of the transaction. 987767D1/10235458_2
Description
1
PAYMENT CARD IMAGING FOR MOBILE PAYMENT
CROSS-REFERENCE TO RELATED PATENTS
This application is a divisional of Australian Patent No. 2009288405 which was filed on 24 August 2009 entitled “Payment card imaging for mobile payment”, which claims Convention priority from US Provisional Application No. 61/091,343 filed on 23 August 2008 entitled “Credit card imaging for mobile payment and other applications”, and from US Patent Application No. 12/326,873 filed on 2 December 2008, entitled “Credit card imaging for mobile payment and other applications”.
FIELD
This invention relates generally to financial transactions and more particularly to credit card imaging incident to financial transactions.
BACKGROUND
Millions of credit card transactions are accurately processed every day regardless of whether the purchaser is making a purchase using a credit card or mobile payment device in his/her home town, in another part of the world, or via the internet. Each transaction has a two stage process: authorization and clearing & settlement. Authorization is the process of approving or declining the transaction at the commencement of the transaction and clearing & settlement is the process of making the payment and accounting for the payment.
The authorization process begins when a point-of-sale terminal (physical for instore purchases, virtual for internet purchases) obtains a purchaser’s account information from a credit card or mobile payment device and further obtains a transaction amount. The terminal transmits the account information and the transaction amount to an acquirer bank, which combines the account information and the transaction amount into an authorization request. The acquirer bank transmits the authorization request to a proprietary transaction processing network (e.g., VisaNet®), which routes the authorization request to an issuer bank (i.e., the bank that issued the credit card). Alternatively, the proprietary transaction processing network may perform a stand-in review and authorization.
When the authorization request is sent to the issuer bank, the bank, or a designated third party, reviews the request and approves it or denies it. The issuer bank transmits a response to the proprietary transaction processing network indicating its decision. The proprietary transaction processing network forwards the response to the acquirer bank, which in turn, forwards the response to the point-of-sale terminal.
The clearing & settlement process begins with clearing, which, in turn, begins when the point-of-sale terminal, or other merchant processing device, transmits sales draft information (e.g., account numbers and amounts) to the acquirer bank. The acquirer bank formats the sales 987767D1/102353962 2 draft information into a clearing message that it transmits to the proprietary transaction processing network. The network transmits the clearing message to the issuer bank, which calculates settlement obligations of the issuer bank, processing fees, and the amount due the acquirer bank. Settlement begins when the issuer bank transmits funds to a designated bank of the proprietary transaction processing network, which, after processing, transfers the funds to the acquirer bank.
In an alternate credit card transaction processing system, the proprietary transaction network is owned by a single issuer bank. Thus, in contrast with the previously described system, the alternative system includes only one issuer bank, not a large number of issuer banks, and, as such, the issuer bank's functions and the proprietary transaction network functions previously discussed are merged. In this alternate system, the processing of the single issuer is less than the multiple issuer system but creates a processing bottleneck due to the single issuer.
The use of mobile payment devices is gaining momentum in the marketplace and consumers desire more features and ease of use. Therefore, a need exists for additional features in mobile payment devices.
SUMMARY
It is an object of the present invention to substantially overcome, or at least ameliorate, one or more disadvantages of existing arrangements.
According to one aspect of the present disclosure, there is provided a mobile payment device comprising: a contactless payment module configured to execute a payment transaction; a processing module configured to: detect the executing of the payment transaction; and retrieve image data based on the detecting; and a display module configured to process the image data into a displayed image.
According to another aspect of the present disclosure, there is provided a mobile payment device comprising: a contactless payment module configured to execute a payment transaction; a digital image sensor configured to capture a digital image; memory configured to: store a plurality of digital images that include the digital image; and store an image master layer; a processing module configured to: detect the executing of the payment transaction; retrieve the image master layer from memory in accordance with the detecting; retrieve one of the plurality of digital images from memory in accordance with the detecting; and generate image data based on the image master layer and the one of the plurality of digital images; and a display module configured to process the image data into a displayed image.
According to another aspect of the present disclosure, there is provided a contactless payment module comprising: a key module that contains a unique subscriber identification code and transactional information; a memory configured to store payment image data; a contactless interface configured to transmit at least one of the unique subscriber identification code and the transactional 987767D1/10235396_2 2a information during execution of a transaction; and a memory interface configured to output the payment image data during the execution of the transaction.
According to another aspect of the present disclosure, there is provided an apparatus comprising: an interface; a processing module; and memory, wherein the processing module functions to: receive, via the interface, a digital image; determine content of the digital image to produce determined content; analyze the determined content to determine whether the determined content contains inappropriate content; when the determined content does not include inappropriate content, generate a design image layer based on the digital image; retrieve from memory a master image layer; process the design image layer and the master image layer to produce credit image data; and transmit, via the interface, the payment image data.
According to another aspect of the present disclosure, there is provided an apparatus comprising: an interface; a processing module; and memory, wherein the processing module functions to: receive, via the interface, a request for payment image data from a mobile payment device; retrieve the payment image data based on an identity of the mobile payment device; and provide, via the interface, the payment image data to the mobile payment device.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is a schematic block diagram of an embodiment of a financial transaction network in accordance with the present invention;
Figure 2 is a schematic block diagram of an embodiment of a mobile payment device in accordance with the present invention;
Figure 3 is a diagram of an example of a credit image displayed on a mobile payment device in accordance with the present invention;
Figure 4 is a logic diagram of an embodiment of a method for credit image data processing in accordance with the present invention;
Figure 5 is a diagram of another example of a credit image in accordance with the present invention;
Figure 6 is a logic diagram of another embodiment of a method for credit image data processing in accordance with the present invention;
Figure 7 is a schematic block diagram of an embodiment of a contactless payment module in accordance with the present invention;
Figure 8 is a schematic block diagram of an embodiment of a financial transaction apparatus in accordance with the present invention;
Figure 9 is a logic diagram of another embodiment of a method for credit image data processing in accordance with the present invention; 987767D1/10235396_2
Figure 10 is a logic diagram of another embodiment of a method for credit image data processing in accordance with the present invention; and 2015204328 15 Jul 2015
Figure 11 is a logic diagram of another embodiment of a method for credit image data processing in accordance with the present invention.
5 DETAILED DESCRIPTION
Figure 1 is a schematic block diagram of an embodiment of a financial transaction system 10 that includes a payment entity device 12, a database 14, a proprietary network 16, a plurality of proprietary interfaces 18-25, a proprietary gateway 26, a plurality of acquirer devices 28-30, a plurality of issuer devices 32-34, a public network 36 (e.g., the internet), a plurality of 10 user devices 38-42, an plurality of merchant devices 44-52, and a plurality of mobile payment devices 54-56. The system 10 supports point of sale financial transactions, automatic payment financial transactions, mobile payment device financial transactions, user device public network based financial transactions, and/or any other type of credit account (e.g., credit card, pre-paid card, corporate card, debit card, purchasing card, mobile payment account, etc.) based financial 15 transactions. The system 10 may also support credit account communications (e.g., account balance inquires, usage offers, bonus programs, general credit account information, etc.) via the public network 36. The system 10 may further support proprietary client services (e.g., commercial accounts payable and/or accounts receivable processing, financial reporting, etc.) for a client via its associated user device 38 and the proprietary gateway 26. Note that each of 20 connection lines ni-ri6 includes a plurality of individual connection lines for each device connected thereto, but arc shown as a bundle for case of illustration.
As shown, each of the issuer devices 32-34 and acquirer devices 28-30 is connected to the public network 36 and to the proprietary network 16 via a proprietary interface 18-25 to support one or more of the various financial transactions and credit account communications. 25 For instance, a financial transaction may begin with a merchant device 44-52 (e.g., a computer, server, point of sale device, web browser application, and/or any device that facilitates a credit account based transaction) obtaining a credit account information for a point of sale transaction, an internet transaction, a mobile payment transaction, etc. In addition, the merchant device 44-52 determines a corresponding transaction amount and transmits, via a connection line, the credit 30 account information and the transaction amount to an affiliated acquirer device 28-30.
The acquirer device 28-30 (e.g., a computer, server, etc. associated with a financial institution supporting credit account transactions of a merchant) generates an authorization request from the credit account information and the transaction amount. The acquirer device 28-30 transmits the authorization request to the payment entity device 12 via the corresponding 3 proprietary interface 18-20 and the proprietary network 16. The payment entity device 12 accesses the associated database 14 to identify the user associated with the credit account information, an issuer, etc. Having identified the issuer, the payment entity device 12 transmits the authorization request to the appropriate issuer device 32-34 via the proprietary network 16 5 and the corresponding proprietary interface 22-24. 2015204328 15 Μ 2015
In an embodiment, the payment entity device 12, the database 14, and the proprietary network 16 may be operated and maintained by a single entity to facilitate seamless authorization and clearing & settlement. For example, Visa, Inc. may provide its VisaNet® as the proprietary network 16 and have one or more computing devices (e.g., computers, servers, 10 super computers, main frames, etc.) coupled to the proprietary network 16 to function as the payment entity device 12, and may have one or more databases 14 coupled thereto. Further, the proprietary interfaces 18-25, which may be proprietary nodes, modems, bridges, etc., serve as secure connection points to the proprietary network 16 to ensure that only authorized devices (e.g., merchant device 44, issuer device 32-34, acquirer device 28-30) have access to the 15 proprietary network 16.
The issuer device 32-34 (e.g., a computer, server, etc. and corresponding financial transaction software associated with a financial institution that issues credit accounts to users) processes the authorization request to determine whether to approve or deny the request. The issuer device 32-34 transmits, via the associated proprietary interface 22-24 and the proprietary 20 network 16, an approval or denial response to the payment entity device 12. The payment entity device 12 forwards the response to the acquirer device 28-30 via the proprietary network 16 and the corresponding proprietary interface 18-20. The acquirer device 28-30 forwards the response to the merchant device 44-52 via the corresponding connection line. Note that the system 10 also supports the clearing & settlement process. 25 The issuer devices 32-34, the acquirer devices 28-30, and/or the payment entity device 12 support credit account communications from users via the user devices 38-42 and the public network 36, from merchants via the merchant devices 44-52 and the public network 36, etc. For example, a user device 38-42 may access a web site running on the payment entity device 12 (e.g., Visa, Inc.’s web site) to obtain information regarding various credit card offers 30 supported by Visa, Inc. As another example, a user device 38-42 may access an issuer device 32-34 via the public network 36 to obtain current information regarding the user’s account with the issuer, on-line bill payment, open a new account, etc.
In addition to accessing the payment entity device 12 via the public network 36, a user device 38 may have access to a proprietary gateway 26 to access the payment entity device 4 12 via the proprietary network 16 for a proprietary service (e.g., accounts payable, accounts receivable, financial reporting, elite class offers, etc.). Note that the proprietary gateway 26 may be a proprietary node, modem, bridge, etc., that serves as a public connection point to the proprietary network 16. The proprietary gateway 26 functions to ensure that only authorized 5 entities (e.g., user device 38) have access to the proprietary network 16. 2015204328 15 Jul 2015
As mentioned, the system 10 may support mobile payment transactions initiated by a mobile payment device 54-56. During the processing of a credit payment transaction initiated by the mobile payment device 54-56, the mobile payment device 54-56 may obtain a credit image data and display it. The credit image data may be retrieved from memory, from a 10 financial institution server (e.g., the payment entity device 12, an issuer device 32-34, or an acquirer device 28-30), from a contactless payment module, from a corresponding user device 38-42. etc. The processing, determining, generating, retrieving, and/or displaying of credit image data will be described in greater detail with reference to Figures 2-11.
Figure 2 is a schematic block diagram of an embodiment of a mobile payment 15 device 54-56 that includes a contact less payment module 60, a processing module 62, a display module 64, and a bus 72. The display module 64 may include a display 66 (e.g., a Liquid Crystal Display (LCD) display, a Digital Light Projection (DLP) display, etc.) The processing module 62 may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central 20 processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module 62 may have an associated memory 70 and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the 25 processing module. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing module 62 implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory 70 and/or memory element storing 30 the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Further note that, the memory element stores, and the processing module 62 executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in Figures 2-11. Even further note that the mobile payment device 54-56 may include a wireless 5 transceiver 74 that provides cellular (e.g., voice) and data (e.g., email, internet access, etc.) telephone functionality for the mobile payment device 54-56. 2015204328 15 Μ 2015
In operation, the contactless payment module 60 executes a credit payment transaction. In general, when the contactless payment module 60 is proximal to a point of sale 5 terminal (e.g., for point of sale transactions), the contactless payment module 60 exchanges data (e.g., account information, purchase price, etc.) with the point of sale terminal via radio frequency (RF) signals and/or electromagnetic coupling signals. For example, the contactless payment module may be a subscriber identity module (STM) having a radio frequency identification (RFID) interface; a smart card with the RFID interface; a SIM having a near field 10 communication (NFC) interface; and/or a smart card with the NFC interface. In addition to point of sale transactions, the contactless payment module 60 may provide a remote-based transactions (e.g., internet or Short-Message-Service (SMS) based e-commerce transactions) payment method and/or money transfers between mobile payment devices.
The processing module 60 is coupled to detect the executing of the credit payment 15 transaction. For example, the processing module 60 detects the data exchange between the contactless payment module 60 and the point of sale terminal and/or receives a signal from the contactless payment module 60 indicating initiation of the credit payment transaction. After detecting the executing, the processing module 62 retrieves credit image data. The processing module 62 may retrieve the credit image data from memory 70 and/or from the contactless 20 payment module 60. Alternatively, or in addition to, the processing module 62 may retrieve the credit image data from a financial institution server (e.g., the payment entity device 12, an issuer device 32-34, or an acquirer device 28-30) via the wireless transceiver 74.
As an example of retrieving the credit image data at least partially from a financial institution server, the processing module 62 sends a retrieval message to the wireless transceiver 25 74 upon detecting the execution of the credit payment transaction. The wireless transceiver 74 converts the retrieval message into an RF signal that is transmitted to a cellular tower (not shown), which converts the RF signal into a data message that is forwarded to the financial institution server via the public network 36. The financial institution server processes the retrieval message to identify the user, the user’s credit image data and any other pertinent data. 30 The financial institution sends the user’s credit image data to the wireless transceiver 74 via the reverse path from which it received the request message. The wireless transceiver 74 recovers the credit image data from the received RF signal to produce recovered credit image data and provides the recovered credit image data to the processing module 62. 6
The processing module 62 coordinates the credit image data being provided to the display module 64. The graphics engine 68 (which may be a video graphics accelerator, a video decoder, an LCD driver, a DLP driver, etc.) processes the credit image data to produce a displayed credit image that is displayed via the display 66. 2015204328 15Jul2015 5 Figure 3 is a diagram of an example of a credit image displayed on the display 66 of a mobile payment device 54-56. In this example, the credit image data includes a master image layer 80 (e.g., issuer’s logo, credit card logo, cardholder’s name, account number, expiration date, issuance date, etc.) and a design image layer 82 (e.g., a race car character). The design layer 82 may be a custom design image layer (e.g., a digital image provided by the user of the 10 mobile payment device 54-56) and/or one of a plurality of approved design image layers offered by the financial institution that operates the financial institution server.
Figure 4 is a logic diagram of an embodiment of a method for credit image data processing that may be performed by the processing module 62. The method begins at step 90 where the processing module 62 detects the executing of the credit payment transaction by the 15 contactless payment module 60. In addition to detecting the executing of the payment transaction, the processing module 62 may detect a type of the credit payment transaction (e.g., credit card, debit card, commercial purchase card, pre-pay card, corporate card, etc.).
The method then proceeds to step 92 where the processing module 62 retrieves the credit image data based on the detecting of the executing of the credit payment transaction. The 20 processing module 62 may retrieve the credit image data in a variety of ways. For example, the processing module 62 may retrieve the credit image data from the memory 70, which stores the credit image data and may further store a plurality of credit image data. If the memory 70 is storing a plurality of credit image data, then the processing module 62 may retrieve one of a plurality of credit image data based on the type to provide the credit card image or in accordance 25 with a retrieval scheme (e.g., round robin, random, user’s ordering, etc.). Alternatively, or in addition to, the processing module 62 may retrieve the credit image data from a financial server via the wireless transceiver 74. As yet another alternative, the processing module 62 may retrieve the credit image data from the contactless payment module 60.
The method then proceeds to step 94 where the processing module 62 sends the 30 credit image data to the display module 64. The display module 64 processes the credit image data to render on image on the display 66.
Figure 5 is a diagram of another example of credit image data that includes the master image layer 80, the design image layer 82, and may further include a transactional image layer 100. The transactional image layer 100 includes data relating to the current purchase (e.g., 7 purchase amount, available balance, etc.) and other relevant data regarding the account (e.g., next payment due date, amount due, recent purchases, etc.). 2015204328 15 Μ 2015
The processing module 62 may receive the transactional image layer 100 from the financial institution via the wireless transceiver 74. For instance, in response to the retrieval 5 message sent via the wireless transceiver, the wireless transceiver receives a radio frequency (RF) signal from a financial institution server, wherein the RF signal includes the transactional data. The wireless transceiver 74 recovers the transactional data from the RF signal to produce recovered transactional data and provides the recovered transactional data to the processing module 62. The processing module 62 generates the transactional image layer 100 of the credit 10 image data based on the recovered transactional data.
In an embodiment, the processing module 62 may process the master image layer 80 and the transactional image layer 100 such that display 66 alternates presenting the master image and the transactional image. Alternatively, the processing module 62 may process a request from the user to display one or the other of the master image and the transactional image, 15 to jump between the two, or to not display one or more of the image layers.
Figure 6 is a logic diagram of another embodiment of a method for credit image data processing that may be performed by the processing module 62. The method begins at step 110 where the processing module 62 detects the executing of the credit payment transaction as previously discussed. The method continues at step 112 where the processing module 62 20 retrieves the credit image master layer from memory in accordance with the detecting. For instance, as soon as the processing module detects the executing, it begins the retrieval process. Note that the processing module 62 may retrieve the master image layer from memory 70, from a financial institution server via the wireless transceiver 74, and/or from the contactless payment module 60. 25 The method then proceeds to step 114 where the processing module 62 retrieves one of the plurality of digital images from memory 70 in accordance with the detecting. The retrieval may further be done in accordance with a retrieval scheme. Note that the mobile payment device 54-56 may be a cellular telephone with a built-in digital camera such that the digital images stored in memory 70 are a collection of pictures taken by an operator of the device 30 54-56. As part of the retrieval process, the processing module 62 may perform an appropriateness check of the image before providing it to the display module 64.
Such a check begins at step 118 where the processing module 62 determines content of the digital image. The method continues at step 120 where the processing module 62 analyzes the content of the image to determine whether it contains inappropriate content. For example, 8 the processing module 62 may perform an image recognition algorithm to identify potentially inappropriate objects within the image. If, at step 122, the image does not include inappropriate content, the method continues at step 124 where the processing module retrieves the digital image from memory and provides it to the display module 64. If, however, the image potentially 5 includes inappropriate content, the method proceeds to step 126 where the processing module selections another digital image for appropriateness checking. 2015204328 15 Μ 2015
The method then proceeds to step 116 where the processing module 62 generates credit image data based on the credit image master layer and the one of the plurality of digital images. The processing module 62 may further process a transactional image layer into the 10 credit image data, wherein the transactional image layer is based on recovered transactional data.
Figure 7 is a schematic block diagram of an embodiment of a contactless payment module 60 that includes a key module 130, memory 132, a contactless interface 134, and a memory interface 136. The key module 130 contains a unique subscriber identification code and credit transactional information in accordance with a mobile payment protocol. In an 15 embodiment, the unique subscriber identification code may be an International Mobile Subscriber Identity (IMSI). The contactless interface 134 transmits at least one of the unique subscriber identification code and the credit transactional information during execution of a credit transaction. In an embodiment, the contactless interface a radio frequency identification (RFID) interface and/or a near field communication (NFC) interface. 20 The memory 132, which may be memory as previously defined, stores a credit image data that may be retrieved via the memory interface 136 by the processing module 62 or other device, module, etc. The credit image data includes a master image layer and a design image layer, which may be a custom design image layer and/or one of a plurality of approved design image layers. 25 Figure 8 is a schematic block diagram of an embodiment of a financial transaction apparatus 140, which may be included within, or associated with, the payment entity device 12, an issuer device 32-34, and/or an acquirer device 28-30. The apparatus 140 includes a processing module 142, memory 144, and an interface 146, which may be a wireless and/or a wired interface that enables the apparatus 140 to access the public network 36. The processing 30 module 142 may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or 9 operational instructions. The processing module 142 may have an associated memory 144 and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the processing module. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, 5 dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing module 142 implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory 144 and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital 10 circuitry, and/or logic circuitry. Further note that, the memory element stores, and the processing 2015204328 15 Μ 2015 module 142 executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in Figures 9-11.
Figure 9 is a logic diagram of another embodiment of a method for credit image data processing that may be processed by the processing module 142. The method begins at step 15 150 where the processing module 142 receives, via the interface 146, a digital image from a user via a user device 38-42 and/or via a mobile payment device 54-56. The method then proceeds to step 152 where the processing module 142 determines content of the digital image. The method continues at step 154 where the processing module 142 analyzes the content of the digital image to determine whether it contains inappropriate content. This may be done use image recognition 20 software to identify potentially inappropriate objects, gestures, etc. within the digital image.
If the digital image docs not include inappropriate content, the method branches from step 156 to step 158 where the processing module 142 generates a design image layer based on the digital image. The method continues at step 160 where the processing module retrieves from memory 144 a master image layer. The method continues at step 162 where the processing 25 module 142 processes the design image layer and the master image layer to produce credit image data. The method continues at step 164 where the processing module 142 transmits, via the interface 146, the credit image data.
If the digital image does include inappropriate content, the method branches from step 156 to step 166 where the processing module 142 rejects the present digital image and 30 begins processing another if one is available.
Figure 10 is a logic diagram of another embodiment of a method for credit image data processing that begins at step 170 where the processing module 142 receives, via the interface 146, an indication of an execution of a credit payment transaction by a mobile payment device. The method continues at step 172 where the processing module 142 determines an 10 identity of a mobile payment device based on the indication. The method continues at step 174 where the processing module 142 generates a transactional data image layer based on at least one of transactional data of the mobile payment device and the credit payment transaction. The method continues at step 176 where the processing module 142 generates a credit image data 5 based on a design image layer, a master image layer, and the transactional data image layer. The 2015204328 15 Μ 2015 method continues at step 178 where the processing module 142 transmits, via the interface 146, the credit image data to the mobile payment device.
Figure 11 is a logic diagram of another embodiment of a method for credit image data processing that begins at step 180 where the processing module 142 receives, via the 10 interface 146, a request for credit image data from a mobile payment device. The method continues at step 182 where the processing module 142 retrieves the credit image data based on identity of mobile payment device. The method continues at step 184 where the processing module 142 provides, via the interface 142, the credit image data to the mobile payment device. The credit image data may include a master image layer and a design image layer, which may be 15 a custom design image layer and/or one of a plurality of approved design image layers.
In addition to steps 180-184, the processing module 142 may further function to: receive, via the interface 146, an indication of an execution of a credit payment transaction from the mobile payment device; generate a transactional data image layer based on at least one of transactional data of the mobile payment device and the credit payment transaction; and generate 20 the credit image data based on the design image layer, the master image layer, and the transactional data image layer.
As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, 25 but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “coupled to” and/or “coupling” and/or includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a 30 component, an element, a circuit, and/or a module) where, for indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term 11 “operable to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item 5 being embedded within another item. As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. 2015204328 15 Jul 2015 10 The present invention has also been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate 15 boundaries or sequences are thus within the scope and spirit of the claimed invention.
The present invention has been described above with the aid of functional building blocks illustrating the performance of certain significant functions. The boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are 20 appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention. One 25 of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof. 12
Claims (7)
- CLAIMS:1. A contactless payment module comprising: a key module that contains a unique subscriber identification code and transactional information; a memory configured to store payment image data; a contactless interface configured to transmit at least one of the unique subscriber identification code and the transactional information during execution of a transaction; and a memory interface configured to output the payment image data during the execution of the transaction.
- 2. The contactless payment module as defined in Claim 1 functions to execute a payment transaction.
- 3. The contactless payment module as defined in Claim 1, wherein the contactless interface comprises at least one of: a radio frequency identification (RFID) interface; and a near field communication (NFC) interface.
- 4. The contactless payment module as defined in Claim 1, wherein the payment image data comprises: a master image layer; and a design image layer.
- 5. The contactless payment module as defined in Claim 4, wherein the master image layer comprises a rendering that includes: a name of an account holder of an account issued by an issuer to the account holder, wherein the transaction can be conducted upon the account; an account number corresponding to the account; and an expiration date of the account.
- 6. The contactless payment module as defined in Claim 1, wherein the unique subscriber identification code comprises an International Mobile Subscriber Identity (IMSI).
- 7. The contactless payment module as defined in Claim 4, wherein the design image layer comprises a rendering that includes: a custom design image layer comprising a digital image provided by a user of the mobile payment device, or one of a plurality of approved design image layers offered by a financial institution that operates a financial institution server configured to communicate with the contactless payment module.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| AU2015204328A AU2015204328B2 (en) | 2008-08-23 | 2015-07-15 | Payment card imaging for mobile payment |
| AU2017203440A AU2017203440B2 (en) | 2008-08-23 | 2017-05-23 | Payment card imaging for mobile payment |
Applications Claiming Priority (7)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US9134308P | 2008-08-23 | 2008-08-23 | |
| US61/091,343 | 2008-08-23 | ||
| US12/326,873 US8103249B2 (en) | 2008-08-23 | 2008-12-02 | Credit card imaging for mobile payment and other applications |
| US12/326,873 | 2008-12-02 | ||
| AU2009288405A AU2009288405B2 (en) | 2008-08-23 | 2009-08-24 | Payment card imaging for mobile payment |
| PCT/US2009/054812 WO2010027752A2 (en) | 2008-08-23 | 2009-08-24 | Credit card imaging for mobile payment and other applications |
| AU2015204328A AU2015204328B2 (en) | 2008-08-23 | 2015-07-15 | Payment card imaging for mobile payment |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2009288405A Division AU2009288405B2 (en) | 2008-08-23 | 2009-08-24 | Payment card imaging for mobile payment |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2017203440A Division AU2017203440B2 (en) | 2008-08-23 | 2017-05-23 | Payment card imaging for mobile payment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| AU2015204328A1 AU2015204328A1 (en) | 2015-08-06 |
| AU2015204328B2 true AU2015204328B2 (en) | 2017-03-16 |
Family
ID=53761661
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2015204328A Ceased AU2015204328B2 (en) | 2008-08-23 | 2015-07-15 | Payment card imaging for mobile payment |
| AU2017203440A Ceased AU2017203440B2 (en) | 2008-08-23 | 2017-05-23 | Payment card imaging for mobile payment |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2017203440A Ceased AU2017203440B2 (en) | 2008-08-23 | 2017-05-23 | Payment card imaging for mobile payment |
Country Status (1)
| Country | Link |
|---|---|
| AU (2) | AU2015204328B2 (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060219776A1 (en) * | 2003-11-17 | 2006-10-05 | Dpd Patent Trust | Rfid reader with multiple interfaces |
| US20070288371A1 (en) * | 2006-05-25 | 2007-12-13 | Johnson Aratha M | Personal electronic payment system and related method |
-
2015
- 2015-07-15 AU AU2015204328A patent/AU2015204328B2/en not_active Ceased
-
2017
- 2017-05-23 AU AU2017203440A patent/AU2017203440B2/en not_active Ceased
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060219776A1 (en) * | 2003-11-17 | 2006-10-05 | Dpd Patent Trust | Rfid reader with multiple interfaces |
| US20070288371A1 (en) * | 2006-05-25 | 2007-12-13 | Johnson Aratha M | Personal electronic payment system and related method |
Also Published As
| Publication number | Publication date |
|---|---|
| AU2017203440A1 (en) | 2017-06-08 |
| AU2015204328A1 (en) | 2015-08-06 |
| AU2017203440B2 (en) | 2019-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10706424B2 (en) | Device including image including multiple layers | |
| US11887077B2 (en) | Generating exchange item utilization solutions in an exchange item marketplace network | |
| US8880432B2 (en) | System and method of using electronic funds transfer to complete payment for goods and services | |
| TWI435282B (en) | Techniques for authorization of usage of a payment device | |
| US11164228B2 (en) | Method and medium for determining exchange item compliance in an exchange item marketplace network | |
| US20030154139A1 (en) | Secure m-commerce transactions through legacy POS systems | |
| US20130013502A1 (en) | Facilitation of Transactions Using a Transaction Code | |
| US20210117941A1 (en) | Application program interface for conversion of stored value cards | |
| US20200410525A1 (en) | Use of Payment Card Rewards Points for an Electronic Cash Transfer | |
| US20220318866A1 (en) | Payment system and method | |
| EP2660764A1 (en) | System and method for effecting payment to a beneficiary including a real-time authorisation of the payment | |
| US20100316204A1 (en) | Methods and Systems for Optimizing Online Order Process Flow | |
| US20230125366A1 (en) | Securely utilizing an exchange item unaffiliated with a merchant server | |
| US12159286B2 (en) | Systems and methods for executing parallel electronic transactions | |
| AU2017203440B2 (en) | Payment card imaging for mobile payment | |
| WO2016032519A1 (en) | Before-the-fact budgeting | |
| US20190114602A1 (en) | Configuration Tool for Payment Processing | |
| WO2014124492A1 (en) | Payment system and method | |
| AU2015201521A1 (en) | System and method for a merchant debit card program including a plurality of issuers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FGA | Letters patent sealed or granted (standard patent) | ||
| MK14 | Patent ceased section 143(a) (annual fees not paid) or expired |