(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2008/0275779 A1
`Lakshminarayanan
`(43) Pub. Date:
`NOV. 6, 2008
`
`US 20080275779Al
`
`(54) MOBILE PAYMENT SERVICES
`
`Publication Classi?cation
`
`(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 US. Application Data
`
`(60)
`
`Provisional application No. 60/889,443, ?led on Feb.
`12, 2007.
`
`(51) Int. Cl.
`(2006.01)
`G06Q 20/00
`(2006.01)
`G06Q 30/00
`(52) us. c1. ........................................... .. 705/14; 705/39
`(57)
`ABSTRACT
`A Java2 Enterprise Edition (J2EE) enabled server executing
`Java software provides a ?nancial transaction Web service to
`a client each of which communicates wirelessly with the
`J2EE enabled server and executes Java software to conduct
`?nancial transactions between a merchant and a consumer
`upon an account issued by an issuer to the consumer. Each
`?nancial transaction is submitted by the merchant to an
`acquirer for processing by a transaction handler/payment pro
`cessor, and is submitted by the transaction handler/payment
`processor to the issuer to obtain a payment amount for the
`?nancial transaction from the account, and wherein the issuer
`forwards the payment amount of the ?nancial transaction to
`the transaction handler/payment processor who forwards the
`payment amount of the ?nancial transaction to the acquirer to
`pay the merchant for the ?nancial transaction.
`
`Enrollment Business Model
`
`,* 606
`
`600
`x
`
`608
`
`OBTAIN CODE SIGNING CERTIFICATE
`FRoNI CERTIFICATE AUTHORITY
`
`Transaction
`Handler/
`Payment
`Processor
`
`Payment
`Gateway
`
`ENRoLLIIIIENT USING
`BULK CONSUMER
`FILE UPLOAD
`4P Issuer
`
`604
`
`\
`\ \
`\
`W \
`BULK MERCHANT
`\
`FILE UPLOAD
`\
`
`\
`\
`
`T
`
`i 610
`
`-
`Acquirer
`
`4
`
`Initiate
`Enrollment
`Request
`
`Merchant
`
`v‘; 612
`
`616 i.‘
`
`\ \
`/
`
`Initiate
`Enrollment
`
`,4.
`
`r
`
`Request
`
`\
`
`Over the Air:
`Downloads;
`,
`Upgrades;
`Signed/T rusted \
`Smart Client
`[.1
`
`e
`
`/ / \
`/ /
`\
`/
`
`\ \
`\L Consumer
`
`\
`\
`
`‘i 602
`
`_ _ _ — — _ ‘I
`
`I
`
`|
`|
`|
`
`|
`Consumer
`Wireless Client With |
`Smart Client
`Preinstalled
`By Manufacturer
`
`I
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 1 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 1 0f 18
`
`US 2008/0275779 A1
`
`102
`
`/
`//
`
`104
`
`I
`/
`
`/
`//
`
`106
`
`108
`
`I
`/
`/
`
`110
`
`/
`//
`
`Server
`
`Workstation
`
`PC, Laptop
`
`Commun
`ications:
`Palmtop
`Computer,
`Personal
`Digita|
`Assistant
`
`Point of
`Sale
`Terminal
`
`Network
`Card
`
`Pa er
`9
`
`Settop Box
`Network TV
`
`Smart
`Phone;
`Cell
`Phone
`
`Screen
`Phone
`
`Smart
`Card
`
`'_ _ _ T
`I
`CDC I
`
`— _ _ 7
`CLDC I
`
`I
`
`Java 2
`Enterprise
`Edition
`
`I
`|
`|
`
`Java 2
`Standard
`Edition
`
`‘52::
`.
`.
`Ed'tm"
`(J2ME)
`
`____ __l
`
`_ _ _
`
`T ‘‘‘‘ i‘ F
`Hot Spot
`I
`I
`
`Java Language
`
`Java
`Virtual Machine
`(JVM)
`
`EITWFTJ 6r? —
`n‘llgctllllizl‘lle
`xllgtciailne
`(KVM)
`(CVM)
`
`Memory:
`
`10 MB 6 ----------------- “91 Mb 512kB€ +32kB
`
`64 bit
`
`32 bit
`
`16 bit
`
`8 bit
`
`1001
`
`Figure 1
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 2 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 2 0f 18
`
`US 2008/0275779 A1
`
`[- 200
`
`MlDlet Suite: Applications written in the Mobile lnforrnation
`Device Pro?le (MlDP) speci?cation for a JZME pro?le:
`
`/f 202
`
`/
`
`Applications: Payment; Identity; Loyalty; Transit
`
`M P: User Interface, HTTP networking, etc.
`
`J2ME Core APls
`
`/f 206
`
`Comgact Java Virtual Machine (KVM):
`Threads, no Floats...
`
`/f 208
`
`Di ital Si nal Processor (e.g., ARM, etc.)
`
`Figure 2
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 3 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 3 0f 18
`
`US 2008/0275779 A1
`
`? 304
`
`fsoo
`
`glignt Tigr
`(/X
`\' L HTTP
`/l
`/ Intern et <\
`\\
`1
`)V/
`\v ’
`
`* XML OR JSP HTML
`
`/
`
`Client Communicators:
`Palmtop Computer, PDA;
`5 PC (HTML Browser),
`Laptop;
`Smart Phone;
`Cell Phone (J2ME GUI (Midlets with
`XML Parser)
`
`4’
`wgp Tigr
`
`Fire Wall
`
`Web
`Server
`(HTML Images)
`
`Servlet Engine
`(JSP Servlets Presentation Beans)
`
`302
`
`//
`
`/~ 306
`/
`
`308
`
`w J2EE Application Server/
`EJB Container
`
`/i 310
`/
`
`Session Bean & Entity Bean
`
`Back End Tier
`
`/
`/
`
`\
`\\
`
`A
`/
`Database (
`>
`\
`\\//
`
`/i 312
`/
`/
`
`Figure 3
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 4 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 4 0f 18
`
`US 2008/0275779 A1
`
`JSR-82 speclflcatlon
`
`Applications
`
`Javax.b|uetooth
`
`.
`KVM Extenslons
`
`MIDP
`
`CLDC
`
`KVM
`
`Bluetooth
`Protocol
`Stack
`
`Bluetooth
`Radio
`
`/f 402
`//
`
`/? 404
`/
`
`/? 406
`/
`/
`
`/f 408
`/
`
`Figure 4
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 5 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 5 0f 18
`
`US 2008/0275779 A1
`
`f 500
`
`/f 502
`
`504
`
`505
`
`508
`
`/~ 510
`
`/i 512
`
`/
`
`///
`
`514
`
`Layer lV:
`Transaction Handler/ Payment Processor Gateway:
`Performs Authorization and Credit Request From Gateway
`
`ISO 8583 Financial Message
`
`I
`
`La er lll:
`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 & Basel
`- Offers Administrative operations for Member Bank
`
`XML HTTPS
`
`I
`
`Layer ll:
`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 l: Secure Element Layer (Smart Card or SIM Card):
`- Tamper-resistant
`- Connected temporarily or permanently
`- Contains user credentials
`- Performs cryptography function
`
`Figure 5
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 6 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 6 0f 18
`
`US 2008/0275779 A1
`
`W L606
`
`600
`_\
`
`/ 608
`/
`Payment
`Gateway
`
`OBTAIN CODE SIGNING CERTIFICATE
`FRoM ERTIFICATE AuTHoRITY
`\
`
`4
`
`I
`
`/
`/
`
`’
`Transaction
`Handler/
`Payment
`Processor
`
`f 604
`/
`/
`
`ENROLLMENT USING
`\
`BULK CONSUMER
`\
`FILE UPLOAD
`\ \
`\ % Issuer
`\
`\
`\
`\
`\
`
`ENROLLMENT USING
`BULK MERCHANT
`FILE PLOAD
`
`610
`
`"
`//
`/
`
`-
`
`Acqulrer
`
`T
`Initiate
`Enrollment
`Request
`4
`
`Merchant
`
`\\
`\; 612
`
`616 i\ \ \
`\
`//H
`/ \V/ \j/
`/ Over the Air:
`
`\
`
`Enrlctlilirlrtiznt
`Req uest
`
`
`
` K //) I
`
`
`
`
`
`
`
`Downloads; Upgrades; Signed/T rusted \
`
`/L//
`\
`Smart Client
`\ "\V//*T/* \ \
`/ / \
`\‘ Consumer
`/ /
`\
`/
`\
`\
`\
`
`\
`
`\\
`\; 602
`
`/ /
`
`— — — — — — ‘I
`
`I
`
`|
`|
`|
`
`|
`Consumer
`Wireless Client With I
`Smart Client
`I
`Preinstalled
`By Manufacturer
`
`I_ _ _ _ _ _ _ l
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 7 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 7 0f 18
`
`US 2008/0275779 A1
`
`Proximity Payment
`Transaction Flow
`
`f 70°
`
`//
`
`/
`
`.
`
`Acquirer
`
`4
`
`/f 708
`//
`
`/
`
`/
`
`/
`
`Transaction
`Handler/
`
`> Payment
`Processor
`A
`
`Payment
`Gateway
`
`Figure 7
`
`/ // /H\J
`
`K
`
`// ( \W
`
`Internet
`
`\\
`
`)
`
`\V‘V/Q/K
`\e 716
`
`Issuer
`\\
`
`\; 704
`
`Wireless Internet
`Ea
`
`FINANCIAL APPLICATION
`USING NFC 0R
`BLUETOOTH OR
`OBEX OVER IRDA OR
`V
`Consumer
`SMS 0R
`Merchant:
`POS or 4* NFC + BLUETOOTH 4> Wireless Client
`Wireless Client
`0R RFID:
`\\
`CUSTOMER INVOICE /
`\*
`CONSUMER
`712
`CREDIT CARD
`EXCAHNGE
`
`\
`\;
`702
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 8 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 8 0f 18
`
`US 2008/0275779 A1
`
`P2P Payment: Send and Noti?
`Sender’s
`800
`\
`Consumer
`f
`/ Wireless Client \
`
`/
`
`822
`
`1
`
`\
`
`802a
`
`Receiver Betaiis
`
`First Name : John
`
`Last Name : Mike
`
`City : Austin
`
`Amount : $20G Send
`
`The Amount $29G hae
`been sent to John
`successfully
`
`5
`
`Figure 8
`
`3
`+
`
`Payment
`Gateway
`
`Authorization
`
`Creit
`
`Transaction
`
`Notifioation
`First Name : John
`
`/f 826
`
`Transaction Handler/
`Payment PFOCGSSOF
`
`Last Name : Mike
`
`I
`
`MONK-215123603181
`Notify
`
`\ \
`
`\
`
`806
`
`Credit
`Transaction
`
`6_
`Push: SMS Msg
`Smart Client
`Auto-Launch
`802b *
`\\
`\
`r’
`R '
`ecelve s
`Consumer
`Wireless Client
`
`’
`
`Authorization
`;
`
`“You got
`Moneyl“
`
`Issuer:
`Sender
`
`Issuer:
`Receiver
`
`\\
`\
`\% 804a
`
`\\
`\
`lg 8O4b
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 9 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 9 0f 18
`
`US 2008/0275779 A1
`
`Mobile Payment r900 Figure9
`
`Enter Your if)
`5
`7'8900
`
`Get Cnaiienge
`
`Your Chaiienge
`‘3296.78
`
`Enter Response
`
`Pick or skip Address
`from Address Book
`
`Enter Chaiienge
`129578
`
`Enter PIN
`@
`
`Your Response
`Verify Merchant
`W 06%093
`
`$360
`
`f 930
`
`Your (Ihaiienga
`1296.78
`Enier Response
`seems
`
`Your Shipping Address
`
`H311 W Rarmer Ln,
`#833, Austin,
`TX,?'$729
`
`Submit
`
`6
`*
`
`Payment
`Gateway
`
`Transaction Handler/
`Payment Processor
`
`i authorize
`this oniine
`“arises/no:
`
`Consumer
`Wireless Client
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 10 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 10 0f 18
`
`US 2008/0275779 A1
`
`Virtual Account Management
`
`[- 1000
`
`/f 1022
`
`Yuur Virtuai Acsnunt
`
`Acceuni:
`
`12345675500 234
`
`Pin: i 234
`Waiiet iDN‘JeiisFargo’i23
`
`Max
`
`Max Transactions
`C
`Max Amaunt
`
`\
`\
`
`Consumer
`Wireless Client
`
`Seiect Want-st m
`
`
`
`Weiis Fargo‘i BQFAQ
`
`Ghasei
`
`Submit
`
`1006 ?\ Transaction
`//
`Handler!
`Payment
`Processor
`
`Figure 10
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 11 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 11 0f 18
`
`US 2008/0275779 A1
`
`Mobile Loan Transaction
`
`1102e\
`\
`Consumer
`Wireless Client
`
`|
`1
`
`[-1100
`
`Get a eieetronic PO23
`{Check fer $3990 From
`issuer
`
`2
`
`3
`
`/f 1104
`//
`
`Issuer‘
`E-check
`
`I
`
`4:
`Web Se.rV'C.e
`Communication
`
`I
`
`Payment
`Gateway
`
`\;1108
`
`T
`
`5:
`Real-time
`Credit Check
`+
`
`Credit
`Agency
`
`-
`
`/~1106
`
`Trijmsglctlen /
`an er
`/
`Payment
`
`Processor
`
`\;1118
`
`Figure 11
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 12 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 12 0f 18
`
`US 2008/0275779 A1
`
`Mobile Fraud Notification
`
`\
`
`Consumer
`Wireless Client
`
`f- 1200
`
`Seiect Waiiet iD
`
`Weiis
`BOFAZ
`A
`4
`
`2
`
`Fraud Aiert Max
`3; Am?unt
`
`/f 1224
`/
`
`Account Activities:
`Authorization;
`Clearing and
`Settlement;
`Other
`
`.
`
`4:
`CMLS/CDI
`Infrastructure
`
`I
`
`3
`
`Payment
`Gateway:
`Real-Time
`Anti-Fraud
`Detection
`System
`
`Consumer
`Wireless Client
`
`\
`\
`
`5:
`Real-time
`Fraud
`A|ert
`
`\
`\
`i g 1208
`Transaction Handler/
`Payment Processor
`\
`\
`g 1206
`
`\% 1202b Figure 12
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 13 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 13 0f 18
`
`US 2008/0275779 A1
`
`Mobile Auto Bill Pay
`
`f 1 300
`
`1302 *\
`\
`
`Consumer
`Wireless Client
`
`1
`
`Generate Permanent
`(Never Expira) Anti)
`$3}: Accauni Numbar
`mr Aum 815% my
`
`Next
`
`Ynur Ants Fay Acmunt
`
`Account:
`
`123456?89D123¢156
`
`Wailei lDzWeEisFarga123
`
`33133131331231 an
`Waiis Fargo123
`
`BQFAQ
`
`Chél‘ie’i
`
`4
`
`4
`
`/f 1326
`
`/
`/
`
`_
`e-Bill Pay
`Zayment <— 5' —> Merchant
`ateway
`SOAP/
`—. .
`HTTPS
`www.Ver|zonW|re|ess.com
`
`\\
`\% 1308
`
`Transaction Handler/
`Payment Processor
`/
`/
`1306 Q/
`
`Figure 13
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 14 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 14 0f 18
`
`US 2008/0275779 A1
`
`Mobile ld_ent?y Thej Ale_rt
`
`1406
`
`[- 1400
`
`Transaction Handler/
`Payment Processor
`
`1404
`
`/
`//
`
`1408 e\
`\\
`
`11
`HTTPS
`Issuer — Load New —>
`Account In
`Consumer’s
`Name
`
`Payment
`Gateway
`
`1420
`
`\
`
`\
`\
`
`3
`
`_
`
`Attempt _to Issue.
`new credit or debit
`card in consumer’s
`
`name
`
`T
`
`2:
`
`Validate and Load
`New Account File
`
`‘
`
`/
`/
`
`/ \
`/
`Database (
`)
`
`\
`\_\V/
`
`Gateway Sends
`SMS Message to
`auto-launch
`smart client to
`render alert
`
`Consumer
`Wireless Client
`
`Figure 14
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 15 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 15 0f 18
`
`US 2008/0275779 A1
`
`Consumer Account Loading
`At Mobile Merchant — r1500
`
`/* 1530
`//
`l
`‘I:
`/?
`\j/ At — Cash/check
`DAG
`Payment
`Consumer
`
`Wireless
`> Mighsant
`
`\
`
`T
`2:
`Send: Account
`and Amount
`
`L
`
`/f 1508
`
`/
`/
`
`Payment
`Gateway
`
`i 3:
`
`Transaction:
`Amount Credited
`To Account
`
`i
`
`Transaction
`Handler/
`Payment
`Processor
`
`/f 1506
`
`4:
`Transaction:
`Amount Credited
`To Account
`
`Figure 15
`
`i
`
`/
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 16 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 16 0f 18
`
`US 2008/0275779 A1
`
`Mobile Activation and Security
`
`/? 1630
`/
`,L/
`U
`-
`ZVPQ — Entet
`/
`Credentials
`Md
`and
`Consumer
`PIN
`
`1
`
`1600
`f
`
`Consumer
`Wireless Client
`
`\
`\?
`1602a
`
`2:
`Send: Credentials
`and PIN
`
`/* 1606
`
`? 1608
`/
`
`Payment Gateway:
`/
`-
`,
`Transaction Handler/
`Payment Processor <—> Validate and Hash
`credentials/other data
`
`3:
`Return:
`- Hash Msg Digest,
`- e-Wallet Details,
`- Dynamic key pair
`
`Consumer
`Client/Smart Card/
`SIM CARD
`
`\
`Q 1602b
`
`f 1604
`/
`/
`
`Issuer
`
`I
`
`I
`
`1 6
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 17 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 17 0f 18
`
`US 2008/0275779 A1
`
`Mobile Client Authentication
`
`f 1700
`
`f 1730
`
`//
`?g
`Q? E
`L/ \1
`Consumer
`
`'
`
`A
`
`I
`
`-
`
`Wireless Client:
`
`Consumer
`1-
`Entgnil/ahd —P Execute
`(Max 3
`Transaction \L
`Attempts)
`Application
`
`'
`
`'
`
`1702
`
`2:
`Send At End of
`Transaction:
`- Dynamic Key;
`- Static Msg Digest
`
`/f 1708
`
`/
`/
`//
`/
`
`Transaction Handler/
`Payment Processor
`
`Payment Gateway:
`<—> Validate and Hash
`credentials/other data
`
`Figure 17
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 18 of 32
`
`

`

`Patent Application Publication
`
`Nov. 6, 2008 Sheet 18 0f 18
`
`US 2008/0275779 A1
`
`[-1800
`
`Figure 18
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 19 of 32
`
`

`

`US 2008/0275779 A1
`
`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 bene?t of, US. Provisional
`Application Ser. No. 60/ 889,443, ?led Feb. 12, 2007, entitled
`“MOBILE SERVICES,” the entire contents of Which is
`hereby incorporated by reference.
`
`FIELD
`
`[0002] Implementations generally relate to ?nancial trans
`actions, and is more particularly related to ?nancial transac
`tions conducted With a mobile consumer electronics device.
`
`BACKGROUND
`
`[0003] Consumer transactions With merchants are increas
`ingly being made payable With other than cash or checks.
`More recently, the device being used by consumers to conduct
`such consumer transactions is a mobile consumer electronics
`device having Wireless communications functionality, such
`as a cellular telephone or a Personal Digital Assistant (PDA).
`Such mobile consumer electronics 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, has its limitations. WAP requires key improvements
`in security, and also requires constant air time for o?lline
`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 protocol is 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
`HTML language. One problem With the I-mode protocol is
`that there is no client side scripting language like the Wireless
`Markup Language (WML), Where WML is a language that
`alloWs the text portions of Web pages to be presented on
`cellular telephones and personal digital assistants (PDAs) via
`Wireless access. Also, the I-Mode protocol is not available in
`all geographic regions.
`[0006] Consequently, there is a need in the art to provide a
`mobile consumer electronics device having Wireless commu
`nications functionality by Which a consumer can conduct a
`cashless transaction on an account issued to the consumer by
`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 ?nancial transactions and multiple related
`services.
`
`SUMMARY
`
`[0007] In one implementation, a Wireless ?nancial transac
`tion system includes a Java 2 Enterprise Edition (J2EE)
`enabled server executing a Java softWare product to provide a
`?nancial transaction Web service to Web enabled clients.
`Each client is served the ?nancial transaction Web service in
`Wireless communications With the J2EE enabled server. Each
`client executes a Java language softWare product to conduct a
`?nancial transaction betWeen a merchant and a consumer
`
`upon an account issued by an issuer to the consumer in col
`laboration With the ?nancial transaction Web service. The
`?nancial transaction is conducted at least in part in a Wireless
`communication With the client and the J2EE enabled server.
`Each ?nancial transaction is submitted by the merchant to an
`acquirer for processing by a transaction handler/payment pro
`cessor, and is submitted by the transaction handler/payment
`processor to the issuer to obtain a payment amount for the
`?nancial transaction from the account, and Wherein the issuer
`forWards the payment amount of the ?nancial transaction to
`the transaction handler/payment processor Who forWards the
`payment amount of the ?nancial transaction to the acquirer to
`pay the merchant for the ?nancial transaction.
`[0008] In another implementation, the Web enabled clients
`are Java 2 Standard Edition (J2SE) enabled thick clients that
`can be a Workstation, a personal computer, or a laptop com
`puter. Each thick client executes an operating system (OS) to
`perform OS speci?c commands and the Java softWare product
`to conduct the ?nancial transaction is byte code converted by
`a Java Virtual Machine (JV M) into the OS speci?c commands
`performed by the OS.
`[0009] In yet another implementation, the Web enabled
`clients are Java 2 Micro Edition (J2ME) enabled thin client.
`These thin clients can have a Connected Limited Device
`Con?guration (CDLC) With a J2ME con?guration and can
`execute an operating system (OS) to perform OS speci?c
`commands, Where the Java softWare product to conduct the
`?nancial transaction is byte code converted by a compact Java
`Virtual Machine (KVM) into the OS speci?c commands per
`formed by the OS.
`[0010] In a still further implementation, a Wireless ?nancial
`transaction system includes a Java 2 Enterprise Edition
`(J2EE) enabled server executing a Java softWare product to
`provide a ?nancial transaction Web service smart cards. Each
`smart card has a digital signal processor executing an oper
`ating system (OS) to perform OS speci?c commands and
`executing a Java softWare product to conduct a ?nancial trans
`action in byte code converted by a Card Virtual Machine
`(KVM) into the OS speci?c commands performed by the OS.
`The smart card is served the ?nancial transaction Web service
`in Wireless communications With the J 2EE enabled server and
`executed a Java language softWare product to conduct a ?nan
`cial transaction in collaboration With the ?nancial transaction
`Web service. The ?nancial transaction is conducted at 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
`
`[0011] Implementations Will become more apparent from
`the detailed description set forth beloW When taken in con
`junction With the draWings, in Which like elements bear like
`reference numerals.
`[0012] FIG. 1 illustrates a functional block diagram of
`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 consumer electronics device having Wireless
`communications functionality that can be used by a consumer
`to conduct a cashless transaction in the environment depicted
`in FIG. 1;
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 20 of 32
`
`

`

`US 2008/0275779 A1
`
`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 which is 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
`independent of 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 payment pro-
`cessing system for the environment depicted in FIG. 1;
`[0017]
`FIG. 6 is 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 cashless transaction will be conducted by consumers
`with merchants in the environment depicted in FIG. 1;
`[0018]
`FIG. 7 is a flow chart depicting an exemplary
`method for a person to make a payment in a cashless trans-
`action to a merchant using a wireless consumer electronics
`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 consumer electronics device having wireless
`communications functionality is interactively used by which
`the transferor to move money from the transferor’s account to
`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 consumer elec-
`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 consumer by interactive use of a wireless con-
`sumer electronics 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 account issued by the lender, where the
`borrower applies for the loan from the lender by interactive
`use of a wireless consumer electronics 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 incident to a transaction
`conduct on an account issued by an issuer to the consumer,
`where the consumer requests the notification by interactive
`use of a wireless consumer electronics device to which the
`notification can be delivered;
`[0024]
`FIG. 13 is a flow chart illustrating an exemplary
`method for a consumer to arrange for automatic payments to
`be made to an account issued to the consumer by an issuer,
`where a mobile consumer electronics 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 of a theft of the consumer’s iden-
`tity, such as an attempt to open an account in the name of the
`consumer, where the consumer requests the notification by
`interactive use of a wireless consumer electronics device to
`which the notification can be delivered;
`
`FIG. 15 is a flow chart illustrating an exemplary
`[0026]
`method for a consumer to pay a merchant to add money to an
`account issued to the consumer by an issuer, where the mer-
`chant can use a mobile consumer electronics device having
`wireless communications functionality to add the consumer’s
`money to 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 consumer electronics device; and
`[0028]
`FIG. 18 illustrates a block diagram of an exemplary
`payment processing system within which a mobile consumer
`electronics device having wireless communications function-
`ality can be used by a consumer to conduct a cashless trans-
`action in the environment depicted 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,
`user friendliness, multi-functionality, interoperability, having
`multi-lingual capability, for cost effectiveness, and high per-
`formance and reliability.
`[0030]
`In this architected environment, a consumer hand
`held communications device can be used to make person to
`person money transfers, proximity payments from a con-
`sumer to a merchant, make an on-line purchase, maintain
`accounts, set up and receive fraud, money transfer, and iden-
`tity theft notifications, set up automatic bill payments, take
`out a loan to make a purchase, receive automatic bill payment
`alerts, load money on to 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 consumer by an issuer. The account will
`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 be a retailer, a wholesaler, a reseller, a
`manufacturer, or a distributor, for example. As used herein, if
`a merchant is engaged in making a purchase in a transaction
`from another merchant, then the purchasing merchant will be
`deemed to be the consumer and the selling merchant will be
`deemed to 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-
`merce is further enabled by wireless technology which loosen
`restrictions on the location from which a communication task
`
`is accomplished.
`
`SAP 1004
`
`IPR of US. Patent No.
`
`8,346,894
`Page 21 of 32
`
`SAP 1004
`IPR of U.S. Patent No. 8,346,894
`Page 21 of 32
`
`

`

`US 2008/0275779 A1
`
`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
`
`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 or satellite 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
`CLDC serves the market consisting of personal, mobile, con-
`nected information devices. This configuration includes some
`new classes designed specifically to fit the needs of small-
`footprint devices. A CDLC device has a J2ME connected
`limited device configuration. In particular, the CLDC device
`serves the market ofmobile personal and connected informa-
`tion devices. Relative to the CDC device, the network condi-
`tion connection thereof is ‘always-on’ with a minimum oftwo
`megabytes of memory available for the job assistant.
`[0036]
`Segment 106 of environment 100 uses Java 2 Micro
`Edition (J2ME) and the Java language. A like segment 104,
`segment 106 is for a Java Virtual Machine (JVM).
`[0037]
`Segment 108 of environment 100 is for various
`devices including Point Of Sale terminals (POS), pagers,
`smart phones, cell phones, and related mobile devices. Here,
`segment 108 is for CLDC devices, or J2ME connected limited
`device configuration devices.
`In particular,
`the virtual
`machine for segment 108 is the compact Java virtual machine
`(KVM).
`Segment 110 of environment 100 is for smart cards
`[0038]
`using Java language with the particular virtual machine being
`the card virtual machine (CVM).
`[0039] As seen FIG. 1, memory needed for each of the
`segments 102-10 is shown at the bottom of each segment.
`Segment 102-104 will have between approximately ten and
`one megabytes of memory running at a 64 bit configuration,
`whereas segment 108 operates in a memory size of 512kB
`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 able to 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
`enhanced user experience, scalability, and enhanced perfor-
`mance. Applications can be downloaded over-the-air to
`mobile devices, such as J2ME applications. J2ME supports
`wireless messaging services such as SMS and others. In sum,
`J2ME as depicted in the exemplary implementation of envi-
`ronment 100 provides secured network capability,
`rich
`
`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 of the 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 JavaVirtual
`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 J2ME core API’s 206.
`In particular, layer 206 of stack 200 shows various APIs that
`can be used to interface between applications being run on the
`device (e.g., a cellular telephone) and the JVM running
`J2ME.
`
`[0043] Layer 204 in stack 200 is for a mobile information
`device profile. These include a user interface and hypertext
`transfer protocol (HTTP) networking, for example.
`[0044]