US 20130246258A1
`
`(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2013/0246258 A1
`
` Dessert (43) Pub. Date: Sep. 19, 2013
`
`
`(54) SYSTEM AND METHOD FOR MANAGING
`PAYMENT IN TRANSACTIONS WITH A PCD
`
`(75)
`
`Inventor: Robert Dessert, Canton, GA (US)
`
`(73) Assignee: FIRETHORN MOBILE, INC.) Atlanta,
`GA (US)
`
`(2]) App]. No.: 13/481,766
`
`(22)
`
`Filed:
`
`May 257 2012
`
`Related U.S. Application Data
`
`(60) Provisional application No. 61/611344, filed on Mar.
`15, 2012.
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`G06Q 20/36
`
`(2012.01)
`
`(52) U.S. Cl.
`
`G06Q 20/367 (2013.01)
`CPC
`USPC ............................................... 705/41; 705/16
`
`_
`(37)
`
`ABSTRACT
`
`A system and method for managing payment in a transaction
`using a portable computing device (“PCD”) includes amobile
`wallet token being received from an account issuing entity.
`Next, the mobile wallet token is stored in memory within a
`PCD payment platfonn (Le, a cloud payment solution). A
`
`PCD token that corresponds with the mobile wallet token iS
`generated by the PCD payment platform. The PCL) token iS
`transmitted over a communications network to a PCD. The
`mobile wallet token corresponds to at least one of: a credit
`card accountS 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 input
`from an on—line portal that future use of a payment account
`with a PCD is desired or in response to input received from a
`point-of—sale terminal.
`
`66
`
`20A
`
`.- ———————MOBILE WALLET TOKEN ————————————
`}l |— MOBILE \NALLET TOKEN—————— "I
`:
`18 N r101
`I 203
`I
`Aiternative Payment
`I
`|
`
`,
`
`66\
`
`I’ — MOBiLE WALLET TCKEN- —
`
`Credit Card(s)
`
`Bank Card(s)
`
`10
`
`|
`|
`
`|| I
`
`— — — T — Ji— — —
`
`L .i
`Mobile Wallet Token
`Portal
`
`System(s)
`
`MOBiLEWALLETTUKEN—
`
`14
`
`GATEWAY
`
`l
`:
`|
`
`Merchant ACqUH'el'
`
`— — —
`
`VAULT
`
`13
`
`16
`— — Merchant Enterprise
`System
`5
`Merchant POS
`
`12
`
`System(s)127
`
`44
`
`‘
`G00d(s)/SerVice(s)
`
`l
`:
`|
`|
`
`||
`
`Receiver-Storage/
`POD me”
`generator
`
`PCD Payment
`Platform
`(cloud)
`
`142
`
`Communications
`Network
`
`103A
`
`100
`
`Portable/Mobile
`Computing Device
`1 13
`Payment Application
`
`117 PCD Token storage
`
`90B
`CheCKPOut System
`124
`TAG
`
`Google LLC v. RFCyber Corp. / Page 1 of 41
`
`GOOG-1032
`
`28
`
`F| Card Issuer
`Account Web-MGT
`
`3O
`Bank Card Issuer
`Acoount Web—M GT
`Portal
`
`32
`
`.
`iifijrirsi/ZSE/Jggt
`Portal
`
`103
`
`'
`
`872
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 1 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 1 0f 21
`
`US 2013/0246258 A1
`
`398ESE98€90moEgan.gfieez_<8_momEX__lllllll
`
`
`ZmEOF._.m_n_._<>>m_I__mOS_I__/wm||||||||||||
`
`
`zmxok5.122,m..__m_o_>_|I|IIIIl
`
`
`
`3:663
`
`__
`
`_____or_
`
`._2_:co<E2952
`_8323S"ELotmE5ngch
`
`
`
`
`EwE>mn_con.:39com
`
`
`
`rIIImmIIIII:335:932522/I.zme.5.333550:/I_
`
`
`
`\mmmhofimingmmIExEEj<>>550:
`
`
`
`
`
`8:925Emcee:||
`
`__
`
`wenE29228m
`
`RV
`
`AwVEBw>w
`
`NS‘
`
`mco:mo_c:EEoo
`
`{02sz
`
`385593508$258298xcmm
`
`52-925E88<
`
`.gsoégnmcom_‘0-n—08m2
`
`O<._.
`
`
`
`$92on.5oncon.
`
`
`E996Bogooco>9:509:888
`erm_\_.NNw
`
`
`
`
`co_#mo__aq<E998;
`
`_mtom
`
`
`
`EmE>mn_m>szmg<
`
`
`
`._.O_>_-go>>Esooo<
`
`_mtom
`
`23maooG
`14fO2e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`mm
`
`><>>m_._.<0
`
`63$.28_n_
`
`
`
`._.mu_>_-pm>>E30091
`
`_mtoa
`
`
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 2 of 41
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 2 0f 21
`
`US 2013/0246258 A1
`
`
`
`Am66000000
`
`mnoumwmmas.»Ecm
`
`wow
`
`
`
`
`
`326%.mmeg£28afig
`
`
`
`2:82am:
`
`<3m
`
`23maooG
`14fo3e9aPla.roCrebV.CFRv.CLLb9ooG
`
`
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 3 of 41
`
`
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 3 0f 21
`
`US 2013/0246258 A1
`
`ma,
`
`EN
`
`I({
`
`ES2%.3Sq“2gii88.33$3
`
`
`
`p.23mm?.029%5.$3$2dz2%
`
`$95K92%EE2332
`
`wmmfig9ngEEfiufia
`
`
`
`5,;gang.EEm93:8,
`
`5%wow.mmwas;S8:98
`
`,umémum@5meEat
`
`.mamzng-2568m..:
`
`mmg”SE
`
`
`
`
`
`8.6%“3.new323%Bcan.figs).55%.wk@38an
`
`Em;3%cm.83é$3
`
`
`
`wcSS%£2,
`
`
`
`;mEmztogm.E3:85
`
`m.3%”8:1
`
`
`
`-mEmZfioxw-wk«ujvchm
`
`$3SE
`
`
`
`,..q<,5hm0;szfia
`
`“mmccmum38$3
`
`
`
`wzwzznam
`
`
`
`23maooG
`14fO4e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 4 of 41
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 4 0f 21
`
`US 2013/0246258 A1
`
`Pu223mg“2%322%
`
`
`
`23maooG
`14fO5e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`
`
`,mEmztogw.%338$
`
`305”$5
`
`.meZEm;m“338$
`
`
`
`mama”3%
`
`umimqEganx8cmNEE
`
`
`
`,.mgmztoflm,.Q“Emmi
`
`
`
`$memewwmgamm
`
`
`
`8.3%NEE;_,
`
`_08%,E55
`
`
`
`gamma2%“amEnd“mamEfimnm03m.3=54$8
`
`N9:3mg.32$onm2338.oz39w
`
`
`
`Emmmmim39%”ES.
`
`
`
`gym?“@3me£52@9ng
`
`
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 5 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 5 0f 21
`
`US 2013/0246258 A1
`
`<vm_\
`
`mtoEumm0
`
`GE£3@wE
`
`3mix
`
`mmm
`
`nmw
`
`Eu:302
`
`:osfluczEEou
`
`
`
`HCMEMFMMLBUMM.
`
`METRO
`
`
`
`>3.>SQWE
`
`<m.0."—
`
`$329552
`
`22:88Es>3&5
`
`55%$5on:32.Don
`
`mew99:8833\EQQEQ
`
`
`sZEDEflmcozmo__qa<E9981
`
`23maooG
`14fO6e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`
`
`
`
`cots333.5.
`
`
`
`mEzoonqémbAmwmflww‘nmu
`
`
`
`
`
`NNWwmu_>‘_wmmHHZO_._.<u_._n_n_<._.Zm_>_><n_\muz_n_n_OImouN_._<ZOmxmn_
`
`
`
`
`
`02930.6-sick/j;pzmzkimom
`
`
`
`cozmuEzEEou33mg
`
`
`
`QDICOEGUEJEEO
`
`
`
`0mm:0.muO_um.u._wom>m_nm_n_33mm.
`
`2252552838
`
`wowwow
`
`
`
`$3232«ESE
`
`SEWERQ8.3mm
`
`
`
`83.8mESQEoO923.01
`
`in
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 6 of 41
`
`
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 6 0f 21
`
`US 2013/0246258 A1
`
`Device Display
`
`908
`
`PAYMENT APPLICATION 113
`
`F_3MH
`=P-d
`
`3166
`316F
`in—-—t0re _i5titems
`
`Skinning Capability
`
`1-L
`-316K
`_1-°B-1-C 1D
`
`1E
`
`Darrin/paid
`
`318F
`
`3186
`
`3181—1
`
`332
`
`FIG. 3B
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 7 of 41
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 7 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 7 0f 21
`
`US 2013/0246258 A1
`
`Alternate
`
`Payment
`
`20A
`
`Credit
`
`‘10
`
`Merchant
`
`Systems
`
`Card(s)
`
`Acquirer
`
`V
`
`402
`
`404
`
`mWaIlet
`
`Credit Switch
`
`Data Update
`
`Merchant Enterprise System
`
`Central
`.
`Mob'le
`Payment
`Controller
`
`Mobile Wallet Token
`Receiver—Storage/
`PCD token
`
`generator
`
`Enterprise Router
`
`408
`
`410
`
`MERCHANT POS SYSTEM
`
`Store Controller
`
`132 Retail ECR
`
`canner
`Handheld
`9
`
`”$2232?
`track data 9
`
`.
`
`.
`
`.
`
`.
`
`2 x 20 Monitor
`total 9
`
`131
`
`Graphical
`Customer
`Display
`line item -)
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 8 of 41
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 8 of 41
`
`

`

`Patent Application Publication
`
`S
`
`wmy
`
`
`
`35355.m:0oncom2,\ononLmZmommwEmEoEmm:38.Hm=m>>2522m1\cosmNtofs<
`
`
`
`
`
`momN<ONw<om
`
`2:8v.53v.28map.83353:.
`
`mom
`
`
`
`5:391E2822
`
`thUN309ECU
`
`EmEmu
`
`EONnm<ommm<ommm<ommr<om
`
`
`
`
`JED€ng
`
`fEmofifimw.o3:80ccm0.6mm.gm:c_>_
`Fzm_>_><n_co;m
`
`SRUv.
`
`1gAo00GD2.“3wMm2Cma3lbm0.".
`
`CLL
`
`21m44.mmw
`
`
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 9 of 41
`
`
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 9 0f 21
`
`US 2013/0246258 A1
`
`n_w_\meam; 8»UV.mu3
`m:_w>“v9.9.9.:8an.9:me0:8an32.3.6.
`
`
`
`
`
`E9.warE?52‘
`
`.6335.EESEQ>=chouxcquou~22§EEqu$5.13vawwmwm
`
`
`
`
`
`#03mom:NOEr09<3<8_\<w_\
`.muEEEoumvEwe—San.w>=me£<mc==m.2th98;;2505.EEEE
`
`
`
`
`
`E:08<NuUm
`
`
`
`gm2::Cm
`
`9;52>><>>E<o3.£3,520 LBEW:35
`wowwowN8
`
`\mmSoym;o>_moom
`
`:39non
`
`56$:me
`
`m5
`
`ONQ
`
`SoNF0
`
`m5
`
`
`
`toamcmt.cofiummcmt.
`
`
`
`0:2226.250
`
`
`5:350EmE>mn_
`
`
`:38.#w__m>>9522
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`23maooG
`14fOo1egaPla.
`
`
`
`
`
`
`
`“:2:ch.Emzicu.25.2025.20
`
`
`
`Om:mm:<w_‘
`
`3.33m
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 10 of 41
`
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 10 0f 21
`
`US 2013/0246258 A1
`
`EIZZZ 1H 335‘ OMBJH
`
`aJ3u.eu11MI.Z0I1—
`
`mcozmuEzEEou83mmszuEton
`
`mcozmuEzEEou
`
`ZSL suoneagunwwog angdJalug lueqmaw
`
`Gown
`
`mmEQnEem3.
`
`
`
`BE.ESEmQ
`
`«5:33:32
`
`
`
`omncozmuEsEEou
`
`“amp
`
`
`
`30.5.0
`
`
`
`womKEmEmmczEé8.53
`
`MNmK
`
`
`
`mmEQQBE:ES
`
`on!iE:
`
`
`
`
`
`Each/fin.Fzm_>_><n_eon.
`
`
`
`
`
`EwE>mn_ 8:99
`Em:262:?538?gDmeEmEmQEEE
`
`
`<®WNumn(VMN(NMN
`3.52mSEE“3thEgccoflmm\EEM‘EmousseSim?5:32
`
`éMacias::33%
`
`
`
`
`
`
`
`EcummumoE2822emuEon—magmaEwum>m«mm2053mm.in:
`
`
`233x9.5chEEUEEEmEmmccu§8.53
`
`PH2&53.3.0ESngmmn
`
`ImmO.‘EOEUGMCCLHWEQQngDEmQ
`
` mmémIUNQ3.23“$358.:
`
`
`w._<Eon_mz_._-zo(h.mu_n_
`
`
`
`
`
`
`
`
`:96...u‘m.__m>>o__po_>_
`
`\mmmhogw-._m>_oomm
`
`:39Don
`
`55050
`
`23maooG
`14fO11e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 11 of 41
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 11 0f 21
`
`US 2013/0246258 A1
`
`ACCOUNT WEB-MGT PORTAL
`
`28 30 32
`
`28A
`
`Enrollment
`
`(web & OMW)
`
`Firewall/Secrity722/41
`
`
`My Cards
`
`My Devices
`
`My Favorites
`
`Accou nt Preferences
`
`Reporting
`
`28C
`
`28D
`
`28E
`
`28
`
`28G
`Mobile Wallet Token Generator
`
`Mobile Wallet Token
`Receiver-Storag e/
`PCD token
`
`generator
`
`PCD PAYMENT
`PLATFORM
`
`(CLOUD)
`
`FIG. 73
`
`
`
`Google LLC v. RFCyber Corp. / Page 12 of 41
`
`6006-1032
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 12 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 12 0f 21
`
`US 2013/0246258 A1
`
`2W2
`
`WELCOME TO YOUR ACCOUNT(S)
`MANAGEMENT WEBPAGE
`
`|:|NO
`
`ACCOUNT #1 (ending in 1234) .............. $2400
`ACOOUNT # 2 (ending in 5678) ............. $10,000
`28F1
`
`/
`USE ACCOUNT #1 FOR MOBILE PAYMENTS?
`I:IYES
`.NO
`/28F2
`
`USE ACCOUNT #2 FOR MOBILE PAYMENTS?
`EYES
`
`FIG. 7C
`
`
`
`Google LLC v. RFCyber Corp. / Page 13 of 41
`
`GOOG-1032
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 13 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 13 0f 21
`
`US 2013/0246258 A1
`
`3100
`
`87
`
`880
`
`08
`
`NFC
`Antenna
`
`Power /
`Supply
`
`840
`
`/
`|
`D'
`'Spay
`I Touchscreen
`_
`'
`
`82:30
`
`Arno.
`
`Audio
`Am.
`
`'
`
`
`
`
`
`
`USB
`
`02
`
`Network
`Card
`
`.14
`
`an
`
`
`
`
`842
`
`803
`
`
`
`888
`
`872
`
`Sw.
`
`870
`
`868
`
`822
`
`83
`
`.
`83
`
`85
`
`Port
`
`Stereo
`
`Stereo
`860 Sneaker
`
`"
`
`85:
`
`A
`
`862
`
`i m'
`FM
`
`
`
`Element "
`
`Transceiver
`
`850
`
`Stereo
`Head hones
`
`86-
`
`Ke
`
`ad
`
`874
`
`Mono
`Headset
`w/ micro.
` 876
`
`—-
`FIG. 8
`
`m
`
`
`
`Google LLC v. RFCyber Corp. / Page 14 of 41
`
`GOOG-1032
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 14 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 14 0f 21
`
`US 2013/0246258 A1
`
`EmanuwQEN.3E2”28
`
`m:”9m0;
`
`82?3:24a22222
`
`25:2ESE
`
`moom
`
`-555Egg:
`
`08;§<22:5
`
`
`
`fi859:85..fimE238
`
`3205:
`
`98E0
`
`392$3%:E22922 (com
`
`mm.0."—
`
`43.0."—
`
`
`
`2%meSow.3E2”28
`
`h:”n:mo;
`
`$9.5295:1
`
`52mm385cozgoenam
`
`326:29:B83%
`
`”285
`
`so3:32mm<
`
`30>x52:
`
`2:82E9531
`
`5:5to$9
`
`22052262
`
`EmoE0gusto3m
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`23maooG
`14fO51egaPla.
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 15 of 41
`
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 15 0f 21
`
`US 2013/0246258 A1
`
`1000A
`
`
`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 payment via a
`PCD
`
`1010
`Encrypt account data
`
`Transmit first authentication
`
`code and encrypted account
`data to merchant enterprise
`system
`
`Encrypt merchant acq.
`token and mobile wallet
`token
`
`Transmit merchant acq. token
`with transaction data to merchant
`
`acquirer and mobile wallet token
`to PCD payment platform (cloud)
`
`Store mobile wallet token and
`
`create PCD token corresponding
`to mobile wallet token
`
`1045
`
`
`
`
`Retransmit encrypted account
`data with a second
`authentication code to vault
`
`Transmit PCD token to PCD for
`future use
`
`Determine if payment for
`
`1050
`
`mobile wallet token
`
`based on merchant acq. Token
`and transaction data
`
`Goto Fig. 10B,
`Step 1055
`
`
`
`FIG. 10A
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 16 of 41
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 16 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 16 0f 21
`
`US 2013/0246258 A1
`
`From Fig. 10B,
`Step 1050
`
`1000B
`
`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 POS for approving
`transaction
`
`FIG. 1OB
`
`
`
`Google LLC v. RFCyber Corp. / Page 17 of 41
`
`GOOG-1032
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 17 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 17 0f 21
`
`US 2013/0246258 A1
`
`11003
`
`Start Method for Using
`Pre-Loaded Merchant Account
`from Vault with a PCD for a
`Transaction
`
`Receive input from POS
`that payment via PCD is
`desired and relay input to
`merchant enterprise
`system
`
`1110
`
`Receive confirmation that
`PCD payment is desired
`
`Receive ID associated with
`
`operator of PCD
`
`Determine if operator ID
`
`matches any accounts in Vault
`
`If match exists, transmit
`message that one or more
`accounts associated with
`
`operator exist in Vault
`
`
`
`
`Step 1160
`
`1 130
`
`Apply tender steering rules
`at PCD payment platform
`(cloud)
`
`
`
`1135
`
`Send payment options to PCD
`
`1140
`
`Receive selection of merchant
`
`account for payment from PCD
`
`1145
`Send PCD token from PCD to
`
`PCD payment platform (cloud)
`
`1150
`Match PCD token with mobile
`wallet token (created by Vault)
`
`1155
`
`Transmit mobile wallet token
`
`(created by Vault) to merchant
`enterprise system
`
`Goto Fig. 118,
`
`FIG. 11A
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 18 of 41
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 18 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 18 0f 21
`
`US 2013/0246258 A1
`
`From Fig. 11A,
`Step 1155
`
`Receive mobile wallet token with
`
`merchant enterprise system (i.e.
`
`retailer payment processor)
`
`1165
`Match mobile wallet token
`with transaction data
`
`Transmit mobile wallet token and
`transaction data to Vault
`
`,
`.
`Match mobile wallet token With
`merchant acq. token
`
`Determine if payment for
`transaction should be authorized
`
`based on merchant acq. Token
`and transaction data
`
`Generate authorization response
`and transmit merchant acq. token
`and response to merchant
`enterprise system
`
`1195
`
`Store response and
`merchant acq. token
`
`
`
`
`
`Transmit merchant acq. Token
`with transaction data to
`merchant acquirer
`
`Transmit authorization response
`
`to merchant P05 for approving
`transaction and to PCD via PCD
`payment platform
`
`FIG. 113
`
`6006-1032
`Google LLC v. RFCyber Corp. / Page 19 of 41
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 19 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 19 0f 21
`
`US 2013/0246258 A1
`
`Start Method for Loading Bank
`Issued Card, Fl Credit Card, or
`
`alternative payment account
`data for PCD payments via a
`secure website
`
`1200
`
`Receive from website a
`
`message for account to be
`used for payments via
`PCD
`
`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
`
`
`
`Google LLC v. RFCyber Corp. / Page 20 of 41
`
`6006-1032
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 20 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 20 0f 21
`
`US 2013/0246258 A1
`
`Start Method for Using
`Pre-Loaded Bank Issued Card,
`FI Credit Card, or alternative
`payment account data with a
`PCD for a Transaction
`
`Receive input from POS
`that payment via PCD is
`desired and relay input to
`merchant enterprise
`system
`
`Receive confirmation that
`PCD payment '3 deSIred
`
`
`
`Receive ID associated with
`
`operator of PCD
`
`Determine if operator ID
`matches any accounts in Vault
`
`If match exists, transmit
`message that one or more
`accounts associated with
`
`operator exist in Vault
`
`1300A
`
`1330
`
`Apply tender steering rules
`at PCD payment platform
`(cloud)
`
`
`
`1335
`
`Send payment options to PCD
`
`1340
`Receive selection of at least one
`of Bank Issued, Fl account, and
`Alternate payment for payment
`from PCD
`
`
`
`1345
`Send PCD token from PCD to
`
`PCD payment platform (cloud)
`
`1350
`Match PCD token with mobile
`wallet token (created by Bank, Fl
`account, or alternative payment
`
`provider)
`
`1355
`
`Transmit mobile wallet token
`
`(created by Vault) to merchant
`enterorise s stem
`
`Goto Fig. 138,
`
`Step 1355
`
`FIG. 13A
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 21 of 41
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 21 of 41
`
`

`

`Patent Application Publication
`
`Sep. 19, 2013 Sheet 21 of 21
`
`US 2013/0246258 A1
`
`From Fig. 130,
`Step 1355
`
`
`
`1 360
`
`13003
`
`Receive mobile wallet token with
`
`merchant enterprise system (Le.
`
`retailer payment processor)
`and transaction data 1365
`
`1380
`
`Determine if payment for
`transaction should be authorized
`based on mobile wallet Token
`
`Match mobile wallet token
`with transaction data
`
`1385
`
`1370
`Transmit mobile wallet token and
`
`Generate authorization response
`and transmit mobile wallet token
`
`transaction data to either
`merchant acquirer or Fl issuer or
`
`and response to merchant
`enterprise system
`
`alternative payment provider
`
`
`_
`actual account in Bank
`database, Fl database, or
`alternative payment provider
`database
`
`Store response and
`mobile wallet token
`
`1390
`
`1395
`
`Transmit authorization response
`to merchant POS for approving
`transaction and to PCD via PCD
`
`payment platform
`
`END
`
`FIG. 133
`
`6006-1032
`Google LLC v. RFCyber Corp. / Page 22 of 41
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 22 of 41
`
`

`

`US 2013/0246258 A1
`
`Sep. 19, 2013
`
`SYSTEM AND lVIETHOD FOR MANAGING
`PAYMENT IN TRANSACTIONS WITH A PCD
`
`
`PRIORITY AND RELATED APPLICATIONS
`STATEMENT
`
`[0001] This patent application claims priority under 35
`U.S.C. §119(e) and is related to US. Provisional Patent
`Application Ser. No. 61/611,344, filed on Mar. 15, 2012,
`entitled, “System and Method For Managing Payment In
`Transactions With A PCD,” the entire contents of which are
`hereby incorporated by reference.
`
`DESCRIPTION OF TI IE 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—
`tal 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, such as credit cards, gift cards, and
`stored value cards, are typically used. One problem faced by
`many consumers is that each consumer may be issued a
`separate account corresponding to a single merchant or single
`service provider. Often, the merchant or service provider will
`send each consumer a physical token that corresponds to the
`
`account. Each physical token typically has account inforrna—
`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 huinan—readable codes as a back—up for
`the machine-readable code if the machine-readable code fails
`for a 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 may be used.
`[0006]
`Physical tokens may also be required by merchants
`or service providers as a form of identification of the con-
`sumer and his or her corresponding account. Often, physical
`tokens may be required by a merchant or service provider so
`that any value associated with the token may be redeemed by
`the consumer.
`
`If a consumer has a plurality ofaccounts, such as on
`[0007]
`the order of five 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. If a consumer has ten or more accounts
`which corresponds to ten or more physical tokens, then the
`management of these physical tokens becomes significantly
`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 of trans-
`
`actions so that a consumer may track one or more accounts
`with merchants and/or service providers with case using a
`single PCD.
`
`SUMMARY OF 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
`in memory within a portable computing device payment plat-
`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 to make a payment. 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 mer-
`chant based card account.
`
`[0010] Each mobile wallet token may be generated in
`response to receiving input from a point—of—sale system that
`future use of a 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 that future 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 offers at
`least two layers of security for credit card or other type of
`payment account data. The mobile wallet tokens and the PCD
`tokens may not 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, gift card accounts, bank accounts, etc.) is only
`known to the account issuing entity, like the altemative 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
`
`In the Figures, like reference numerals refer to like
`[0012]
`parts throughout the various views unless otherwise indi-
`cated. For reference numerals with letter character designa-
`tions such as “102A” or “10213”, the letter character designa-
`tions may differentiate two like parts or elements present in
`the same Figure. Letter character designations for reference
`numerals may be omitted when it is intended that a reference
`numeral to encompass all parts having the same reference
`numeral in all Figures.
`[0013]
`FIG. 1 is a diagram ofa wireless portable computing
`device (“PCD”) coupled to a wireless communications net-
`work which are integral parts of a system for managing pay-
`ment transactions with the portable computing device,
`[0014]
`FIG. 2A is a diagram ofa screen for entering a user’ 5
`log-in credentials on the PCD to access the system;
`[0015]
`FIG. 2B is a diagram of a screen for entering addi—
`tional log-in credentials such as a password on the PCD to
`access the system;
`[0016]
`FIG. 2C is a diagram of a screen for the PCD con-
`firming access to system;
`
`
`
`Google LLC v. RFCyber Corp. / Page 23 of 41
`
`GOOG-1032
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 23 of 41
`
`

`

`US 2013/0246258 A1
`
`Sep. 19, 2013
`
`FIG. 2D is a diagram of a screen that shows the
`[0017]
`contents of an image being scamied with a camera of the
`PCD;
`FIG. 2E is a diagram of a screen that shows mer-
`[0018]
`chant information relevant to a transaction and a line item
`listing of products being scanned by a product scanner
`coupled to an electronic cash register;
`[0019]
`FIG. 2F is a diagram of a screenthat shows merchant
`information relevant to a transaction and a coupon option that
`may be selected by a user;
`[0020]
`FIG. 2G is a diagram of a screen that shows mer—
`chant information relevant to a transaction and a total bill for
`a purchase along with a plurality ofpayment 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 upon completion of a
`transaction with a merchant;
`[0022]
`FIG. 21 is a diagram of an exemplary machine—
`readable tag that may be coupled to an electronic cash register
`of a merchant;
`[0023]
`FIG. 3A is a diagram of hardware components and
`software components running on a portable computing
`device for supporting transactions with the portable comput—
`ing device;
`[0024]
`FIG. 3B is a diagram of several software compo-
`nents for a payment application rumiing on a portable com-
`puting device;
`[0025]
`FIG. 4 is a diagram illustrating 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. 5 is a diagram illustrating details of a merchant
`acquirer and credit card subsystems of FIG. 1 for completing
`a sales transaction;
`[0027]
`FIG. 6 is a diagram illustrating details of a gateway
`and alternative payment systems illustrated in FIG. 1;
`[0028]
`FIG. 7A is diagram illustrating details for the central
`mobile payment controller illustrated in FIG. 1 that assists
`with providing personalized pricing and ensemble sugges-
`tions for the PCD consumer;
`[0029]
`FIG. 7B is a diagram illustrating several on—line
`portals for managing payment accounts according to one
`exemplary embodiment of the invention;
`[0030]
`FIG. 7C is a diagram illustrating an exemplary
`account on—line (web) management portal for generating
`mobile wallet tokens;
`[0031]
`FIG. 8 is a functional block diagram illustrating an
`exemplary portable computing device (“PCD”) that may
`include PCD token storage;
`[0032]
`FIG. 9A is a diagram of a screen 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 tender steering algorithm; and
`[0033]
`FIG. 9B is a diagram of a screen that shows mer-
`chant information relevant to a transaction and a total bill for
`a purchase along with a plurality ofpayment options that may
`be selected by user and which were re—ordered by a tender
`steering algorithm.
`[0034]
`FIGS. IDA-10B are fiowcharts illustrating a method
`for loading merchant card account data into a vault for future
`PCD use with a point-of-sale terminal;
`[0035]
`FIGS. 11A-11B are fiowcharts illustrating a method
`for using a preloaded merchant account from a fault with a
`PCD for completing a payment transaction;
`
`FIG. 12 is a flowchart illustrating a method for load-
`[0036]
`ing bank issued card data, financial institution (“other card
`issuer”) credit card data, or altemative payment account data
`for PCD payments Via a secure online portal (i.e., a website);
`and
`FIGS. 13A-13B are llowcharts illustrating a method
`[0037]
`for using preloaded bank issued card data, financial institu-
`tion (“other card issuer”) 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
`described herein as “exemplary” is not necessarily to be con-
`strued as preferred or advantageous over other aspects.
`[0039]
`In this description, the tem “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 data files 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, software, or soft-
`ware in execution. For 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, a
`program, and/or a computer. By way of illustration, 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/0r distrib—
`uted between two or more computers. In addition, these com-
`ponents may execute from various computer readable media
`having various data structures stored thereon. The compo-
`nents 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.g., data 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 of the signal).
`the terms “communication
`[0042]
`In this description,
`device,” “wireless device,” “wireless telephone,” “wireless
`communication device,” and “wireless handset” are used
`interchangeably. With the advent of third generation (“3G”)
`wireless technology and four generation (“4G”), greater
`bandwidth availability has enabled more portable computing
`devices with a 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] Referring 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 103A which are integral parts of a sys-
`
`
`
`Google LLC v. RFCyber Corp. / Page 24 of 41
`
`GOOG-1032
`
`GOOG-1032
`Google LLC v. RFCyber Corp. / Page 24 of 41
`
`

`

`US 2013/0246258 A1
`
`Li.)
`
`Sep. 19, 2013
`
`tem 101 (also referred to herein as a transaction management
`system 101) for managing transactions 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 RF transceiver towers (not illustrated).
`However, one ofordinary skill in the art recognizes that other
`types of communication devices besides broadcast RF trans-
`ceiver towers are included within the scope of this disclosure
`for establishing the communications network 142.
`[0046] The PCD 100 is shown to have a RF antenna 872
`(see FIG. 8) so that a respective PCD 100 may establish a
`wireless communication link 103A 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) ofthe PCD 100. The PCD 100 may also include PCD
`token storage 1 17 that may be part of and/or in addition to
`memory 803. The PCT) token storage 1 17 may contain PCD
`tokens issued by the PCD payment platform (cloud) 50 as will
`be described in further detail below.
`[0047] The payment application 113 may allow the PCD
`l00 to communicate with the PCT) payment platform 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 t