as) United States
`a2) Patent Application Publication 0) Pub. No.: US 2008/0275779 Al
`
`(43) Pub. Date: Nov.6, 2008
`Lakshminarayanan
`
`US 20080275779A1
`
`(54) MOBILE PAYMENT SERVICES
`
`(76)
`
`Inventor:
`
`Dhamodharan
`Lakshminarayanan, Austin, TX
`(US)
`
`Correspondence Address:
`Quarles & Brady LLP
`TWO NORTH CENTRAL AVENUE,One Renais-
`sance Square
`PHOENIX, AZ 85004-2391 (US)
`
`(21) Appl. No.:
`
`12/027,809
`
`(22)
`
`Filed:
`
`Feb. 7, 2008
`
`Related U.S. Application Data
`
`(60)
`
`Provisional application No. 60/889,443, filed on Feb.
`12, 2007.
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`(2006.01)
`G060 20/00
`(2006.01)
`G060 30/00
`(52) US. CMe cescccscssssssssssseeseeessseessesssen 705/14; 705/39
`(57)
`ABSTRACT
`
`A Java2 Enterprise Edition (J2EE) enabled server executing
`Java software provides a financial transaction Web service to
`a client each of which communicates wirelessly with the
`J2EE enabled server and executes Java software to conduct
`financial transactions between a merchant and a consumer
`upon an account issued by an issuer to the consumer. Each
`financial transaction is submitted by the merchant to an
`acquirer for processing bya transaction handler/paymentpro-
`cessor, and is submitted by the transaction handler/payment
`processor to the issuer to obtain a payment amount for the
`financial transaction from the account, and wherein the issuer
`forwards the payment amountofthe financial transaction to
`the transaction handler/payment processor who forwards the
`payment amountofthe financial transaction to the acquirerto
`pay the merchantfor the financial transaction.
`
`Enrollment Business Model
`
`— 606
`
`600 ~
`
`-— 608
`
`OBTAIN CODE SIGNING CERTIFICATE
`FROM CERTIFICATE AUTHORITY
`
` Payment
`
`ENROLLMENT USING
`‘— BULK MERCHANT
`FILE UPLOAD
`
`
`
`
`
`
`Gateway
`ENROLLMENT USING
`
`\
`BULK CONSUMER
`FILE UPLOAD
`
`\ \
`
`\
`
`\
`
`\
`
`\
`
`aN
`
`N\
`
`
`
`Transaction
`Handler/
`Payment
`Processor
`
`
`
`604
`
`
`
`Issuer
`
`Initiate
`Enrollment
`Request
`
`— 610
`
`é
`
`;
`Acquirer
`
`Initiate
`Enrollment
`Request
`
`Merchant
`
`
`
`
`
`“ “
`
`ms
`
`‘ \
`616 —.
`4 oo
`cee
`Overthe Air:
`Downloads;
`Upgrades;
`Signed/Trusted
`)
`Smart Client
`Bee,
`UN co ~
`#
`Lc
`\
`Lc
`\
`
`\
`
`\
`
`\
`
`~~
`
`|
`
`\
`
`— 602
`
`yo |
`
`|
`Consumer
`Wireless Client With
`— 612
`|
`Smart Client
`
`| Preinstalled—|
`|
`By Manufacturer
`Lo J
`
`\
`
`614
`
`1
`
`SAMSUNG 1008
`
`SAMSUNG 1008
`
`1
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 1 of 18
`
`US 2008/0275779 Al
`
`102
`
`»
`
`/
`
`104
`
`i
`/
`
`Server
`
`Workstation
`
`»
`
`106
`
`|
`
`108
`
`j
`/
`i
`
`110
`
`»
`
`/
`
`
`
`Commun-
`ications:
`Palmtop
`Computer,
`Personal
`Digital
`Assistant
`
`Point of
`Sale
`Terminal
`
`PC, Laptop
`
`Network
`Card
`
`Pager
`g
`
`
`
`Settop Box
`Network TV
`
`Screen
`Phone
`
`Smart
`Card
`
`by po
`|
`CDC
`|
`|
`CLDC
`|
`
`Java 2
`Enterprise
`Edition
`
`|
`|
`|
`
`Java 2
`Standard
`Edition
`
`Sava2
`Edition
`(J2ME)
`
`Java Language
`
`
`
`[
`
`|CompactJava [Card
`Java
`—[
`Hot Spot
`|
`Virtual Machine
`virtual
`|Virtual
`|
`(JVM)
`|
`uv
`Machine
`|
`_|
`(KVM)
`(CVM)
`
`10 MB €
`------------------- >1Mb
`512kB€ 332kB
`
`Memory:
`
`64 bit
`
`32 bit
`
`16 bit
`
`8bit
`
`wo%
`
`a
`
`Figure 1
`
`2
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 2 of 18
`
`US 2008/0275779 Al
`
`i 200
`
`Applications: Payment; Identity; Loyalty; Transit
`
`MIDP: User Interface, HTTP networking, etc.
`
`MIDlet Suite: Applications written in the Mobile Information
`Device Profile (MIDP) specification for a J2ME profile:
`
`Digital Signal Processor (e.g., ARM, etc.)
`
`J2ME Core APIs
`
`Compact Java Virtual Machine (KVM):
`Threads, no Floats...
`
`Figure 2
`
`3
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 3 of 18
`
`US 2008/0275779 Al
`
`ne
`
`300
`
`Client Tier
`
` | HTTPS
`
`
`
`
`
`Client Communicators:
`Palmtop Computer, PDA;
`PC (HTML Browser),
`Laptop;
`Smart Phone;
`Cell Phone (J2ME GUI (Midlets with
`XML Parser)
`
`Back End Tier J2EE Application Server/
`
`Web
`Server
`(HTML Images)
`
`Servlet Engine
`(JSP Servlets Presentation Beans)
`
`Middleware Tier
`
`EJB Container
`
`Figure 3
`
`4
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 4 of 18
`
`S 2008/0275779 Al
`
`JSR-82 Specification
`
`400
`
`5 U
`
`Figure 4
`
`Javax.bluetooth
`
`Bluetooth
`Protocol
`Stack
`
`Bluetooth
`Radio
`
`5
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 5 of 18
`
`US 2008/0275779 Al
`
`Layer IV:
`Transaction Handler/ Payment Processor Gateway:
`Performs Authorization and Credit Request From Gateway
`
`Layer Ill:
`Transaction Handler/ Payment Processor Gateway:
`- Authenticates/authorize mobile client
`- Handles User Enroll Request
`- Activates Smart Client
`- Converts incoming mobile msg into ISO 8583 financial msg
`- Interacts with Gateway Systems: SMS & Base1
`- Offers Administrative operations for Member Bank
`
`XML HTTPS
`
`- Performs cryptography function
`
`Layer Il:
`Smark Client Layer:
`- Enhanced User experience
`- Secured network capability
`- On-device data persistence support
`- Multi-Lingual Support
`- Multi-Card Wallet application
`- Multi-Function applications Package
`- OVER-THE-AIR Download
`- Session Based stateful Conversation
`- Multi-Thread Support
`- Size < 200 kB
`
`APDU Protocol (ISO 7816-4 Format)
`
`Layer I: Secure Element Layer (Smart Card or SIM Card):
`- Tamper-resistant
`- Connected temporarily or permanently
`- Contains user credentials
`
`Figure 5
`
`6
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 6 of 18
`
`US 2008/0275779 Al
`
`
`EnrollmentBusinessModel_ ,,
`600 ‘\
`Transaction
`
`Handler/
`Payment
`
`Processor
`
`/
`
`608
`
`OBTAIN CODE SIGNING CERTIFICATE
`
`FROM CERTIFICATE AUTHORITY
`
`Payment
`Gateway
`
`— 604
`
`\BULKCONSUMER /
`
`60
`/
`ENROLLMENT USING
`
`FILE UPLOAD
`‘ .
`Issuer
`\
`ENROLLMENTUSING\
`'_ BULK MERCHANT —
`\
`FILE
`UPLOAD
`
`
`
`
`
`\
`
`\
`
`\
`
`,
`
`/
`
`/
`
`610
`
`.
`
`oo
`
`~~ a
`
`L
`
`Initiate
`Enrollment
`Request
`
`Merchant
`
`\
`\_ 612
`
`616 — ‘.
`ee ~
`/ Overthe Air:
`|
`Downloads,
`Lo
`fo
`Upgrades;
`|
`Signed/Trusted
`“Smart Client
`eo
`\
`~a
`oo
`\
`
`\ ee
`
`\
`)
`
`\
`
`\
`
`\
`
`\
`
`Initiate
`Request
`
`Enrollment
`
`_~
`
`Consumer
`
`\
`
`\
`\— 602
`
`|
`|
`Consumer
`Wireless Client With |
`Smart Client
`.
`Preinstalled
`|
`
`By Manufacturer
`
`|
`|
`|
`
`|
`
`7
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 7 of 18
`
`US 2008/0275779 Al
`
`Proximity Payment
`Transaction Flow
`
`y— 100
`
`Transaction
`Handler/
`Payment
`Processor
`
`Acquirer
`
`Payment
`
`Gateway
`
`Wireless Client
`
`Consumer
`
`Wireless Internet
`HTTPS
`
`Merchant:
`POS or
`Wireless Client
`
`FINANCIAL APPLICATION
`UsING NEC oR
`BLUETOOTH OR
`OBEX OVER IRDA OR
`SMS oR
`NEC + BLUETOOTH
`OR RFID:
`CUSTOMER INVOICE /
`CONSUMER
`CREDIT CARD
`EXCAHNGE
`
`8
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 8 of 18
`
`US 2008/0275779 Al
`
`P2P Payment: Send and Notify
`Sender's
`i 800
`
`Consumer
`
`Wireless Client Receiver 1D
`
`
`
`
`54122577077
`
`Amount
`
`
`
`$200
`
`The Arnount $200 has
`been sent to John
`successfully
`
`Receiver Details
`
`First Name = John
`
`Last Name: Mike
`City : Austin
`Amount: $200
`
`Send
`
`t
`p
`aymen
`Gateway
`
`Authorization
`
`Credit
`Transaction
`
`Figure 8
`
`Eirst Name - John
`Last Name : Mike
`
`— 826
`
`Payment Processor
`
`Mobile: 5123003101
`Noatification Transaction Handler/
`
`
`Notify
`
`6:
`Push: SMS Msg
`Smart Cllent
`Auto-Launch
`
`\
`Receiver’s
`Consumer
`Wireless Client
`
`Credit
`Transaction
`
`Authorization
`
`“You get
`Money!"
`
`Issuer:
`Sender
`
`Issuer:
`Receiver
`
`\
`
`\__ go4a
`
`\__ g04b
`
`9
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 9 of 18
`
`Mobile Payment
`
`900
`
`Your Challenge
`{29678
`
`enier Response
`
`
`
`Enter Challenge
`
`A29678
`
`
`
`
`
`Enter FIN
`baieoe
`
`Figure 9
`
`Lr US 2008/0275779 Al
`
`Enter Your iB
`
`{2578900
`
`
`
`Get Challenges
`
`Pick or skip Address
`from Address Book
`
`Verify Merchant
`
`WWW.Amazon.com
`
`$300
`
`
`Your Response
`BEGIZ3
`
`
`
`Your Chaflenge
`129678
`
`Enter Response
`Seso23
`
`Your Shipping Address
`
`7011 W Farmer Ln,
`#833, Austin,
`
`Submit
`
`10
`
`Payment
`Gateway
`
`1 authorize
`this online
`ransactigy
`
`Consumer
`Wireless Client
`
`10
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 10 of 18
`
`US 2008/0275779 Al
`
`Virtual Account Management
`
`Wireless Client
`
`Select Wallet iD
`
`Wells Fargoi23
`
`BOFAZ
`
`Chaset
`
`Submit
`
`Your Virtual Account
`Account:
`
`1234567890 123456
`
`Pin: 1234
`
`Wallet ID:WelisFargo123
`Nexg
`
`y~ 1000 Consumer
`
`
`Enter Expiry Date
`Enter Virtual Account
`
`
`
`SSUES
`AaES
`4 AO M2007
`
`
`1294567 890 123455
`;
`
`Max Transactions
`
`
`5
`PING
`pee
`
`
`Max Amount
`
`
`500
`
`Transaction
`Handler/
`Payment
`Processor
`
`Payment
`Gateway
`
`11
`
`11
`
`

`

`Patent Application Publication
`Nov. 6, 2008 Sheet 11 o0f18|=US 2008/0275779 Al
`
`Mobile Loan Transaction
`
`Consumer
`Wireless Client
`
`y 1100
`
`Set a electronic POS
`Check for $3000 From
`
`—@Q— Web Service
`
`Payment
`Gateway
`
`
`Communication
`
`5:
`Real-tlme
`Credit Check
`
`Credit
`Agency
`\\
`
`Transaction
`Handler/
`Payment
`Processor
`
`\— 1118
`
`Figure 11
`
`12
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 12 of 18
`
`US 2008/0275779 Al
`
`Mobile Fraud Notification
`
`Consumer
`Wireless Client
`
`a 1200
`
`Fraud Alert Max
`§ Amount
`
`0
`
`Payment
`Gateway:
`Real-Time
`Anti-Fraud
`Detection
`System
`
`4:
`CMLS/CDI
`Infrastructure
`
`5:
`Real-tlme
`Fraud
`Alert
`
`— 1206
`
`Figure 12
`
`
`
`AccountActivities:
`Authorization;
`Clearing and
`settlement;
`Other
`
`Consumer
`
`
`
`Select Wallet 1D
`
`Wells Fargoi23
`BOFAZ
`
`Chase’
`
`fT 1224
`
`/
`
`
`Wireless Client \
`
`13
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 13 of 18
`
`US 2008/0275779 Al
`
`Mobile Auto Bill Pay
`
`Wireless Client
`
`Consumer
`
`Your Auto Pay Account
`
`Account:
`
`1234567890 123456
`Wallet [D:WellsFargo1Z3
`
`OK
`
`Generate Permanent
`(Never Expire) Auto
`Pay Account Number
`for Auto Bill Pay
`
`Next
`
`Select Wallet 1D
`
`Nelis Fargo i22
`
`BOFA2
`Chase}
`
`fo 1300 1302 ,
`
`Payment
`Gateway
`
`e-Bill Pay
`Merchant
`www.\VerizonWireless.com
`
`Figure 13
`
`14
`
`14
`
`

`

`Patent Application Publication
`Nov. 6, 2008 Sheet 14 0f18|=US 2008/0275779 Al
`
`Mobile Identity Theft Alert
`
`,
`
`1404
`
`Issuer
`
`Attemptto issue
`new credit or debit
`card in consumer’s
`
`name
`
`
`a Payment Processor
`
`
`
`
`
`1408 —,
`\
`
`
`
`Payment
`Gateway
`
`1:
`HTTPS
`Load New
`AccountIn
`Consumer’s
`Name
`
`
`Validate and Load
`New Account File
`
`
` 2:
`4: +Gateway Sends
`
`//
`
`/\
`/
`\
`|
`|
`\
`\/
`\VY
`
`Database
`
`\
`
`SMS Message to
`auto-launch
`smart client to
`renderalert
`
`1402 —
`
`Wireless Client
`
`Consumer
`
`Figure
`
`14
`
`15
`
`15
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 15 of 18
`
`US 2008/0275779 Al
`
`Consumer Account Loading
`At Mobile Merchant
`
`fo 1500
`
`7— 1530
`
`/
`
`LW
`
`Wireless
`4:
`y
`| A ~_. Cash/check a
`i \\
`Payment
`Consumer
`
`
`Gateway
`
`>.
`
`— 1512
`
`Send: Account
`and Amount
`
`Payment
`
`3:
`Transaction:
`Amount Credited
`To Account
`
`Transaction
`Handler/
`Payment
`
`Processor
`
`4:
`Transaction:
`Amount Credited
`To Account
`
`Figure 15
`
`ss
`
`16
`
`16
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 16 of 18
`
`US 2008/0275779 Al
`
`Mobile Activation and Security
`
`7 1630
`
`/
`.
`f
`1:
`<.
`i
`hs _séEnter
`A
`Credentials
`i/ \\
`and
`Consumer
`PIN
`
`1600
`
`fr
`
`Consumer
`Wireless Client
`
`
`
`\
`
`1602a
`
`2:
`Send: Credentials
`and PIN
`
`/
`
`
`[~ 1608
`
`
`Seeeaeney
`Transaction Handler/
`
`credentials/other data
`Payment Processor
`
`é
`
`
`
`3:
`Return:
`- Hash Msg Digest,
`- e-Wallet Details,
`- Dynamic keypair
`
`Consumer
`Client/Smart Card/
`SIM CARD
`
`Figure 16
`
`17
`
`17
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 17 of 18
`
`US 2008/0275779 Al
`
`Mobile Client Authentication
`
`y- 1700
`
`-—— 1730
`
`/
`4:
`Consumer
`JO
`Enter Valid
`Wireless Client:
`Ith
`Execute
`\
`PIN
`,
`
`
`‘| Transaction=}\(Max 3
`,
`icati
`UM}
`Attempts)
`Application
`
`
`
`1702
`
`Consumer
`
`2:
`
`Send At End of
`Transaction:
`- Dynamic Key;
`- Static Msg Digest
`
` —
`
`/ 1706
`
`Transactionfancier
`ay
`
`/ 1708
`
`Payment Gateway:
`Validate and Hash
`credentials/other data
`
`Figure 17
`
`18
`
`18
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 18 of 18
`
`US 2008/0275779 Al
`
`y_ 1800
`
`Figure 18
`
`19
`
`

`

`US 2008/0275779 Al
`
`Nov. 6, 2008
`
`MOBILE PAYMENT SERVICES
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application is a Non-Provisional Application
`and claims priority to, and the benefit of, U.S. Provisional
`Application Ser. No. 60/889,443, filed Feb. 12, 2007, entitled
`“MOBILE SERVICES,” the entire contents of which is
`hereby incorporated by reference.
`
`FIELD
`
`Implementations generally relate to financial trans-
`[0002]
`actions, and is more particularly related to financial transac-
`tions conducted with a mobile consumerelectronics device.
`
`BACKGROUND
`
`[0003] Consumertransactions with merchants are increas-
`ingly being made payable with other than cash or checks.
`Morerecently, the device being used by consumers to conduct
`such consumertransactions is a mobile consumerelectronics
`
`device having wireless communications functionality, such
`as acellular telephoneor a Personal Digital Assistant (PDA).
`Such mobile consumerelectronics devices lack interoperabil-
`ity.
`[0004] One application protocol used by mobile consumer
`electronics devices having wireless communications func-
`tionality is I the Wireless Application Protocol (WAP). WAP,
`however,hasits limitations. WAP requires key improvements
`in security, and also requires constant air time for offline
`operations. WAP places limitations on a rich user interface,
`and lacks compatibility between micro-browsers. WAP
`required different gateways from different vendors
`[0005] Another such protocolis I-mode protocol, which is
`a wireless data service that is accessed by a wireless packet
`network and the contents are described in a subset of the
`
`HTMLlanguage. One problem with the I-mode protocol is
`that there is no client side scripting languagelike the Wireless
`Markup Language (WML), where WMLis a language that
`allows the text portions of Web pages to be presented on
`cellular telephones and personaldigital assistants (PDAs) via
`wireless access. Also, the I-Mode protocolis not available in
`all geographic regions.
`[0006] Consequently, there is a needin the art to provide a
`mobile consumerelectronics device having wireless commu-
`nications functionality by which a consumer can conduct a
`cashless transaction on an account issued to the consumerby
`an issuer, where the transaction is conducted by the consumer
`with a merchant, and where executable instructions enabling
`the transaction on the mobile device will interoperate on a
`variety of different mobile devices (e.g.; cellular telephones,
`PDAs, palmtop computers, etc.) as one application offering
`different types of financial transactions and multiple related
`services.
`
`SUMMARY
`
`In one implementation, a wireless financial transac-
`[0007]
`tion system includes a Java 2 Enterprise Edition (J2EE)
`enabled server executing a Java software productto provide a
`financial transaction Web service to Web enabled clients.
`Eachclient is served the financial transaction Web service in
`wireless communications with the J2EE enabled server. Each
`client executes a Java language software product to conduct a
`financial transaction between a merchant and a consumer
`
`upon an account issued by an issuer to the consumerin col-
`laboration with the financial transaction Web service. The
`
`financial transaction is conductedat least in part in a wireless
`communication with the client and the J2EE enabled server.
`
`Eachfinancial transaction is submitted by the merchantto an
`acquirer for processing bya transaction handler/paymentpro-
`cessor, and is submitted by the transaction handler/payment
`processor to the issuer to obtain a payment amount for the
`financial transaction from the account, and wherein the issuer
`forwards the payment amountofthe financial transaction to
`the transaction handler/payment processor who forwards the
`payment amountofthe financial transaction to the acquirerto
`pay the merchantfor the financial transaction.
`[0008]
`In another implementation, the Web enabledclients
`are Java 2 Standard Edition (J2SE) enabledthick clients that
`can be a workstation, a personal computer, or a laptop com-
`puter. Each thick client executes an operating system (OS) to
`perform OSspecific commandsandthe Java software product
`to conduct the financial transaction is byte code converted by
`a Java Virtual Machine (JVM)into the OS specific commands
`performed bythe OS.
`[0009]
`In yet another implementation, the Web enabled
`clients are Java 2 Micro Edition (J2ME) enabledthin client.
`These thin clients can have a Connected Limited Device
`Configuration (CDLC) with a J2ME configuration and can
`execute an operating system (OS) to perform OS specific
`commands, where the Java software product to conduct the
`financial transaction is byte code converted by a compact Java
`Virtual Machine (KVM)into the OSspecific commandsper-
`formed by the OS.
`[0010]
`Inastill further implementation,a wireless financial
`transaction system includes a Java 2 Enterprise Edition
`(J2EE) enabled server executing a Java software product to
`providea financial transaction Web service smart cards. Each
`smart card has a digital signal processor executing an oper-
`ating system (OS) to perform OS specific commands and
`executing a Java software product to conducta financialtrans-
`action in byte code converted by a Card Virtual Machine
`(KVM)into the OS specific commandsperformedby the OS.
`The smart card is served the financial transaction Web service
`in wireless communications with the J2EE enabled server and
`executed a Java language software product to conducta finan-
`cial transaction in collaboration withthe financialtransaction
`Webservice. The financial transaction 1s conductedat least in
`part wireless communication with the smart card and is con-
`ducted with a merchant upon an account issued by an issuer to
`a consumer.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`Implementations will become more apparent from
`[0011]
`the detailed description set forth below when taken in con-
`junction with the drawings, in which like elements bear like
`reference numerals.
`
`FIG. 1 illustrates a functional block diagram of
`[0012]
`exemplary environment of varying scale from servers to
`smart cards that can operated in a architecture for a Java
`environment to conduct wireless cashless transactions;
`[0013]
`FIG. 2 illustrates an exemplary J2ME device stack
`for a mobile consumerelectronics device having wireless
`communications functionality that can be used by a consumer
`to conduct a cashless transaction in the environmentdepicted
`in FIG. 1;
`
`20
`
`20
`
`

`

`US 2008/0275779 Al
`
`Nov. 6, 2008
`
`FIG. 3 illustrates a functional block diagram of
`[0014]
`exemplary architecture for a wireless cashless transaction
`system enabled by Java 2 Platform, Micro Edition (J2ME);
`[0015]
`FIG. 4 illustrates an exemplary communication
`stack in compliance with J2ME and Bluetooth standard
`according to the Java Specification Request-82, the purpose
`of whichis to standardize a set ofApplication Program Inter-
`faces (APIs) to allow Java technology-enabled devices to
`integrate into a Bluetooth environment, where each API is
`independentof the stack and radio used;
`[0016] FIG.5 is an exemplary architecture of four layers by
`which smart cards, SIM cards, and smart clients can commu-
`nicate with a payment gateway operating in a paymentpro-
`cessing system for the environmentdepicted in FIG.1;
`[0017]
`FIG. 6is a block diagram illustrating an exemplary
`environment having process flow of a business model to
`enroll accounts respectively issued by an issuer on which
`wireless cashlesstransaction will be conducted by consumers
`with merchants in the environmentdepicted in FIG.1;
`[0018]
`FIG. 7 is a flow chart depicting an exemplary
`methodfor a person to make a payment in a cashless trans-
`action to a merchant using a wireless consumerelectronics
`device;
`FIG. 8 is a flow chart illustrating an exemplary pro-
`[0019]
`cess flow for a person-to-person money transfer services,
`where a mobile consumerelectronics device having wireless
`communications functionality is interactively used by which
`the transferor to move money from the transferor’s accountto
`the transferee’s account;
`[0020]
`FIG. 9 is a flow chart depicting an exemplary
`method for a person to make a purchase from a merchant
`through its Internet e-commerce Web service in a cashless
`transaction by interactive use of a wireless consumerelec-
`tronics device;
`[0021]
`FIG. 10 is a flow chart depicting an exemplary
`method for a consumer to manage an account issued by an
`issuer to the consumerby interactive use of a wireless con-
`sumerelectronics device;
`[0022]
`FIG. 11 is a flow chart depicting an exemplary
`method for a borrower to apply for a loan from a lender to
`make purchase on an accountissued by the lender, where the
`borrowerapplies for the loan from the lender by interactive
`use of a wireless consumerelectronics device;
`[0023]
`FIG. 12 is a flow chart depicting an exemplary
`method for a consumer to receive a real-time notification
`
`about a potential incidence of fraud incidentto a transaction
`conduct on an account issued by an issuer to the consumer,
`where the consumerrequests the notification by interactive
`use of a wireless consumerelectronics device to which the
`notification can be delivered;
`[0024]
`FIG. 13 is a flow chart illustrating an exemplary
`method for a consumerto arrange for automatic payments to
`be made to an accountissued to the consumerbyanissuer,
`where a mobile consumerelectronics device having wireless
`communications functionality is interactively used by the
`consumer to make the arrangement;
`[0025]
`FIG. 14 is a flow chart depicting an exemplary
`method for a consumer to receive a real-time notification
`about a potential incidence ofa theft of the consumer’s iden-
`tity, such as an attempt to open an accountin the nameof the
`consumer, where the consumer requests the notification by
`interactive use of a wireless consumerelectronics device to
`whichthe notification can be delivered;
`
`FIG. 15 is a flow chart illustrating an exemplary
`[0026]
`method for a consumerto pay a merchant to add moneyto an
`account issued to the consumerby an issuer, where the mer-
`chant can use a mobile consumerelectronics device having
`wireless communications functionality to add the consumer’s
`moneyto the consumer’s account;
`[0027]
`FIGS. 16-17 are flow charts depicting respective
`exemplary methods by which a consumer can have secure
`communications when conducting financially-related trans-
`actions within a payment processing system using of a wire-
`less consumerelectronics device; and
`[0028]
`FIG. 18 illustrates a block diagram of an exemplary
`paymentprocessing system within which a mobile consumer
`electronics device having wireless communicationsfunction-
`ality can be used by a consumerto conduct a cashless trans-
`action in the environmentdepicted in FIG. 1.
`
`DETAILED DESCRIPTION
`
`[0029] Cashless transactions conducted with one or more
`wireless devices are addressed in various exemplary imple-
`mentations described for a payment processing system. The
`cashless transactions, which are conducted within the pay-
`ment processing system, can be conducted on many con-
`sumer hand held communications device such as cellular
`telephones and Personal Digital Assistants in an environment
`that is disclosed as being architected for simplicity, security,
`userfriendliness, multi-functionality, interoperability, having
`multi-lingual capability, for cost effectiveness, and high per-
`formanceandreliability.
`[0030]
`In this architected environment, a consumer hand
`held communications device can be used to make person to
`person moneytransfers, proximity payments from a con-
`sumer to a merchant, make an on-line purchase, maintain
`accounts, set up and receive fraud, moneytransfer, and iden-
`tity theft notifications, set up automatic bill payments, take
`out a loan to make a purchase, receive automatic bill payment
`alerts, load moneyonto an account, as well as other functions.
`[0031] The cashless transactions that are conducted with
`one or more wireless devices, as described herein, are appli-
`cable for transactions with payment processing system.
`Within the payment processing system, a transaction handler
`processes a transaction characterized by a consumer and a
`merchant engaging in the transaction upon an account that
`has been issued to the consumerby an issuer. The accountwill
`preferably be a non-credit account such as a prepaid account,
`a debit account, a deposit account, a flexible spending
`account, a health savings account, or combinations thereof.
`The merchant may bea retailer, a wholesaler, a reseller, a
`manufacturer, or a distributor, for example. As used herein, if
`a merchant is engaged in making a purchasein a transaction
`from another merchant, then the purchasing merchantwill be
`deemed to be the consumerandthe selling merchant will be
`deemedto be the merchant for that transaction.
`
`[0032] Referring to FIG. 1, a flowchart depicts an exem-
`plary implementation of a hardware/Java enabled ultimate
`commerce (U-Commerce) environment 100 facilitated for
`mobile transactions in a payment processing system. U-Com-
`merce represents an environment which is enabled by
`changes introduced by numerous networks and network
`devices that can be connected through the Internet. U-Com-
`merceis further enabled by wireless technology which loosen
`restrictions on the location from which a communication task
`
`is accomplished.
`
`21
`
`21
`
`

`

`US 2008/0275779 Al
`
`Nov. 6, 2008
`
`Segment 102 of environment 100 is a exemplary
`[0033]
`server implementation in which a server executes Java 2
`Enterprise Edition using the Java language, where one such
`application is for a hot spot where a wireless fidelity access
`point is located or for an area where this is an open wireless
`network.
`
`Segment 104 of environment 100 is an exemplary
`[0034]
`segment for workstation, PC and laptop implementations.
`Section 104 devices can execute Java 2 Standard Edition
`
`graphical user interfaces and secured persistence capability
`for each mobile device having a corresponding and compat-
`ible implementations.
`[0041]
`FIG. 2 shows an exemplary Java 2 Micro Edition
`(J2ME)device stack for a mobile device. By way of example,
`and not by way of limitation, a mobile device might be a
`cellular telephone using the exemplary J2ME device stack
`200. At the bottom ofthe stack is a digital signal processor
`(DSP) 210. By way of example, DSP 210 might be a ARM
`chip, such as a 32-bit RISC, 256k ROM, 256k Flash, 64k
`RAM,etc. The next layer in the stack is a compact Java Virtual
`Machine (KVM) 208 In KVM 208,there are threads and no
`floats. For a device having the stack 200, preferably there will
`be a J2ME connected limited device configuration (CLDC)
`which have KVM and Java 2 Micro Edition core Application
`Program Interfaces (APIs), by way of example.
`[0042] The next layer in the stack is JZEME core API’s 206.
`In particular, layer 206 of stack 200 showsvarious APIs that
`can be usedto interface between applications being run on the
`device (e.g.; a cellular telephone) and the JVM running
`J2ME.
`
`using the Java language. One such application for segment
`104 is a Java virtual machine (JVM).
`[0035]
`Segment 106 of environment 100 is for implemen-
`tations of various mobile communicators including palm top
`computers, personal digital assistant with communication
`capabilities, network cards, cable orsatellite set-top boxes for
`network television, and audio visual telephonic equipment
`such as screen phones. These communicators can be Connec-
`tive Device Configuration (CDC) for implemented devices
`for a Java 2 Micro Edition (J2ME) configuration. In particu-
`lar, the CDC device in segment 106 will have more memory
`and more processing power than a J2ME Connected Limited
`Device Configuration (CDLC) device in segment 108. The
`CLDCserves the market consisting of personal, mobile, con-
`[0043] Layer 204 in stack 200 is for a mobile information
`nected information devices. This configuration includes some
`device profile. These include a user interface and hypertext
`new classes designed specifically to fit the needs of small-
`transfer protocol (HTTP) networking, for example.
`footprint devices. A CDLC device has a J2ME connected
`[0044] The highest level in stack 200 is layer 202 whichis
`limited device configuration. In particular, the CLDC device
`particular MIDlet applications. A MIDlet application can be
`serves the market ofmobile personal and connected informa-
`tion devices. Relative to the CDC device, the network condi-
`one of a suite of such applications. In particularly, a MIDletis
`tion connection thereofis ‘always-on’ witha minimum oftwo
`an application written for the mobile information device pro-
`megabytes of memory available for the job assistant.
`file (MIDP). MIDlet applications are subclasses of JAVAX.
`micro edition.MIDlet.MIDlet class that is defined by the
`[0036]
`Segment 106 of environment 100 uses Java 2 Micro
`MIDP. The MIDPis a specification for a J2MEprofile. It is
`Edition (J2ME)and the Java language. A like segment 104,
`layered on top of CLDC and adds APIs for application life
`segment 106 is for a Java Virtual Machine (JVM).
`cycle, user interface, networking, and persistent storage.
`[0037]
`Segment 108 of environment 100 is for various
`Example of applications in the MIDlet suite would be a pay-
`devices including Point Of Sale terminals (POS), pagers,
`ment application, an identity application, a loyalty applica-
`smart phones, cell phones, and related mobile devices. Here,
`tion for awarding loyalty of a consumer with a credit card
`segment 108 is for CLDCdevices, or JZ2ME connectedlimited
`towards a merchant accepting such credit cards, or for award-
`device configuration devices.
`In particular,
`the virtual
`ing a particular loyalty of a consumerfor using ofaparticular
`machine for segment 108 is the compact Java virtual machine
`brand of credit cards (e.g., American Express, Master, Visa,
`(KVM).
`Diners Club, etc.) Another application in the MIDlet suite
`Segment 110 of environment 100 is for smart cards
`[0038]
`would be a transit application which allows a user to use an
`using Java language withthe particular virtual machine being
`accountto be able to gain access to a transit facility such as a
`the card virtual machine (CVM).
`subway, a bus, train, lightrail, etc.
`[0039] As seen FIG. 1, memory needed for each of the
`[0045]
`FIG. 3 depicts an exemplary J2ME system which
`segments 102-10 is shown at the bottom of each segment.
`particularly depicts an exemplary architecture 300 for
`Segment 102-104 will have between approximately ten and
`U-Commerce. The architecture 300 has a back endtier 312, a
`one megabytes of memory runningat a 64 bit configuration,
`middle end tier 310, a web tier at 308, a firewall 306, and a
`whereas segment 108 operates in a memory size of 512kB
`client tier 302.
`through 32kB, where the bit size ranges from 32 bit to 16 bit.
`Lastly, segment 110 is about the 8 bit range.
`[0040] Environment 100 see in FIG.1, places an emphasis
`on Java version 2 Micro Edition (J2ME)for various merito-
`rious reasons. These include the ability to write code only
`once and yet be ableto run it on any mobile device. J2ME also
`provides end-to-end-N security using standard HTTPS pro-
`tocol. Moreover, there can be a dynamic delivery of applica-
`tions and services using J2ME. The foregoing provide an
`enhanceduser experience, scalability, and enhanced perfor-
`mance. Applications can be downloaded over-the-air to
`mobile devices, such as J2MEapplications. JZME supports
`wireless messaging services such as SMSandothers. In sum,
`J2MEasdepicted in the exemplary implementation of envi-
`ronment 100 provides secured network capability,
`rich
`
`[0046] Back end tier 312 includes a database for storing
`data used by other tiers within the U-Commercearchitecture
`300. The middle layer tier 310 includes a J2EE application
`server and an EJB container as well as an enterprise bean
`having the components of a session bean andan entity bean.
`As used herein, J2EE is to be understood as the Java 2 Plat-
`form, enterprise edition which is a version of Java for devel-
`oping and employing enterprise applications, such as main
`frame-scale computing typical of large enterprises. As used
`herein, EJP or enterprise Java beans is a componentarchitec-
`ture for the development and employmentof object-oriented,
`distributed, enterprise-level applications. Applications writ-
`ten using the enterprise Java beans are scaleable, transac-
`tional and multi-user secure. The enterprise bean is a compo-
`
`22
`
`22
`
`

`

`US 2008/0275779 Al
`
`Nov. 6, 2008
`
`nent that implements a business task or business entity andis
`of two types: an entity bean or a session bean as mentioned
`above.
`
`[0047] Web tier 308 includes a web server (e.g.; serving
`HTMLimages) and a servlet engine (e.g., JSP servlets pre-
`sentation beans). As used herein, JSP is to be understood as
`Java server pages which are normal HTML with Java code
`pieces embedded in them. A servlet is a Java program that
`runs on a web server where the service side Java program
`provides additional features to the server. Common examples
`of Java servlets are small programs written in the Java lan-
`guage which are added to a web server.
`[0048] Web tier 308 communicates throughfirewall 306 to
`the internet using XML extendable mark up language or JSP
`HTML. The internet is exposed in architecture 300 at client
`tier 302 which includes communications using the HTTPS
`protocol with various client communicators 304. Examples of
`client communicators 304 include th