0000
`
`
`
`209 05A1
`
`United States
`(19)
`(2) Patent Application Publication (0) Pub. No.: US 2015/0220905 Al
`
`(43) Pub. Date: Aug. 6, 2015
`DESSERT
`
`(54)
`
`(71)
`
`(64)
`
`(G0)
`
`(51)
`
`SYSTEM AND METHOD FOR MANAGING
`PAYMENT IN TRANSACTIONS WITH A PCD
`
`Applicant: QUALCOMM INCORPORATED.San
`Diego, CA (US)
`
`Inventor: Robert L. DESSERT. San Diego, CA
`(US)
`
`Appl. No.: 14/688,682
`
`Filed:
`
`Apr. 16, 2015
`
`Related U.S. Application Data
`
`Continuation of application Na, 13/481.766. filed on
`May 25, 2012.
`
`Provisional application No. 61/611,344,filed on Mar,
`15, 2012,
`
`Publication Classification
`
`Int. Cl.
`G06 20/32
`G060 20/40
`G060 20/36
`
`(2006,01)
`(2006.01)
`(2006.01)
`
`(52) US.Ch
`CPC csecarseevers G06O 20/322 (2013.01): G06G 20/36
`(2013.01); Gd6O 20/40 (2013.01)
`
`(57)
`
`ABSTRACT
`
`Asystem and method for managing payment ina transaction
`using a portable computing device (“PCI”) includes a mobile
`wallet token being received from an accountissuing, entity.
`Next. the mobile wallet token is stored in memory within a
`PCD payment platform (i.e.. a cloud payment solution). A
`PCD token that corresponds with the mobile wallet token is
`generated by the PCD payment platlorm. The PCD token is
`transmitted over a communications network to a PCD. The
`mobile wallet token corresponds to at least one of a credit
`card account, an alternative or non-traditional payment
`account, a stored value account, an account from a financial
`institution, and a merchant based card account. A mobile
`wallet token may be generated in response to receiving inpul
`from an on-line portal that future use of a payment account
`with a PCDis desired or in responseto input receivedfroma
`point-of-sale terminal.
`
`66
`
`66
`
`|
`MOBILE WALLET TOKEN—
`
`14
`
`eo —-—- --MOBILE WALLET TOKEN —— — — — — — — — —
`et prt MOBILEWALLET TRESS me er me me me 4
`
`NS
`eo
`|
`20a
`|_ 208
`Credil Cardis)
`Bank Card(s)
`rT aMOBILEWALLETTOKEN- —:|
`
`Mobile Wallet Token
`Receiver-Storage/
`PCD Payment
`PCDloken
`generator
`Platform
`(cloud)
`
`10
`
`av
`1]
`
`Merchant Acquirer
`
`1
`if VAULT
`
`13.
`
`28
`
`Fl Card Issuer
`Account Web-MGT
`Portal
`
`30
`Bank Card Issuer
`Account Web-MGT
`Portal
`
`32
`Alternative Payment
`Account Web-MGT
`Portal
`
`i42
`
`
`
`Communications
`Network
`
`— =| Merchant Enterprise
`System
`12
`i
`Merchant POS
`System(s)
`27
`
`
`
`Receipt
`
`103
`
`872
`
`103A
`
`100
`Computing Device
`11
`S
`Payment Application
`VW
`
`PCD Tokenstorage Portable/Mobile
`
`44
`Good(s)/Service(s)
`
`Check-Out System
`124
`
`TAG
`
`Samsung, Exh. 1045, p. 1
`Samsung, Exh. 1045,p. 1
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet I of 21
`
`US 2015/0220905 Al
`
`g0¢VOiLor-™raeL—_————,NAvYOLIATIVM
`
`aaOW—29M=eNa¥OLLSTI¥Ms1GOn-——————a:
`
`
`
`
` JUeyQeyy|||teheeee4[YexOLSIEMe190¥Oljj42—-NSNOLLATFeOXe:|
`
`
`(s)pegyueg(s)pegWap99
`
`
`
`jabesojs-janjaoay
`
`
`—NSNOLLATIWMATION>
`
`
`
`jUauWiAeYaAleLal|\y
`
`(s)wajshg
`
`99
`
`|||Jauinboy
`asudiajuyjueyquayy|_—_
`
`
`LINWAos
`|||(pnoja)|WOE
`juawdedOd
`
`€L
`
`9k
`
`orl
`
`W840)G9Od
`
`Joyesaueb
`
`FL
`
`AVMALVS
`
`cbi
`
`Zél
`
`(s)wejsis
`
`SOdWueynay
`
`SUONEd/UNLUWOD
`
`YJOMION
`
`Janss|Ped|4
`
`
`
`LOW-GaMIUNoDoy
`
`jEWOd
`
`
`
`(s)eo1as/(s)pooyVEO
`
`L‘SisOT
`
`SIGOW/a|QeWOd
`
`cOL
`
`
`
`aoiaagBuyndwoy
`
`val
`
`
`
`WwayshgiNO-WEYDehh
`
`OVL
`
`
`
`uoleoddyjuawAeY
`
`e238
`
`
`
`aBeioysuayoygod
`
`
`
`
`
`Janss|puesyueg
`
`
`
`LOW-93/\Junosay7
`
`BUOY
`
`
`
`qualuAedaAljeUley}y
`
`
`
`LOW-G9MjUNnDooYy
`
`|EWOd
`
`Samsung, Exh. 1045, p. 2
`Samsung, Exh. 1045,p. 2
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 2 of 21
`
`US 2015/0220905 Al
`
`
`
`aanUNDOHBS
`
`aaapoBNOKeI
`
`90¢
`
`SUOMIOUCD99SUD)
`
`SUIOHIDUOO19SwusD}
`
`Je
`Via
`
`dé“Sid
`
`VeDid
`
`Samsung, Exh. 1045, p. 3
`Samsung, Exh. 1045, p. 3
`
`

`

`Patent Application Publication
`
`Aug. 6
`
`»2015 Sheet 3 of 21
`
`US 2015/0220905 Al
`
`zL
`
`3L¢é
`
`@
`
`widse:gOL0Z‘Oztal‘eleg
`
`
`
`
`
`wd/e'9GLOz‘Ozjudy‘ale
`
`
`
`
`
`yeu]‘Sayeoneyno,uodriod
`
`401GL0%‘SZaunpUOsauidxe
`
`
`
`UESUOIUAUOIMGeJONpOse
`
`
`
`ZuodhiosSuyasn|juemNOKOg'Q9'N$10)soud
`
`
`
`BonGa![Wmapuepalicdeaq
`
`Arii
`
`
`
`‘pauueosBulagswe:
`
`-GWENWOUS-FHPRP
`
`
`
`GOESSOU
`
`
`
`~BUEN)VOUS-1#JONPOdd|
`
`GBOLS“80d
`
`
`
`~SUB]LOUS-2#JONPold
`
`
`
`SES§Soud
`
`“WLOLYOdONLY
`
`
`
`‘pouuessHulagswe!
`
`LsuryBOLONSuCIg
`
`
`
`2Suey860)“ONB1035
`
`dé‘Sis
`
`aé‘Sia
`
`CeSid
`
`Samsung, Exh. 1045, p. 4
`Samsung, Exh. 1045,p. 4
`
`biJUEUOIEYY
`
`
`
`
`
`
`
`AOS
`
`sseuppySuey
`
`LeUBYyNOYY
`
`ssauppyBuel)
`
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 4 of 21
`
`US 2015/0220905 Al
`
`iéSia
`
`idiZ0su-3
`
`G601Sieoug
`
`$6$$ddud
`
`OG'O1GFOL
`
`
`paddyuodne-900%eeu
`wde'9O02‘Ozdy-a12q
`
`Laue}BBD}.ONGUIS
`~WENHOUS-1#lONPOlg
`~BIENHOUS-C#JONPOle
`
`~SWUENLOUS~Z#JONPC|
` Hé0¢De0¢
`wide?O02OZWAYIED|Nh4s
`
`OOOLS-HPSqauited
`
`juawAed O0bs-WeaviauikedSigSeb#bO'es~Fa
`
`
`/ue]8601ON2403S
`Le"CHPOE
`DéDis
`
`asuiedxyssouisng
`OBOLSHEIOL
`
`ssauoplyBLYWeyAl
`
`
`
`ssauppyBuyteyy
`
`LHUBLoA
`
`jglueyouayy
`
`
`
`fHDOYS
`
`POuyeil
`
`WELZ
`
`Samsung, Exh. 1045, p. 5
`Samsung, Exh. 1045, p. 5
`
`
`
`
`
`
`

`

`Patent App!
`
`icat
`
`ion
`
`ca
`Publi
`
`tion
`
`Aug
`
`-6,2015 Sheet 5 of 21
`
`US 2015/0220905 Al
`
`
`
`(SOdYana@)/OVWLplaid4e9N
`
`
`
`
`
`Grr)
`
`L£8
`
`uonenunuWwo;
`
`
`
`qualia]ainzas
`
`Ve‘Sis
`
`
`
`
`
`00lGnO13-WHOILV1dINSWAVdddd
`
`
`
`
`
`aalAagBundwogajqewog
`
`
`
`UONRIUNWIWIODar1IAAaguoHeIyHUAap|BIA8G
`
`
`
`
`
`voojnbuolss
`
`
`
`eseguole30Bail806Aejdsiga31naq
`
`
`
`[sdne2SOd|AJOSETTNOILVONGIZNIWNOSYIdcIddLNIWAVd/ONIddOHS
`peeNOWIWO2
`
`
`Bulualsog-0a5AV1dSIC
`
`926WL3omaenOLE
`
`
`
`uoletadNIMAVTdS/0
`
`
`eJOLUE)S31AaAWTdSIC
`
`
`
`avaeedINWanVlszy
`
`BLE
`
`N#ATSIC
`
`
`
`aBeoysuax0)GOd
`
`qnyuoWesiunUweg)a3aqg
`
`Samsung, Exh. 1045, p. 6
`Samsung, Exh. 1045, p. 6
`
`
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 6 of 21
`
`US 2015/0220905 Al
`
`PAYMENT APPLICATION 113
`
`Device Display
`
`908
`
`(Salah
`
`4
`
`naeiaseen SaRen] Lea aa En ee
`showmap ceeee|myaccount)(preferences}
`
`Skinning Capability
`
`aaeet
`16F—
`
`BA
`8BfTemmciect)|aartiF
`3
`
`318F 318G—Loplitcheck)(__gartlar_) CremattingJ
`
`332
`
`FIG. 3B
`
`Samsung, Exh. 1045, p. 7
`Samsung, Exh. 1045,p. 7
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 7 of 21
`
`US 2015/0220905 Al
`
`
`
`Alternate
`Payment
`Systems
`
`20A
`
`Credit
`Card(s)
`
`10
`Merchant
`Acquirer
`
`13
`
`VAULT
`
`Merchant Enterprise System
`
`16
`
`Central
`Mobile
`Payment
`Controller
`
`Mobile Wallet Token
`Receiver-Storage/
`PCD token
`generator
`
`AQ?
`
`mWallet
`
`Credit Switch
`
`Data Update
`
`Enterprise Router
`
`408
`
`MERCHANT POS SYSTEM
`Store Controller
`
`1392 Retail ECR
`
`12
`
`127
`
`410
`
`412
`8
`
`
` 134
`
`Handheld
`Scanner
`yalty, gif
`rg
`gift card
`loyalty,
`
`Magtips
`eader
`track data >
`
`MSR/PINpad
`track data >
`
`Cou
`:
`pons /
`Discounts
`
`N
`
`129
`
`.
`
`2x20 Moni
`x
`onitor:
`total >
`:
`Graphical
`Customer
`Display
`line item >
`
`131
`
`Samsung, Exh. 1045, p. 8
`Samsung, Exh. 1045, p. 8
`
`

`

`0cevo0d
`
`LWO¢
`
`qUaWalje¢/uoNezuouny
`
`c0S
`
`
`
`JauinboyJuUBYa//\
`
`
`
`asidsaUyJUeYDA|\
`
`waysks
`
`INSWAVdddd
`
`WHOSLWId
`
`(anoT9)
`
`Ua}JEMSI!GO/
`
`/aBbeios-JaAiaoay
`
`U840}OOd
`
`JOJEJBIUBD
`
`Patent Application Publication
`
`Aug. 6,2015 Sheet 8 of 21
`
`US 2015/0220905 Al
`
`
`
`Qzv0zBcVOC
`
`JuDY2iayy
`
`[#pso>
`
`SpseDFBL
`
`
`
`jJaqe]a3eAld
`
`Samsung, Exh. 1045, p. 9
`Samsung, Exh. 1045, p. 9
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 9 of 21
`
`US 2015/0220905 Al
`
`DBLdetVel
`
`
`
`
`
`
`
`(AdsWwLWOa)JUBWAEYaAQeUsaI\y7BULI[IgJOLIE)BUOYa}IGoWjeusaquy
`
`
`
`
`
`
`
`
`
`A8ldetdet
`anjenpau0ysysodagpuewagysodagazeusary
`
`
`
`
`
`LAsLage
`
`
`4apjACidJOPAupduio3AuodwozRy
`
`
`
`
`
`juawiADgquauliAndaulT-uioauly-uig
`cHTi#tZHTh
`
`yaldaVv
`
`waldayo
`
`cH
`
`TW
`
`WALSAS
`
`THONWYE
`
`
`
`POs£981celLOstVelVelYEks
`
`
`
`
`
`arkLINVAAVMSLVOVELAVM
`
`ALVS
`
`809909c09
`
`Lo
`
`
`
`YoUms§pad5
`
`9‘SI4
`
`
`
`qwodsued|Uolazesuet|
`
`
`JajOUODjueWwAeY
`SQ|ENUED
`
`
`USO!JIIEAAAl!QOV)
`jaBbeloyssaniesay
`
`usy4O)09d
`
`Joyeieueb
`
`Samsung, Exh. 1045, p. 10
`Samsung, Exh. 1045, p. 10
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 10 of 21
`
`US 2015/0220905 Al
`
`os
`
`A2ELAsn.
`
`ZG/ SUOHEDUNUWILUOD asludsajuq JUeYDIA|\) VlSis
`
`
`
`
`BuliaaisJapa)){bujaudpazijouossiagAnjdsipaaunjpg)(u)-uB}sAyjDAo}
`
`
`
`asoisejegWUeYUayyvedasoige1egwarsAsZEL210152184asp
`SUONEDUNWWODad!Aaglual|>
`
`
`(__saouarayaig—)gee
`
`
`Sassy24db15quDYyQIa)quawaBbpupjaainag
`
`
`
`
`sburddowgilsbuiddayy2/0,
`
`-jualWaboubl\
`
`O€ZUONeTUNWUIODJUaLAeg
`
`TELsuj8uqsajnyOV4Lez(bugaiquiasuzBEL
`
`
`Juawabounja2aq
`
`eaS/OMadl4[femaies|yy
`
`(GNO19)WHOSLV1dLNAWAVdGod
`
`dg9e4
`
`
`
`jUaIWAD,palda22%
`
`Su0HdQ
`
`shuiddoyyboy
`
`
`
`
`
`USO]JBIJIEASIQo/\
`
`jabesoys-seaiao3y
`
`us4O}GDd
`
`Jojesauab
`
`Samsung, Exh. 1045, p. 11
`Samsung, Exh. 1045, p. 11
`
`
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 11 of 21
`
`US 2015/0220905 Al
`
`ACCOUNT WEB-MGT PORTAL
`
`28, 30, 32
`
`28A
`(web & OMW
`
`Enrollment
`
`
`
`
`Firewall/Security722A1
`
`28
`
`28
`
`28E
`
`Reporting
`
`28
`
`F
`
`28G
`
`Mobile Wallet Token
`
`
`Receiver-Storage/
`PCD token
`
`
`
`generator
`
`PCD PAYMENT
`PLATFORM
`(CLOUD)
`
`FIG. 7B
`
`Samsung, Exh. 1045, p. 12
`Samsung, Exh. 1045, p. 12
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 12 of 21
`
`US 2015/0220905 Al
`
`28,30,32
`
`WELCOME TO YOUR ACCOUNT(S)
`MANAGEMENT WEBPAGE
`
`ACCOUNT# 1 (endingin 1234)............. $2400
`ACOOUNT# 2 (ending in 5678)............. $10,000
`28F 1
`
`[JNO
`
`USE ACCOUNT#1 FOR MOBILE PAYMENTS?
`[_]YEs
`X<JNo
`Pek
`
`USE ACCOUNT#2 FOR MOBILE PAYMENTS?
`<lYEs
`
`FIG, 7C
`
`Samsung, Exh. 1045, p. 13
`Samsung, Exh. 1045, p. 13
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 13 of 21
`
`US 2015/0220905 Al
`
`)00
`
`879
`
`880
`
`808
`
`NFC
`Antenna
`
`Power
`Supply
`
`82
`
`[Tovensraen|
`840
`828
`Touchscreen
`842
`830
`p-—__-#
`Cont.
`Display V
`336
`
`854,|
`
`Port
`
`MEMORY
`
`Stereo
`
`
`860,|Speaker Amp.
`
` 838
`
`
`
`
`856,
`[Speaker rae
`Mecoana
`M/ /|__[
`FM
`
`864
`
`Tuner
`
`3858
`
`86
`
`850
`
`tereo
`Headphones
`866
`
`863
`
`Keypad
`Mono
`Headset}
`w/ micro.
`
`874
`
`876
`
`FIG. 8
`
`878
`
`Samsung, Exh. 1045, p. 14
`Samsung, Exh. 1045, p. 14
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 14 of 21
`
`US 2015/0220905 Al
`
`[#JUBYOJAY\ 006
`
`006
`
`sseippyBueyy
`
`
`
`Jequinysuoyg
`
`L#UeYoe\
`
`ssaippyGuljeyy
`
`JAQGUNNBuoy
`
`
`
`
`
`Wd6E'80102'Sz.Udyied
`
`481‘ClSOd
`
`
`
`ino,YUeYL
`
`INOJOUdyO}BSY
`
`
`
`
`
`yoajasaseajduoyeroadde
`
`€6£9-WLOL
`
`ooes-eaHEUDIOWN
`
`pledWO
`
`Z9--dlSOd
`
`-pagJUBYOJA/\
`
`00015poyjuawhed
`
`C#POWjSlU
`
`juawAed
`
`
`
`
`
`Wd6E'80102‘SZludy‘ajeq
`
`
`
`junoooyjuawe4
`
`YIMHOYO}
`
`JUBYOJaI\|MAN
`
`
`
`Buimoyjoyay}joauoAUe
`
`‘SJANO
`
`g6Sis
`
`V6‘Sls
`
`Samsung, Exh. 1045, p. 15
`Samsung, Exh. 1045, p. 15
`
`

`

`US 2015/0220905 Al
`
`y
`
`1030
`
`Encrypt merchant acq.
`token and mobile wallet
`
`Transmit merchant acq. token
`with transaction data to merchant
`acquirer and mobile wallet token
`
`1035
`
`1040
`
`mobile wallet token Aug. 6,2015 Sheet 15 of 21
`
`Patent Application Publication
`
`Start Method for Loading
`Merchant Card Account Data
`into Vault (for future PCD use)
`with POS
`
`Receive input designating
`that merchant account
`should be saved in vault
`for future paymentvia a
`PCD
`
`Encrypt account data
`
`Transmit first authentication
`code and encrypted account
`data to merchant enterprise
`system
`
`Retransmit encrypted account
`data with a second
`authentication code to vault
`
`Create merchant acq. token and
`
`token
`to PCD paymentplatform (cloud)
`to mobile wallet token
`future use
`
`Store mobile wallet token and
`create PCD token corresponding
`
`Transmit PCD token to PCD for
`
`1045
`
`1050
`
`Determine if paymentfor
`transaction should be authorized
`based on merchant acg. Token
`and transaction data
`
`Goto Fig. 10B,
`
`Step 1055
`
`FIG. 10A
`
`Samsung, Exh. 1045, p. 16
`Samsung, Exh. 1045, p. 16
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 16 of 21
`
`US 2015/0220905 Al
`
`From Fig. 10B,
`
`Step 1050
`
`10008
`
`
`
`
`1055
`
`Generate authorization response
`and transmit merchant acq. token
`and response to merchant
`enterprise system
`
`Store response and
`merchant acq. token
`
`1065
`
`Transmit authorization response
`to merchant POSfor approving
`transaction
`
`FIG. 10B
`
`Samsung, Exh. 1045, p. 17
`Samsung, Exh. 1045, p. 17
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 17 of 21
`
`US 2015/0220905 Al
`
`
`
`Start Method for Using
`
`Pre-Loaded Merchant Account
`
`
`from Vault with a PCD for a
`
`Transaction
`
`y
`
`1130
`
`Apply tender steering rules
`at PCD paymentplatform
`
`(cloud)
`
`1135
`
`Send paymentoptions to PCD
`
`1140
`
`Receive selection of merchant
`
`accountfor payment from PCD
`PCD paymentplatform (cloud)
`
`Send PCD token from PCD to
`
`1145
`
`1105
`
`Receive input from POS
`that payment via PCD is
`desired and relay input to
`merchant enterprise
`
`system
`
`1110
`Receive confirmation that
`PCD paymentis desired
`
`4115
`
`Receive ID associated with
`
`Determine if operator ID
`
`1120
`
`1125
`
`lf match exists, transmit
`message that one or more
`accounts associated with
`operator exist in Vault
`
`operator of PCD
`matches any accounts in Vault
`enterprise system
`
`1150
`
`Match PCD token with mobile
`wallet token (created by Vault)
`
`1155
`
`Transmit mobile wallet token
`(created by Vault) to merchant
`
`Goto Fig, 11B,
`Step 1160
`
`
`
`
`
`
`FIG. 11A
`
`Samsung, Exh. 1045, p. 18
`Samsung, Exh. 1045, p. 18
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 18 of 21
`
`US 2015/0220905 Al
`
`From Fig, 11A,
`Step 1155
`
`Receive mobile wallet token with
`merchantenterprise system (i.e.
`retailer payment processor)
`
`4465
`Match mobile wallet token
`with transaction data
`
`Transmit mobile wallet token and
`transaction data to Vault
`
`.
`;
`Match mobile wallet token with
`merchant acg. token
`
`Determineif payment for
`transaction should be authorized
`based on merchant acq. Token
`and transaction data
`
`Generate authorization response
`and transmit merchant aca. token
`and response to merchant
`enterprise system
`
`1195
`
`Store response and
`merchantacq.token
`
`
`
`
`
`Transmit merchant acg. Token
`
`Transmit authorization response
`to merchant POSfor approving
`
`merchant acquirer
`
`payment platform
`
`FIG. 11B
`
`Samsung, Exh. 1045, p. 19
`Samsung, Exh. 1045, p. 19
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 19 of 21
`
`Start Method for Loading Bank
`Issued Card, Fl Credit Card, or
`alternative payment account
`data for PCD paymentsvia a
`secure website
`
`Receive trom website a
`message for account to be
`used for payments via
`PCD
`
`US 2015/0220905 Al
`
`41200
`
`future use
`
`Issue mobile wallet token from
`account issuing entity (Bank, other
`Fl issuer entity, Alternative
`payment provider)
`
`Receive with PCD payment
`platform (cloud) the mobile
`wallet token from account
`issuing entity
`
`Generate PCD token
`corresponding to mobile wallet
`token
`
`Transmit PCD token to PCD for
`
`FIG. 12
`
`Samsung, Exh. 1045, p. 20
`Samsung, Exh. 1045, p. 20
`
`

`

`Patent Application Publication
`
`Aug. 6,2015 Sheet 20 of 21
`
`US 2015/0220905 Al
`
` Start Method for Using
`
`
`
`
`
`Pre-Loaded Bank Issued Card,
`Fl Credit Card, or allernative
`payment account data with a
`PCD for a Transaction
`
`
`
`1305
`
`
`
`
`Receive input from POS
`that payment via PCDis
`desired and relay input to
`merchant enterprise
`system
`
`
`
`
`
`
`
`1310
`Receive coniirmation that
`PCD paymentis desired
`
`1315
`
`Receive ID associated with
`
`operator of PCD
`matches any accounts in Vault
`operator exist in Vault
`
`Determine if operator ID
`
`1320
`
`1325
`
`If match exists, transmit
`messagethat one or more
`accounts associated with
`
`:
`
`1330
`
`Apply tender steering rules
`at PCD payment platform
`
`(cloud)
`
`1335
`
`Send payment options to PCD
`
`1340
`Receive selection of at least one
`ofBank Issued, Fl account, and
`
`Alternate payment for payment from PCD
`PCD paymentplatform (cloud)
`provider)
`
`Send PCD token from PCD to
`
`1345
`
`1350
`Match PCD token with mobile
`wallet token (created by Bank, FI
`account, or alternative payment
`
`1355
`
`Transmit mobile wallet token
`(created by Vault) to merchant
`enterprise system
`
`Goto Fig. 13B,
`Step 1355
`
`
`
`
`
`
`FIG. 13A
`
`Samsung, Exh. 1045, p. 21
`Samsung, Exh. 1045, p. 21
`
`

`

`Patent Application Publication
`
`Aug. 6, 2015
`
`Sheet 21 of 21
`
`US 2015/0220905 Al
`
`From Fig. 136,
`Step 1355
`
`
`
`
`
`
`yi
`
`1380
`
`Determine if payment for
`transaction should be authorized
`based on mobile wallet Token
`
`and transaction data
`enterprise system
`
`1385
`
`Generate authorization response
`and transmit mobile wallet token
`and response to merchant
`
`1360
`
`Receive mobile wallet token with
`merchant enterprise system (i.e.
`
`retailer payment processor)
`
`1365
`
`Match mobile wallet token
`with transaction data
`
`1370
`Transmit mobile wallet token and
`transaction data to either
`merchant acquirer or Fl issuer or
`alternative payment provider
`
`database
`
`actual account in Bank
`database, F| database, or
`alternative payment provider
`
`1390
`
`Store response and
`mobile wallet token
`
`1395
`
`Transmit authorization response
`to merchant POS for approving
`transaction and to PCD via PCD
`
`paymentplatform
`
`END
`
`FIG. 13B
`
`Samsung, Exh. 1045, p. 22
`Samsung, Exh. 1045, p. 22
`
`

`

`US 2015/0220905 Al
`
`Aug. 6, 2015
`
`SYSTEM AND METHOD FOR MANAGING
`PAYMENTIN TRANSACTIONS WITH A PCD
`
`PRIORITY AND RELATED APPLICATIONS
`STATEMENT
`
`(0001) This patent application claims priority under 35
`ULS.C. §119(e) and is related to U.S. Provisional Patent
`Application Ser, No, 61/611,344, filed on Mar. 15, 2012.
`enlitled, “System and Method For Managing Payment In
`‘Transactions With A PCD." the entire contents of whichare
`hereby incorporated by reference.
`
`DESCRIPTION OF THE RELATED ART
`
`Portable computing devices (PCDs) are becoming
`[0002]
`necessities for people on personal and professional levels.
`These devices may include cellular telephones, portable digi-
`ta] assistants (PDAs), portable game consoles, palmtop com-
`puters. and other portable electronic devices.
`[0003]
`PCDs are often utilized to conduct financial trans-
`actions. For example, PCDs may be used to check bank
`account balances, transfer funds between bank accounts, and
`for paying bills. While PCDs are useful for these types of
`transactions, there is a growing need in the art for utilizing
`PCDs in other types of transactions.
`[0004]
`‘These other types of transactions may include those
`in which physical tokens, suchas credit cards. gift cards, and
`stored value cards, are typically used, One problem faced by
`many consumers is thal each consumer may be issued a
`separate account corresponding to a single merchant or single
`service provider. Often, the merchant or service providerwill
`send each consumer a physical token that correspondsto the
`account Each physical token typically has account informa-
`tion provided on it as well as machine-readable codes so that
`point-of-sale (“POS”) terminals can easily process these
`machine-readable codes.
`
`In addition to machine-readable codes, each physi-
`[0005]
`cal token usually has human-readable codes as a back-up for
`the machine-readable code if the machine-readable code fails
`fora particular transaction, In some instances, a merchant or
`service provider may not have a machine reader to read the
`machine-readable code. In such scenarios, the human-read-
`able code maybe used.
`[0006]
`Physical tokens may also be required by merchants
`or service providers as a form of identification ofthe con-
`sumer and his or her corresponding account. Often, physical
`tokens may be required by a merchantor service provider so
`that any value associated with the token may be redeemed by
`the consumer.
`
`(0007) Tfaconsumerhasa plurality ofaecounts, suchas on
`the order offive or more, then the consumer will likely carry
`the same amount ofphysical tokens on his or her person. This
`can be problematic because the physical tokens do consume
`space and do require the consumer to remember to carry them
`on his or her person. Ifa consumer has ten or more accounts
`which corresponds to ten or more physical tokens, then the
`management of these physical tokens becomessignificantly
`burdensome and problematic for the consumer,
`[0008] Accordingly. what is needed is a system and method
`that may overcome the problems associated with physical
`tokens. Specifically, a system and method is needed for elimi-
`nating the use of physical tokens for various types oftrans-
`
`actions so that a consumer may track one or more accounts
`with merchants and/or service providers wilh ease using a
`single PCD,
`
`SUMMARYOF THE DISCLOSURE
`
`[0009] According to one exemplary aspect of the system
`and method, a mobile wallet token is received from an
`account issuing entity. Next, the mobile wallet token is stored
`intmemory within a portable computing device paymentplat-
`form. A portable computing device token that corresponds
`with the mobile wallet token is generated by the portable
`computing device payment platform. The portable computing
`device token is transmitted over a communications network
`for use in transactions in Which an operator selects a portable
`computing device io make a payment, The mobile wallet
`token corresponds toat least one of: a credit card account, an
`alternative or non-traditional payment account, a stored value
`account, an account from a financial institution. and a mer-
`chant based card account.
`
`token may be generated in
`[0010] Each mobile wallet
`response to receiving input from a point-ol-sale system thal
`future use ofa payment account with the portable computing
`device is desired, Alternatively, a mobile wallet token may be
`generated by an account issuing entity in response to receiv-
`ing input from an on-line portal thatfuture use of a payment
`account with the portable computing device is desired.
`[0011] With the mobile wallet tokens and PCD tokens man-
`aged by the PCD payment platform, this structure ollers al
`least two layers ofsecurity for credit card or other type of
`payment account data, The mobile wallet tokens and the PCD
`tokens maynot contain any relevant account data. The corre-
`spondence or relevance of PCD tokens to their matching
`mobile wallet tokens is only known to the PCD payment
`platform. Similarly,
`the correspondence or relevance of
`mobile wallet tokens to actual payment accounts (i.e, credit
`card accounts, gifl card accounts, bank accounts, etc.) is only
`known to the account issuing entity, like the alternative pay-
`ment systems, credit card systems, bank card systems, and
`vaults. As described above, these account issuing entities are
`responsible for generating the mobile wallet tokens.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`Inthe Figures. hke reference numerals refer to like
`[0012]
`parts throughout the various views unless otherwise indi-
`cated, For reference numerals with letter character designa-
`ions such as “102A” or “L028” the letter character designa-
`tions may differentiate two like parts or elements present in
`the same Figure, Letler character designations for reference
`numerals may be omitted whenit is intended that a reference
`numeral to encompass all parts having the same reference
`nunieral in all Figures.
`[0013]
`FIG. Lisadiagram ofa wireless portable computing
`device (“PCD”) coupled to a wireless communicaions net-
`work which are integral parts of a system lor managing pay-
`ment transactions with the portable computing device;
`(0014)
`FIG. 2A isa diagramofa screenfor entering a user's
`Jog-in credentials on the PCD 10 access the system:
`[0015]
`FIG. 2B is a diagram ofa screen for entering addi-
`tional log-in credentials such as a password on the PCD to
`access the system:
`(0016)
`PIG, 2C is a diagramola screen for the PCD con-
`firming access to system;
`
`Samsung, Exh. 1045, p. 23
`Samsung, Exh. 1045, p. 23
`
`

`

`US 2015/0220905 Al
`
`Aug. 6, 2015
`
`FIG. 2D is a diagram of a screen that shows the
`(OU17])
`contents of an image being scanned with a camera ofthe
`PCD;
`VLG. 2E is a diagram of a screen that shows mer-
`[0018]
`chant information releyant to a transaction and a line item
`listing of products being scanned by a product scanner
`coupled to an electronic cash register:
`[0019]
`FIG.2PFisa diagramofa screen that shows merchant
`information relevantto a transaction and a coupon option that
`may be selected by 4 user;
`[0020]
`FIG. 2G is a diagram ofa screen that shows mer-
`chant information relevant to a transaction and a total bill for
`a purchase along witha plurality of payment options that may
`be selected by a user:
`[0021]
`FIG. 2H is a diagram of a screen that shows an
`electronic receipt that may be provided upan completionofa
`transaction with a merchant:
`(0022)
`FIG. 2] is a diagram of an exemplary machine-
`readable tag that may be coupled to an electronic cushregister
`ofa merchant;
`[0023]
`FIG. 3A is a diagram ofhardware components and
`software components running on a portable computing
`device for supporting transactions with the portable compul-
`ing device:
`[0024]
`PIG. 3B is a diagram ofseveral software compo-
`nents for a payment application running on a portable com-
`puting device:
`[0025]
`PIG. 4is a diagramillustrating details for the mer-
`chant point-of-sale system and the merchant enterprise sys~
`tem of FIG. 1 for completing a sales transaction:
`[0026]
`FIG. 5isa diagramillustrating details of a merchant
`acquirer and credit card subsystems of FIG. 1 for completing
`a sales transaction:
`(0027) VIG. 6is a diagram illustrating details ofa gateway
`and alternative payment systemsillustratedin FIG. 1;
`(0028)
`FIG. 7A is diagram illustrating details forthe central
`mobile payment controller illustrated in FIG. I that assists
`with providing personalized pricing and ensemble sugges-
`tions for the PCD consumer:
`[0029]
`FIG. 7B is a diagramillustrating several on-line
`portals for managing payment accounts according to one
`exemplary embodiment ofthe invention:
`(0030)
`FIG. 7C is a diagram illustrating an exemplary
`account on-line (web) management portal for generating
`mobile wallet tokens:
`[0031]
`FIG. 8 isa functional block diagramillustrating an
`exemplary portable computing device (“PCD”) that may
`include PCDtoken storage:
`[0032]
`FIG. 9A is a diagram of a sereen that shows mer-
`chant information relevant to a transaction and a total bill for
`a purchase along with a plurality of offers which were gen-
`erated by a tendersleering algorithm: and
`[0033]
`FIG. 9B is a diagram ofa screen that shows mer-
`chant information relevant to a transaction and a total bill tor
`a purchase along witha plurality of payment optionsthat may
`be selected by user and which were re-ordered by a tender
`steering algorithm.
`[0034]
`FIGS. 104-10B are flowcharts illustrating a method
`for loading merchant card accountdata into a vault for future
`PCDuse with a point-of-sale terminal:
`[0035)
`PIGS. 114-11B are flowcharts illustrating a method
`for using a preloaded merchant account from a fault with a
`PCD for completing a payment transaction;
`
`PIG. 12 is a fowehart illustrating a method for load-
`[0036]
`ing bank issued card data. financial institution (“other card
`issuer’) credit card data, or allernative payment account dala
`for PCD payments via a secure online portal (i.e., a website):
`and
`FIGS. 13.A-13B are fowcharts illustrating a method
`(0037)
`for using preloaded bank issued card data, financial institu-
`lion (“other cardissuer”) credit card data, or alternative pay-
`ment account data with a PCD for a payment transaction.
`
`DETAILED DESCRIPTION
`
`[0038] The word “exemplary”is used herein to mean “serv-
`ing as an example,
`instance, or illustration.” Any aspect
`deseribed herein as “exemplary”is not necessarily to be con-
`strued as preferred or advantageous over other aspects.
`(0039)
`In this description, the term “application” may also
`include files having executable content, such as; object code,
`scripts. byte code, markup language files, and patches, In
`addition, an “application” referred to herein, may also include
`files that are not executable in nature, such as documents that
`may need to be opened or other datafiles that need to be
`accessed.
`
`[0040] The term “content” may also include files having
`executable content, such as: object code, scripts, byte code.
`markup language files. and patches, In addition, “content”
`referred to herein, may also include files that are not execut-
`able in nature, such as documents that may need to be opened
`or other data files that need to be accessed,
`[0041] As used in this description, the terms “component.”
`“database.” “module.” “system.” and the like are intended to
`refer to a computer-related entity, either hardware, firmware,
`a combination of hardware and software. solbware, or saft-
`ware in execution. Por example, a component may be, but is
`not limited to being, a process running on a processor. a
`processor, an object, an executable. a thread of execution. 4
`program, and/or a computer. By way ofillustration, both an
`application running on a computing device and the comput-
`ing device may be a component. One or more components
`may reside within a process and/or thread of execution, and a
`component may be localized on one computer and/ordistrib-
`uted between two of more computers. In addition, these com-
`ponents may execute from various computer readable media
`having various data structures stored thereon. The compo-
`nenls may communicate by way of local and/or remote pro-
`cesses such as in accordance with a signal having one or more
`data packets (e... dala from one component interacting with
`another component in a local system, distributed system,
`and/or across a network such as the Internet with other sys-
`tems by way ofthe signal).
`the terms “communication
`[0042]
`In this deseription.
`device,” “wireless device.” “wireless telephone,” “wireless
`communication device,” and “wireless handset” are used
`interchangeably, With the advent ofthird generation (“3G")
`wireless technology and four generation ("4G"), greater
`bandwidth availability has enabled more portable computing
`devices with 4 greater variety of wireless capabilities. There-
`fore, a portable computing device may include a cellular
`telephone. a pager, a PDA, a smartphone, a navigation device,
`or a hand-held computer, like a tablet PC, with a wireless
`connection or link.
`[0043] Reterring initially to FIG. 1, this figure is a diagram
`of a wireless portable computing device (“PCD”) 100
`coupled to a communications network 142 via a wireless
`communication link 103.4 which are integral parts ofa sys-
`
`Samsung, Exh. 1045, p. 24
`Samsung, Exh. 1045, p. 24
`
`

`

`US 2015/0220905 Al
`
`Aug. 6, 2015
`
`tem 101 (also referred to herein as a transaction management
`system 101) for managing wansactions with the portable
`computing device 100,
`0044] Many of the system elements illustrated in FIG. 1
`are coupled via communication links 103 to the communica-
`tions network 142, The communication links 103 illustrated
`in FIG, 1 may comprise wired or wireless links. Wireless links
`include, but are not limited to, radio-frequency (“RF”) links,
`infrared links, acoustic links, and other wireless mediums.
`The communications network 142 may comprise a wide area
`network (“WAN”), a local area network (“LAN”), the Inter-
`net, a Public Switched Telephony Network (“PSTN”), a pag-
`ing network, or a combination thereof
`[0045] The communications network 142 may be estab-
`lished by broadcast RP transceiver lowers (not illustrated),
`However, one of ordinary skill in the art recognizes that other
`types of communication devices besides broadcast RE trans-
`ceiver towers are included withinthe scope ofthis disclosure
`for establishing the communications network 142,
`[0046] The PCD 100is shown to have a RF antenna 872
`(see FIG. 8) so that a respective PCD 100 may establish a
`wireless communication link 103.4 with the communications
`network 142 via RF transceiver towers (not illustrated), The
`portable computing device (PCD) 100 may support a pay-
`ment application 113 that may reside in memory 803 (See
`FIG. 8) of the PCD 100. The PCD 100 may also include PCD
`token storage 117 that may be part of and/or in additionto
`memory 803. ‘The PCD token storage 117 may contain PCD
`tokens issued by the PCD payment platform (cloud) 50as will
`be described in further detail below.
`
`(0047) The payment application 113 may allow the PCD
`100 to communicate with the PCD paymentplatform 50 over
`the communications network 142. The payment application
`113 may also allow the PCD 100 to collect information from
`a machine-readable tag 124 (also referred to herein as tag
`124) that may be coupled to an electronic cash register
`(“ECR”) 412 (not illustrated in FIG. 1, but see FIG. 4) of a
`check-out system 90B. Further details about the check-out
`system 90B will be described below in connection with FIG,
`3A.
`[0048] The machine-readable tag 124 may comprise a
`unique merchant identifier and a unique terminal (or elec-
`tronic cash register) identifier that helps the PCD 100.
`to
`manage point-of-sale (POS)
`transactions, Further details
`about the machine-readable tag 124 will be described below
`in connection with FIG. 21. The ECR 412 (not illustrated in
`FIG, 1, but see FIG. 4) of the Merchant POS system 12 may
`comprise a mechanical or electronic device or combination
`thereof for calculating and recording sales transactions. The
`ECR 412 of the merchant POS system 12 may produce a
`physical receipt 127 at the end ofa transaction that lists goods
`and/or services purchased with the portable computing
`device 100. Further details about the merchant POS system
`12 will be described below in connection with FIG. 4.
`(0049)
`‘The merchant POS system 12 may be coupled to the
`merchant enterprise system 16 via the communications nel-
`work 142. The merchantenterprise system 16 may support
`the completion of transactions when credit cards or when
`bank cards have been selected as a form of payment for a
`particular transaction. The merchant enterprise system 16
`may be coupled to