i) United States
`12) Patent Application Publication (10) Pub. No.: US 2014/0365371 Al
`(43) Pub. Date: Dec. 11, 2014
`
`Ohlhausen
`
`US 20140365371A1
`
`(52) U.S.Cl
`CPC ooeecccccscccsessssesssseesesseeseee G06Q 20/42 (2013.01)
`USPC cesssssssssssssssssssssssssssssissivesssssnsssvusesssseees 705/44
`
`(57)
`
`ABSTRACT
`
`A specially configured computer [or transferring money to a
`merchant, company, or other individual. The computer may
`comprise a barcode receiver configured to receive a copy ofa
`barcode generated by the merchant, a barcode decoder con-
`figured. to decode the barcode information with an applica-
`tion, a data input configured to receive customerinformation
`in an application running on the customer computer, a pay-
`mentinterface configured to presentan interface for transmit-
`ting a bank paymentto the merchant, a transaction informa-
`tion transfer module configured to send the transaction
`information to a bank system, a bank payment initialor con-
`figured to send an instruction to the bank system toinitiate
`paymentusing the bank systemat a first time period; and send
`a confirmation to a payment service provider indicating pay-
`ment was initiated; wherein the confirmation is sent within
`ten minutes of the first time period.
`
`
`
`54)
`
`71)
`72)
`
`73)
`
`21)
`
`22)
`
`86)
`
`
`
`ELECTRONIC PAYMENTSYSTEM
`
`Applicant: Safety Pay, Inc., Miami Beach, FL (US)
`Inventor:
`
`Ralf Ohlhausen, Frankfurt am Main
`(DE)
`
`Assignee: Safety Pay, Inc., Miami Beach, FL (US)
`
`Appl. No.:
`
`14/363,415
`
`PCTFiled:
`
`PCT No.:
`
`
`
`Dee. 7, 2012
`
`PCT/US12/68539
`
`§ 371 (c)(1),
`(2), (4) Date:
`
`Jun. 6, 2014
`
`(60)
`
`Related U.S. Application Data
`Provisional application No. 61/568,911, filed on Dec.
`9, 2011.
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`G06Q 20/42
`
`(2006.01)
`
`amma4¢s4
`
`ene, Cee
`, Relector 210
`
`ests
`T;
`Datastore 240
`
`| Duterrnation 330
`Paanere bnterdace |
`
`Bank Payment 342
`
`GOOG-1008
`Google LLC v. RFCyber Corp./ Page 1 of 17
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 1 of 17
`
`

`

`Patent Application Publication
`
`Dec. 11,2014 Sheet 1 of 5
`
`US 2014/0365371 Al
`
`aEEpOPYmyNY
`
`Soe
`
`nog&
`
`—
`
`PRBLAIOP
`
`IOEI
`
`pause
`
`S27Sp
`
`plesaoe
`
`
`
`
`
`Gg,BREET|
`
`STEsotmouDr
`
`Optmene
`
`ORIETBS
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 2 of 17
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Dec. 11,2014 Sheet 2 of 5
`
`US 2014/0365371 Al
`
`Zaaetg
`
`
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 3 of 17
`
`
`

`

`Patent Application Publication
`
`Dec. 11,2014 Sheet 3 of 5
`
`US 2014/0365371 Al
`
`Semmens BE
`
`
`
`_Oiogoptydonsesun:
`
`cH
`
`
`
`Chirapeseuacy
`
`(pfWore
`
`afed
`
`OG|taeediacy
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 4 of 17
`
`
`
`
`
`

`

`Patent Application Publication
`
`Dec. 11,2014 Sheet 4 of 5
`
`US 2014/0365371 Al
`
`
`
`soaymdergeee]|
`
`Prej
`
`z
`
` a
`
`ABCA
`
`|wonpmarecay|CHIESUBAy
`
`Pagieay
`
`tg3gtizi3
`
`tee
`
`SAYYAS
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 5 of 17
`
`
`
`
`
`

`

`Patent Application Publication
`
`Dec. 11,2014 Sheet 5 of 5
`
`US 2014/0365371 Al
`
`sanmeramnnnsonnoannedOEmenaal1das3
`
`BoeseyEeel2eee.cectumammnsesed
`73gdary)—
`ustaasts
`meee|eeoy1O61dSd
`O21sg|19EeNpABANVEEQniPARED
`aR]BaneFE|peneeeyy|=
`viretpadegay4ida|:eaeiemanaeMILIEULEEDTEEBeyaban1comuneeSOS'Edag{ig|BORE,FoI,ILILIEDETLEDELE
`
`
`
`
`
`PEER}EpoGp]cory
`
`
`psaEHeroesUreL|Optsowpronaywaaring|ieGeneddy
`ETTSES
`
`Gerenyay-_sah
`
`
`
`ASA38vIREIA,
`
`agdawg+agdng
`
`
`
`EPOULYoe)esYe
`
`
`
`Goecsibacesriinsnnuincemrnnineasndby
`
`
`
`
`
`
`
`ghee
`
`
`
`
`
`
`
`astasa||octsendwoymueseyyo,HOTEUNSELROUENasa
`
`yeu
`
`dag
`
`BEdaysSSGoiSeder
`
`
`BEdawguesc
`
`
`
`ryOLLLTTUTENMLLILEEh
`
`
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 6 of 17
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`US 2014/0365371 Al
`
`Dec. 11, 2014
`
`ELECTRONIC PAYMENT SYSTEM
`
`T,
`
`CROSS REFERENC
`
`
`
`
`
`[0001] This application claims the benefit of priority to
`US. Provisional Application, 61/568,911, filed Dec. 9, 2011,
`the contents of which are incorporated by reference in their
`entirety.
`
`BACKGROUND
`
`[0002] This disclosure relates to payment mechanisms for
`delivering paymentto a merchantorotherlegal entity without
`needingto tender a physicalcredit card, check, or cash during,
`the transaction. Rather, a process, computer, and system for
`paying a merchant using a computer such as a smart phoneis
`provided.
`
`SUMMARY
`
`[0003] A method of paying a merchant with a customer
`computeris disclosed. The method may comprise generating
`a barcode comprising a set of transaction information includ-
`ing sales and merchant information to be encoded with a
`merchant computer, generating an invoice comprising the
`barcode with the merchant computer, storing a copyof the
`barcode in the customer computer, entering customerinfor-
`mation into a payment application running on the customer
`computer, decoding the barcode information with the pay-
`ment application, and presenting an interface with three
`options: a) bank payment; b) credit or debit card payment; or
`c) mobile wallet payment.
`[0004] Choosing choice a) bank payment, may cause the
`payment application running on the customer computer to
`send the transaction information to a payment service pro-
`vider, reccive a transaction ID linked with the transaction
`information at the customer computer from the paymentser-
`vice provider, display some transaction information on a dis-
`playofthe customer computer, and provide an interface with
`optionsfor the bank payment: a) manual login; b) automated
`bank payment; or c) direct debit.
`[0005] Choosing choice a) manual login, may cause the
`application to launch a web browser or a bank application on
`the customer computer to access an online or mobile bank
`system. Using the web browseror bank app the customer can
`log into a bank system account ofthe customer. Through the
`web browser or bank app, the customer can transmit the
`transaction information and/or transaction ID to the bank
`systemusing the paymentapp, send the transaction ID to the
`paymentservice provider using the bank system, send some
`transaction information from the paymentservice providerto
`the bank system, display information about the transaction on
`the display ofthe customer computer using the bank system,
`verify and/or amend the transaction, and initiate payment
`using the bank system. The bank system may be configured to
`transfer funds from the customerto the merchant or an inter-
`mediary paymentservice provider using the bank system, and
`send a confirmationnotice to the merchant or the intermedi-
`ary payment service provider. The payment service provider
`may send the confirmation notice to the merchant and/or
`customer, and if applicable may transfer funds minus a ser-
`vice lee [rom the paymentservice provider to the merchant.
`[0006] Choosing choice b) automated bank payment, may
`cause the payment app to launch a web browseror a bank app
`onthe customer computerto access an online or mobile bank
`system associated with the customer, provide the customer
`
`with an interlace lo iniliale payment using the stored and
`gathered customer information and transaction information
`and/or transaction ID, to automatically populate fields and
`transfer funds from a financial accountofthe customerto the
`merchant or an intermediary payment service provider. The
`bank system maybe configured to transfer funds from an
`account of the customer to the merchant or an intermediary
`paymentservice provider using the bank system, and send a
`confirmation notice to the merchantor intermediary payment
`service provider. The payment service provider may send the
`confirmation notice to the merchant and/or customer, and
`transfer funds from the paymentservice provider to the mer-
`chant.
`
`[0007] Choosing choice c) direct debit, maycause the pay-
`ment app to launch a web browseror an application on the
`customer computer providing the customer with an interface
`to initiate payment using the stored and gathered customer
`information and transaction information, send a direct debit
`authorization to the merchant or intermediary paymentser-
`vice providerallowing the debit of funds from the customer’s
`bank account. The merchantor intermediary paymentservice
`provider notifies the debit authorization to the customer’s
`financial institution and requests the transfer of the funds to
`the merchant or intermediary payment service provider: and
`if applicable the payment service provider maytransfer the
`funds to the merchant.
`
`Ifthe customerselects choice b) credit or debit card,
`[0008]
`the application maylaunch a website of the merchant allow-
`ing the customer toinitiate an online or mobile credit card or
`debit card payment by using the merchant’s card payment
`service provider. The payment service provider may execute
`the online or mobile credit card or debit card payment, notify
`the merchant that the customer has initiated funds transfer
`request, and transferring funds from an account of the cus-
`tomer to an account of the merchant and or intermediary
`payment service provider. Once executed, the paymentser-
`vice provider may send the merchant a notice that the funds
`werereceived, and if applicable may transfer the funds minus
`a service fee to an account controlled by the merchant.
`[0009]
`Ifthe customerselects choice c) mobile wallet pay-
`ment, the application may launch a web browser or mobile
`wallet app on the customer computer to access a wallet
`account. The web browser or mobile wallet app may request
`the customer to verify transactions details, and mayrequest
`username and passwordor a pin to authenticate and authorize
`the payment before providing a transfer funds function con-
`figured to transfer funds from a wallet account of the cus-
`tomer to an account of the merchant or an intermediary pay-
`ment service provider.
`[0010]
`In addition to the above processes, a specially con-
`figured computer is set forth herein. The computer may com-
`prise a processorfor executing instructions stored on tangible
`computer readable storage media, tangible computer read-
`able storage media for storing processor instructions. ‘The
`instructions may comprise, a barcode receiver configured to
`receive a copy ofa barcode generated by the merchant, a data
`input contigured ta receive customer information into an
`application running on the customer computer, a barcode
`decoder configured to decade the barcode information with
`the application, a paymentinterface configured to present an
`interface for transmitting a bank paymentto the merchant, a
`transaction information transfer module configured to send
`the transaction information to a payment service provider, a
`transaction ID receiver configured to receive a transaction ID
`
`
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 7 of 17
`
`

`

`US 2014/0365371 Al
`
`Dec. 11, 2014
`
`linked with the transaction information at the customer com-
`puler from the payment service provider, a login interlace
`configured to provide an interface for logging into a bank
`system account ofthe customer, a transaction ID transmitter
`configured to transmit the transaction ID ta the bank system
`using the application, anda bank paymentinitiator configured.
`to initiate payment using the bank system.
`[0011]
`In another configuration, a method ofpaying a mer-
`chant with a customer computer is disclosed. The method
`maycomprise generating a barcode associated with transac-
`tion information to be encoded with a merchant computer;
`receiving a copy of the barcode at the customer computer;
`executing an application on the customer computer to decode
`the barcode information; presenting an interface for transmit-
`ting a bank payment to the merchant; logging into a bank
`system account of a customer;transmitting all ora part ofthe
`transaction information to the bank system using the cus-
`tomer computer; and initiating payment using the bank sys-
`tem ata first lime. Either the bank system lo a payment service
`provider may send a confirmation notice of payment to a
`computer ofthe merchant within ten minutesofthefirst time;
`and transfer funds from the payment service provider to a
`financial account of the merchant. The computerof the mer-
`chant maybethe first computer, or it may be a second com-
`puter such as a smart phone. The merchant mayreccive the
`confirmation notice within a few seconds of transmission.
`[0012]
`In another configuration, a computer for paying a
`merchant is provided. The computer may comprise a proces-
`sor for executing instructions stored on tangible computer
`readable storage media, and tangible computer readable stor-
`age media for storing processorinstructions. The instructions
`may comprise instructions to the processor to generate a
`barcode receiver configured to receive a copy of a barcode
`generated by a computerofthe merchant; a barcode decoder
`configured to decode the barcode information with the appli-
`cation; a data input configured to receive customer informa-
`tion in an application running on the customer computer; a
`paymentinterface configured to presentan interface for trans-
`mitting a bank payment to the merchant; a transaction infor-
`mation transfer module configured to send the transaction
`information to a bank system; anda logininterface configured
`to provide an interface for logging into a bank system account
`ofthe customer. The computer readable media may comprise
`instructions for the processor to generate a bank payment
`initiator configured to send an instruction to the bank system
`to initiate payment using the bank system at a first time
`period; and send an instruction to the bank system to send a
`confirmation to a payment service provider indicating pay-
`ment was initiated; wherein the confirmation is sent within
`(en minules (or in some cases within a fewseconds) ofthe first
`limeperiod. Alternatively, the computer readable media may
`comprise instructions for the processor to generate a bank
`payment initiator configured to send an instruction ta the
`bank system to initiate payment using the bank system at a
`first time period; and send an instructionto the bank system to
`send a confirmation to the merchant indicating payment was
`initiated; wherein the confirmation is sent within ten minutes
`(or in somecase within a few seconds) ofthefirst time period.
`
`BRIEF DESCRIPTION
`
`FIG. 1 is a process flow diagram of the merchant
`[0013]
`computer and the customer computer.
`[0014]
`FIG. 2 is a box diagram of the processes of the
`paymentprocessor.
`
`FIG. 3 is a flow diagram of the payment service
`
`[0015]
`provider.
`FIG. 4 is box diagram ofsomeofthe functions and
`[0016]
`modules ofthe application.
`[0017]
`FIG.45 isa process flow diagram ofthe application,
`merchant computer, customer computer, and the payment
`service provider.
`
`
`
`DETAILED DESCRIPTION
`
`
`[0018] The following disclosed system and methods pro-
`vide equipment, software, instructions, and process flows to
`enable a customerto pay a merchant using a customer com-
`puter. In an exemplary point of sale transaction, a customer
`would approach a merchant who would ring up the sale and
`provide a receipt for the purchase. The receipt may be elec-
`tronically displayed, emailed, faxed, printed, etc. The mer-
`chant’s computer may include a barcode of somesort on the
`receipt comprising information about the merchant and the
`transaction. When considering the scope of “customer” and
`“merchant” these terms should be afforded a meaning
`roughly equivalent to “payor” and “payee”respectively ...a
`merchant being a legal entity intending lo receive a payment
`for a good or service, release ofobligation, satisfaction of
`debt, etc. while a customeris a legal entity intending to pay for
`the same. An exchange between twolegal entilies such as a
`tenant/landlord, lendee/lendor, patient/doctor, passenger/air-
`line, patron/restaurant, restaurant/food service provider, resi-
`dent/IRS, etc. should all be considered a customer/merchant
`pairs.
`FIG. 1 shows a merchant computer 100 comprising
`[0019]
`computer hardware sucha processor 101, memory 102, hard
`drive 103 (or tangible computer readable storage media). The
`merchant computer maybe a desktop, server, laptop, smart
`phoneor other computer device, The merchant may use more
`than one computer, such as a combination of a desktop and a
`smart phone in some configurations. ‘he computer readable
`media (CRM) may comprise specially configured instruc-
`tions (a checkout processor 200) comprising an invoice gen-
`erator 205, merchant data collector 210, a barcode generator
`215, and delivery module 220. The invoice generator 205 may
`requestdata from the computerasto the products, quantities,
`and price ofproducts to be purchased(c.g. “Sales Information
`250”.). Other examples of Sales Information 250 mayinclude
`a sales identification number; numbers and namesofitems in
`sale, price per item, currency,sales tax, date and timeofsale,
`etc. The merchant mayinput these products into a datastore
`240 using a scanner 104 or other technology product recog-
`nition technology. The merchant data collector 210 is config-
`ured to store information about the merchant, i.e. the “Mer-
`chant Information 230” in the computer readable storage
`memory. Merchant Information 230 may include name,
`address, email address, website URLs, bank or other payment
`details of the merchant, Payment Service Provider (PSP)
`details, and/or merchant ID. “'l'ransaction Information 255”
`may include both “Merchant Information 230” and “Sales
`Information 250” or an identifier associated with the Mer-
`chant Information and the Sales Information. The scanner
`104 can place product information into the transaction datas-
`tore 240 which the invoice generator 205 can usc to gencrate
`the sales information 250. Both the Merchant Information
`230 and Sales Information 250 maybe encoded bya barcode
`generator 215 into a barcode 125. The barcode generator may
`create barcodes in a numberofdifferent recognized barcodes
`formats such as the UPC or Matrix (2D) barcode. The check-
`
`
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 8 of 17
`
`

`

`US 2014/0365371 Al
`
`Dec. 11, 2014
`
`also shownin FIG. 5 as processes 8a, 84, and 8crespectively.
`out processor 200 can deliver the invoice and barcodeto the
`‘The bank payment option mayaccess a PSP 150and/or bank
`delivery module which will format the invoice and barcode
`system 180, the credit/debit card option may access a mer-
`into a format suitable for final deliveryto the customer com-
`chant website or app 151, and the mobile wallet option may
`puter. In somecases, the delivery module 220 may comprise
`access a wallet website or app 152. A wallet account is a
`an email module for delivering the invoice and barcode via
`stored value account provided by a wallet service provider.
`email, a fax module for delivering the invoice and barcade via
`Such accounts may haveless features than bank accounts and
`fax, a display module for displaying the invoice and barcode
`ona screen, and a printer module for formatting and deliver-
`wallet providers are more lightly regulated than banks They
`
`ing the invoice and barcodetoaprinter. can be accessed via mobile phones,but often they can also be
`accessed and used by anyinternet-connected device as well as
`[0020] The customer computer 130 may comprise a pro-
`plastic cards, e.g. prepaid cards. In any of the options, the
`cessor 131, memory 132, and tangible computer readable
`customer computer 130 and App may sendvia a transaction
`storage media 133. The CRM maycomprise a paymentappli-
`informationtransfer module 353 (FIG. 4) at least some Trans-
`cation (“the App”) 300 configured to receive the Merchant
`action and/or Customer Information to the merchant or PSP
`and Sales Informationvia a barcode receiver or intake module
`either directly, or by storing such informationintoafile that is
`305, For example, an email client may receive the email with
`then shared by uploading the file through a web browser,
`the barcode. and a data processor may determine the Mer-
`chant Information and Sales Information from the barcode.
`website, or application.
`Of course, barcodes are often used for scanners, so in some
`[0024] Asshownin FIG.3, a PaymentService Provider 150
`embodiments, the email module may deliver the Merchant
`or PSPis a third party computer configuredto receive ‘Trans-
`action Information 255 either from the merchant or the cus-
`Information and Sales Information without encoding it into a
`tomer or both, receive Customer Information 330 from the
`barcode. The email module may employ encryption to pro-
`vide additional securityto the transaction. The customer com-
`customer, generate 405 a transaction ID 410,deliver the trans-
`puter may also comprise an integrated camera or feature a
`action ID 410 to the merchant computer 100 and/or customer
`connected scanner 134 as shown for reading a barcode dis-
`computer 130, store 415 the Transaction Information 255
`played on a display 105 on the merchant computer 100 or
`together with the associated Transaction ID 410, receive 165
`a confirmation from the customer’s financial institution 160
`printed on an invoice 125 bythe printer 120. The App may
`interface with drivers or other software used to control an
`that a paymentto the merchant’s financial institution 170 or to
`the PSP’s financial institution 166 has been initiated. The PSP
`optic device such as a scanner or camera to capture an image
`ofthe barcode. The invoice intake module 305 may comprise
`150 maydeliver 173 a notification to the Merchant Computer
`a barcode decoder 306 (FIG.4) configured to decodethe sales
`100 and/or Customer Computer 130 that the payment was
`and merchantinformation fromthe scanned barcodein order
`initiated. While the customer may interact with a website
`to provide the customer computer with the needed informa-
`hosted by the payment service provider, in some configura-
`tion to effect the payment process.
`tions, the customerwill use an application or a web browserto
`login into 181 a bank system 180 of the customer’s financial
`[0021] The customer computer may be a smart phone, cell
`institution 160. The bank system may receive 182 a transac-
`phone, laptop, tablet, or any mobile or desktop computer.
`tion ID from the Customer Computer 130 and forward 183
`Once the customer computer 130 has determined the Mer-
`chant Information and Sales Information vis-a-vis the invoice
`this transaction I) to the PSP 150. The PSP 150 may return
`184 the transaction information associated to the transaction
`intake module 205, the customer computer can initiate the
`TD to the bank system 180.
`paymentprocess.
`[0025] The customer, the PSP and the merchant may have
`[0022] The App 300 mayfeature a data input 310 for the
`an account with a financial institution 160, 166 and 170. The
`customer to enter and store (either in the computer readable
`financial institutions (160, 166 and 170) can send and receive
`media of the computer 130 or on a networked data store)
`finances through ACH, wire, or other techniques. A “Bank
`various types of “Customer Information” such as a customer
`System 180,’ an application or web portal that a customer can
`ID, name,deliveryand billing address, bank details, account
`access to provide information to the customer’s financial
`number, account access credentials, user name, password,
`institution and/or direct a specific payment to the merchant’s
`pin, other account details, payment preferences, currency
`financial institution 171 or to the PSP’s financialinstitution
`preferences, credit and/or debit card details, card numbers,
`172, maybe provided by the customer’s financialinstitution
`expiry dates, security codes, other paymentdetails, and infor-
`(or third party hosting site) to send and receive information
`mation relating to the customer computer 130. ‘The customer
`between the customer and the customer’s financial institu-
`computer 130 may already comprise stored answers for some
`tion.
`ofthese data fields, and the App 300 may communicate with
`the customer computer to automatically populate some of
`these fields by using a data populator 344 (FIG. 4) that can
`drawdata from the CRM of the customer computer 130.
`[0023] The App may comprise a paymentinterface 340 to
`offer the customer several payment options including a bank
`paymentoption 341, credit or debit card payment option 342,
`ora mobile wallet payment option 343. Ifthe customerselects
`the bank payment option 341, (which may be stored as a
`default option as part of the Customer Information), the App
`will launch the paymentprocessor 350 offering the customer
`three choices 351-353 to pay through his Bank System;
`manuallogin 351, automated bank payment 352,direct debit
`353 (these choices are shown in FIG. 2). These choices are
`
`FIG. 4 showssomeadditional modules/functions of
`[0026]
`the payment application 300. For example,
`the payment
`application may comprise a transaction ID receiver 371 con-
`figured lo receive a transaction TD linked with the transaction
`information at the merchant computer [rom the paymentser-
`vice provider. A launcher 372 may launch a web browseror
`bank application on the customer computer. A logininterface
`373 may provide the customer with a screen for entering Bank
`System information. During login, the customer may transmit
`the transaction ID to the Bank System using a transaction ID
`transmitter 374. A bank paymentinitiator 375 may provide
`the customera button or otherinterface to send an instruction
`to the bank system to: initiate payment using the bank system
`
`
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 9 of 17
`
`

`

`US 2014/0365371 Al
`
`Dec. 11, 2014
`
`Step 7a. Whenselecting the bank payment option,
`[0034]
`ata first ime period; and send a confirmation to a payment
`the transaction information may be sent to the PSP 150 pro-
`service provider indicating payment wasinitiated; wherein
`the confirmation is sent within ten minutes ofthefirst time
`viding this option, who mayassign a transaction ID if not
`period.
`already part ofthe transaction information and may send the
`transaction ID back to the customer computer 130 and App
`
`[0027] FIG.§illustrates a process flow for effecting pay-
`(running on the computer), which may be configured to dis-
`ment to a merchant. The process flow maybe implemented or
`playat least some Transaction Information 505. Depending
`executed in various sequences other than the ones provided.
`on the stored CustomerInformation (in Step 5), theApp may
`Although the sequences are proposed as step 1, step 2, etc.,
`be configured to display the paymentinterface providing the
`some steps may be skipped or repeated, and the arrangement
`customer with the following options for the bank payment:
`of the steps may be changed depending on needs for the
`8a) manual login, 85) automated bank payment,or 8c) direct
`customer application, payment service provider, etc.
`debit.
`[0028]
`Step 1 and 1a. In step 1, a merchant computer 100
`maydetermine transaction information to be added to an
`invoice fromthe products or services for sale. The merchant
`computer 100 may be configured to determine the contents of
`the transaction information to store into the barcode and
`generate the barcode with the barcode generator. In some
`embodiments (Step 1a), the merchant transfers the transac-
`Gion information to a PSP 150, whoassigns a transaction ID to
`the transaction information,stores both transaction ID and the
`corresponding transaction information in their system and
`returns the transaction ID ta the merchant, who mayencadeit
`in additionor instead of the transaction information into the
`barcode. The barcade may be transferred to the Delivery
`Module 220.
`
`Step 74, bypassing Steps 8-13, may be executed
`[0035]
`when option 74) credit or debit card paymentis selected by
`customer through the interface. The customer makes an
`online or mobile credit or debit card payment by using the
`merchant’s website by either providing the card details and
`customer info manually or via the App 300 using stored data
`if available and if necessaryproviding the rest manually. The
`PSP may request authorization of the payment fromthe cus-
`tomer’s financial
`institution (Step 761). The customer’s
`financial institution may check availability of the requested
`amount on the customer’s account, may reserve the amount
`for a set period and may notify the PSP if il authorizes the
`paymentor not (Step 742). If authorized, the PSP may request
`either right awayorat a later stage the customer’s financial
`institutionto transfer the authorized amount fromthe custom-
`er’s account to the merchant or the PSP (Step 743).
`[0036]
`Step 7c, bypassing Steps 8-15, may be executed
`when option c) mobile wallet is selected. The customer makes
`a mobile wallet payment by using a web browser or mobile
`wallet app on the customer computerto access his/her mobile
`wallet account by entering his/her access credentials if nec-
`essary, enter any necessarytransaction information or verify
`and/or amend the stored Transaction Information that may
`have been passed on by the App; and if necessary authorize
`the paymentto the PSP or merchant for example with a PIN,
`before executing it. A mobile wallet paymentis confirmed by
`the wallet provider to the PSP or merchant. The PSP may
`notify (step 16) the merchant whether the payment was suc-
`cessful or not, and ifsuccessful, the fundsare transferred from
`the customer’s mobile wallet to the merchant’s financialinsti-
`tution (Step 7ce1) or to the PSP’s financial institution (Step
`7¢2) through ACHor other electronic transfer mechanism.If
`applicable the PSP may subsequently transfer the payment to
`the merchant (Step 7c3).
`[0037]
`Step 8a, returning back to the step 7a process (bank
`payment), in step 8a (manual login), the customer computer
`is configured to execute a program(such as a web browseror
`a bank app) for accessing the customer’s Bank System 180
`(such as a bank or financial instituGion’s online or mobile
`banking platform). In some embodiments, this program will
`be launched automatically by the App 300.
`[0038]
`Step 84 is selected when the customer selects b)
`automated bank payment 352 in the App (bypassing Steps
`9-13). In this process, the App provides the customer with an
`interface to enter his or her Customer Information 330 or to
`verify and/or amend the stored Customer Information and
`then execute the payment using the Customer Bank System.
`The App then accesses the Bank System, using at least some
`of the CustomerInformation, navigates automaticallyto the
`Bank System’s moneytransfer or payment screen and enters
`automatically the required Transaction and CustomerInfor-
`mation from the previously entered or stored values. Depend-
`
`Step 2 and 2a. In step 2. the Delivery Module 220
`[0029]
`maybe configured to collect necessary information from the
`merchant computer 100 to display or print the barcode. The
`merchant computer 100 maybe configured to direct the deliv-
`ery module to create an output having the TransactionInfor-
`mation encoded within a barcode. The output Gncluding the
`invoice and barcode) may thenbe sent to a Printer 120 (Step
`2) or a Display 105 (Step 2a).
`[0030]
`Step 3 and 3a. The printer 120 prints an invoice
`comprising the harcode (Step 3) or the display 105 displays an
`invoice and/or barcode (Step 3a).
`[0031]
`Step 4. A customer computer 130 can use the “App”
`300 stored in memory and executed by the processor of the
`customer computer to scan the barcode once the image ofthe
`informationis in the memoryof the customer computer. The
`computer can then decode barcode and effect payment. If the
`customer computeris a smart phone, the optic device maybe
`an integrated camera or a connected external camera. The
`customer computer may be connected to at least one of the
`parlicipaling parties in this process via a data network 145.
`‘The data network 145 may comprise standardfixed or mobile
`networking equipment.
`[0032]
`Step 5. The customer mayuse the data input 310 to
`store various types of Customer Information 330 in the Com-
`puter Readable Media 133 of the customer computer.
`[0033]
`Step 6. Using the image captured by the optic device
`135 (or email received by the email client), the customer
`computer 130 decodes the information in the barcode. ‘The
`App 300 maycomprise instructions [rom whichthe processor
`ofthe customer computer can decode the barcode. Once the
`decoded information is obtained, the App 300 maystore the
`Transaction Information into the computer readable media of
`the customer computer 130. The App may offer anc or more
`of the payment options to the customer as shown in FIG.1:
`elements 341-343. Based on the merchant information, which
`is part of the transaction information, there could be several
`providers for each payment option creating a longer list,
`similar to the checkout page of online merchants.
`
`
`
`
`
`GOOG-1008
`Google LLC v. RFCyber Corp. / Page 10 of 17
`
`

`

`US 2014/0365371 Al
`
`Dec. 11, 2014
`
`ing on the bank’s security processes, which vary from bank to
`bank,
`the Customer may have to authorize the payment
`explicitly by entering a code, e.g. a pin or one-time password
`int