US20120150688A1 - Payment service to efficiently enable electronic payment - Google Patents
Payment service to efficiently enable electronic payment Download PDFInfo
- Publication number
- US20120150688A1 US20120150688A1 US13/348,511 US201213348511A US2012150688A1 US 20120150688 A1 US20120150688 A1 US 20120150688A1 US 201213348511 A US201213348511 A US 201213348511A US 2012150688 A1 US2012150688 A1 US 2012150688A1
- Authority
- US
- United States
- Prior art keywords
- merchant
- network address
- reference return
- return network
- payment service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/14—Payment architectures specially adapted for billing systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0609—Buyer or seller confidence or verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0613—Third-party assisted
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0641—Shopping interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/102—Entity profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/102—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for e-commerce
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/16—Implementing security features at a particular protocol layer
- H04L63/168—Implementing security features at a particular protocol layer above the transport layer
Definitions
- Example embodiments relate to a selective interface display system.
- an e-commerce web site is built around a set of web pages that collectively comprise an “merchant.”
- the web pages generally include an electronic catalog of product offered by the merchant (along with prices), and a product selection scheme that often corresponds to a “shopping cart model.”
- Toward the end of a shopping “experience” the customer is presented with one or more pages corresponding to a “check out” or purchase transaction process. At this time, the customer usually is asked to enter payment information, such as a credit card number and billing address.
- all or part of this information may have been stored during a previous visit and is recalled based on user identification, e.g., through a login process.
- the customer is able to finalize the transaction via a confirmation action, such as activating a “confirm purchase” button displayed on a corresponding web page.
- FIG. 1 is an architecture and network flow diagram corresponding to a first scheme for facilitating e-commerce merchant payment via a third-party payment service in accordance with one embodiment the invention
- FIG. 2 is a flowchart illustrating further details of operations performed by the architecture of FIG. 1 during a consumer purchase from an e-commerce site;
- FIG. 3 shows a web page via which merchants are enabled to specify one or more URLs corresponding to web pages to which the consumer is redirected to during a purchase check out process
- FIG. 4 is a schematic diagram illustrating a conventional computer server that is suitable for practicing embodiments of the invention disclosed herein.
- Embodiments of methods and architectures for facilitating electronic payment of goods and services corresponding to on-line purchases are described herein.
- numerous specific details are set forth to provide a thorough understanding of embodiments of the invention.
- One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc.
- well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
- the architectures provide efficient mechanisms for enabling payment of goods and services offered by e-commerce merchants via the payment service on an individual consumer basis.
- the mechanisms enable e-commerce merchants to easily add payment via the service as an option to authorized customers, and seamlessly integrate transactions via the payment service into the merchant's check out process.
- the architecture enables identification of consumers who are authorized to use the payment service without requiring the service to disseminate any customer lists or the like to e-commerce merchants that use the mechanisms.
- the mechanism is facilitated via an application program interface (API) and corresponding cookies relating to the API and use of the payment service.
- API application program interface
- a service cookie is sent to the consumer's computer (and subsequently stored thereon) when the consumer logs into the payment service's website. For example, when a consumer signs up to use the payment service, a service cookie is sent back to the consumer's device (e.g., computer) to be stored on that device by a browser. The cookie is then used to facilitate future transactions via the service. Based on the existence of the service cookie, the service can determine whether the consumer has ever successfully logged into the service website.
- API application program interface
- the service will advise the merchant, via the API, to allow the consumer to use the payment service for a current purchase. Accordingly, the merchant will present a checkout process congruent with the use of the service as a payment option.
- FIG. 1 An architecture and process flow diagram 100 corresponding to one embodiment of the invention is shown in FIG. 1 , while a flowchart further describing the operations performed via the architecture is shown in FIG. 2 .
- the process begins in a block 200 in which the merchant signs an agreement with the payment service to use the payment service API for facilitating consumer payment via the service.
- An administrator or the like at the payment service then enables the merchant for API access.
- the merchant is enabled for API access via an admin tool that is used to administrate user's accounts.
- the merchant specifies a return URL for its website.
- user's of the payment service including merchants, are enabled to provide one or more return URLs for respective sites operated by the merchant via a user profile page hosted by the service, such as depicted in FIG. 3 .
- the merchant simply enters the URL address for each web page that merchant wants the flow to be re-directed from the payment service site, as described below in further detail.
- the final step for enabling use of the API is completed when the merchant incorporates the payment service's API into appropriate web pages on its web site, as depicted by a block 204 .
- These web pages will typically include one or more pages leading to a check out flow for the site.
- the one or more pages are collectively represented by merchant page 1 in FIG. 1 —it will be understood that the provisions discussed below corresponding to merchant page 1 should be included in each of the web pages corresponding to the initial portion of a check out process.
- the merchant and service websites are configured to facilitate consumer payments via the payment service.
- various consumers are enabled to provide payment for products purchased from the merchant via the payment service in the following manner.
- consumer's will access the merchant website via a web-enabled device, such as a Macintosh computer 102 , personal computer (PC) 104 , and laptop 106 depicted in FIG. 1 .
- PC personal computer
- laptop 106 depicted in FIG. 1 .
- these are merely exemplary web-enabled devices that consumer may use, with other devices including but not limited to PDA's, pocket PC's, web-enabled phones, workstations, etc.
- a consumer operating the web-enabled device visits the merchant's website and selects one or more products for purchase, e.g., via “placing” the products in an electronic shopping cart.
- the consumer then initiates the site's check out process by activating an appropriate button displayed on Merchant page 1 , such as a “Check Out” button 108 .
- an appropriate button displayed on Merchant page 1 such as a “Check Out” button 108 .
- a set of operations corresponding to blocks 208 , 210 , 212 , and 214 are performed substantially instantly in a manner that is transparent to the consumer.
- the consumer i.e., the browser on the consumer's device
- merchant page 1 . 3 which comprises a blank page (with regard to visual content).
- Merchant page 1 . 3 is embedded with code to redirect the device's browser to page 1 . 6 hosted by the payment service.
- information identifying the merchant i.e., a merchant ID
- the browser is redirected to the service's server using a URL having the following format:
- the service server Upon receiving the merchant ID, the service server checks its user profile data to verify that the merchant is enabled for API use in block 210 .
- data embedded in the foregoing URL format provides a built-in security measure, wherein the MID and URL values are checked against user profile information for the merchant to authenticate the request. Accordingly, if the merchant decides to rename its “page 2 ” URL, the merchant will need to update the corresponding URL entered in the user profile above in connection with block 202 and FIG. 3 . If the merchant is not enabled, an indicator is sent back to the merchant server indicating such via the reply discussed below.
- a CGI (common gateway interface) command is executed on the service's server to interpret the consumer's service cookie.
- the browser on the consumer's device automatically forwards a copy of the cookie back to the service server.
- This is a process that is automatically performed by modern browser's that support cookies in response to being directed to a website that issued the cookie, and does not require any modification on the client (i.e., consumer device) side.
- a cookie is merely a pas of text that a web server sends to a client (e.g., a browser running on the consumer's device) to have stored on the client for subsequent use.
- Each cookie contains information comprising name-value pairs that may be used by the issuing web site during subsequent interactions with the site to transfer information to the site without requiring any action by the user. Typically, such information includes user ID's and the like.
- the CGI command redirects the browser back to the merchant's web server to merchant page 2 , which begins the augmented check out flow.
- a reply is passed to the server (e.g., embedded as a variable in a pre-formatted URL in one embodiment) that indicates whether or not the consumer is authorized to use the payment service.
- respective reply variable values are also used to indicate an authentication failure and a cookie cannot be interpreted.
- the merchant server extracts the reply variable passed from service page 1 . 6 and dynamically changes the flow of the check out process beginning at merchant page 2 . For example, if a cookie is not received from the consumer's device, the consumer is not authorized to use the payment service. Accordingly, the reply will indicate such, and the portion of the check out flow beginning with merchant page 2 will continue with a check out process that doesn't present the consumer with an option to pay via the payment service. In contrast, if the reply indicates the consumer is an authorized user, the merchant page 2 will lead to one or more subsequent pages (not shown) that will enable the user to pay for the purchase via the payment service. Typically, these pages will be coded by the merchant to fit the particular check-out process preferred by the merchant.
- the checkout process will perform a behind-the-scenes interaction with the payment service to complete a payment transaction in response to a consumer's authorization to pay for the product using the payment service. Further details of this process are known in the art, and, as such, are not disclosed herein.
- the foregoing scheme provides an efficient mechanism for enabling e-commerce merchants to offer purchase payments via third-party payment services. This is advantageous to both the merchant and consumers.
- the cost associated with credit card transactions fees are eliminated for most payment service transactions.
- payments issued by the payment services are trustworthy. Consumers also enjoy the benefit of being able to purchase products on-line in a secure manner that doesn't require disclosure of credit card information, or even require the consumer to possess a credit card.
- a generally conventional computer server 400 is illustrated, which is suitable for use in connection with practicing the embodiments of the present invention discussed above.
- computer server 400 may be used for running software modules and components on the merchant web server and service server to facilitate the operations in the flow diagrams and flowcharts discussed above.
- Examples of computer systems that may be suitable for these purposes include stand-alone and enterprise-class servers operating UNIX-based and LINUX-based operating systems, as well as servers running the Windows NT or Windows 2000 Server operating systems.
- Computer server 400 includes a chassis 402 in which is mounted a motherboard 404 populated with appropriate integrated circuits, including one or more processors 406 and memory (e.g., DIMMs or SIMMs) 408 , as is generally well known to those skilled in the art.
- a monitor 410 is included for displaying graphics and text generated by software programs and program modules that are run by the computer server.
- a mouse 412 (or other pointing device) may be connected to a serial port (or to a bus port or USB port) on the rear of chassis 402 , and signals from mouse 412 are conveyed to the motherboard to control a cursor on the display and to select text, menu options, and graphic components displayed on monitor 410 by software programs and modules executing on the computer.
- Computer server 400 also includes a network interface card (NIC) 416 , or equivalent circuitry built into the motherboard to enable the server to send and receive data via a network 418 , such as the Internet, enabling the server to be connected to the world-wide web.
- NIC network interface card
- File system storage for storing server-side data may be implemented via a plurality of hard disks 420 that are stored internally within chassis 402 , and/or via a plurality of hard disks that are stored in an external disk array 422 that may be accessed via a SCSI card 424 or equivalent SCSI circuitry built into the motherboard.
- disk array 422 may be accessed using a Fibre Channel link using an appropriate Fibre Channel interface card (not shown) or built-in circuitry.
- Other hard disk interfaces may also be used.
- Computer server 400 generally may include a compact disk-read only memory (CD-ROM) drive 426 into which a CD-ROM disk may be inserted so that executable files and data on the disk can be read for transfer into memory 408 and/or into storage on hard disk 420 .
- a floppy drive 428 may be provided for such purposes.
- Other mass memory storage devices such as an optical recorded medium or DVD drive may also be included.
- the machine instructions comprising the software components that cause processor(s) 406 to implement the operations of the embodiments discussed above will typically be distributed on floppy disks 430 or CD-ROMs 432 (or other memory media) and stored in one or more hard disks 420 until loaded into memory 408 for execution by processor(s) 406 .
- the machine instructions may be loaded via network 418 as a carrier wave file.
- embodiments of this invention may be used as or to support a software program executed upon some form of processing core (such as the CPU of a computer) or otherwise implemented or realized upon or within a machine-readable medium.
- a machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer).
- a machine-readable medium can include such as a read only memory (ROM); a random access memory (RAM); a magnetic disk storage media; an optical storage media; and a flash memory device, etc.
- a machine-readable medium can include propagated signals such as electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.).
Abstract
A method comprising communicating a web page, over a network, to a merchant server associated with a merchant. The web page includes a plurality of input mechanisms for receiving a plurality of reference return network addresses. The method further comprises receiving a first reference return network address, over a network, from the merchant, the first reference return network address being received at the payment service server, the first reference return network address identifying an interface that is hosted by a first merchant web site that is operated by the merchant and being utilized as a first landing page to which the consumer user is redirected to by the payment server to execute a transaction between the consumer user and the merchant. Finally, the method comprises storing the first reference return network address at the payment service server in user profile information that is associated with the merchant.
Description
- This application is a continuation application which claims the priority benefit of U.S. application Ser. No. 13/160,316, filed Jun. 14, 2011, entitled “PAYMENT SERVICE TO EFFICIENTLY ENABLE ELECTRONIC PAYMENT,” which is a continuation that claims the priority benefit of U.S. application Ser. No. 12/198,664 filed Aug. 26, 2008, entitled “PAYMENT SERVICE,” which is a continuation that claims the priority benefit of U.S. application Ser. No. 10/749,684, filed Dec. 31, 2003, issued as U.S. Pat. No. 7,457,778 on Nov. 25, 2008 and, entitled “METHOD AND ARCHITECTURE FOR FACILITATING PAYMENT TO E-COMMERCE MERCHANTS VIA A PAYMENT SERVICE,” which claims the priority benefit of U.S. Provisional Application No. 60/456,504, filed on Mar. 21, 2003, entitled “METHOD AND ARCHITECTURE FOR FACILITATING PAYMENT TO E-COMMERCE MERCHANTS VIA A PAYMENT SERVICE,” which priority benefit is also claimed, and each of which is incorporated herein in its entirety.
- Example embodiments relate to a selective interface display system.
- The past decade has seen a tremendous growth in the use of the world-wide web for online purchases of products and services. Such products are available via web sites provided by e-commerce merchants, such as electronic retailers. Typically, an e-commerce web site is built around a set of web pages that collectively comprise an “merchant.” The web pages generally include an electronic catalog of product offered by the merchant (along with prices), and a product selection scheme that often corresponds to a “shopping cart model.” Toward the end of a shopping “experience” the customer is presented with one or more pages corresponding to a “check out” or purchase transaction process. At this time, the customer usually is asked to enter payment information, such as a credit card number and billing address. In some instances, all or part of this information may have been stored during a previous visit and is recalled based on user identification, e.g., through a login process. After the payment information is entered, the customer is able to finalize the transaction via a confirmation action, such as activating a “confirm purchase” button displayed on a corresponding web page.
- In most instances, the only payment mechanism offered by e-commerce merchants for retail customers is via credit cards. There are many reasons for this, including increasing the likelihood of receiving payment for the goods, fraud protection, and accounting simplicity. However, credit card payments do not come without a cost. On the merchant side, a transaction fee is subtracted by the credit card operator (e.g., bank) that typically includes a base amount plus a second amount based on a percentage of the overall purchase price (e.g., 1.5-2%). This leads to significant costs for larger merchants. From the consumer's perspective, there are also many drawbacks pertaining to credit card payments. Many consumers are weary about entering credit card information on-line, and thus may not make purchases from e-commerce merchants. Furthermore, many consumers prefer not to use credit cards for purchases, or do not have any credit cards to begin with. Accordingly, it would be advantageous to provide an alternative payment mechanism for both e-commerce merchants and consumers. Ideally, such an alternative payment mechanism should be easy to implement using existing network infrastructure.
- The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein like reference numerals refer to like parts throughout the various views unless otherwise specified:
-
FIG. 1 is an architecture and network flow diagram corresponding to a first scheme for facilitating e-commerce merchant payment via a third-party payment service in accordance with one embodiment the invention; -
FIG. 2 is a flowchart illustrating further details of operations performed by the architecture ofFIG. 1 during a consumer purchase from an e-commerce site; -
FIG. 3 shows a web page via which merchants are enabled to specify one or more URLs corresponding to web pages to which the consumer is redirected to during a purchase check out process; and -
FIG. 4 is a schematic diagram illustrating a conventional computer server that is suitable for practicing embodiments of the invention disclosed herein. - Embodiments of methods and architectures for facilitating electronic payment of goods and services corresponding to on-line purchases are described herein. In the following description, numerous specific details are set forth to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
- Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
- In accordance with aspects of the present invention, methods and architectures are disclosed herein for facilitating payment of goods and services via a third-party electronic payment service (i.e., the “payment service” or simply “service”). More particularly, the architectures provide efficient mechanisms for enabling payment of goods and services offered by e-commerce merchants via the payment service on an individual consumer basis. The mechanisms enable e-commerce merchants to easily add payment via the service as an option to authorized customers, and seamlessly integrate transactions via the payment service into the merchant's check out process. Furthermore, the architecture enables identification of consumers who are authorized to use the payment service without requiring the service to disseminate any customer lists or the like to e-commerce merchants that use the mechanisms.
- In one embodiment, the mechanism is facilitated via an application program interface (API) and corresponding cookies relating to the API and use of the payment service. A service cookie is sent to the consumer's computer (and subsequently stored thereon) when the consumer logs into the payment service's website. For example, when a consumer signs up to use the payment service, a service cookie is sent back to the consumer's device (e.g., computer) to be stored on that device by a browser. The cookie is then used to facilitate future transactions via the service. Based on the existence of the service cookie, the service can determine whether the consumer has ever successfully logged into the service website. If an appropriate cookie has been sent to the consumer (actually the device), indicating the consumer is authorized to use the service, the service will advise the merchant, via the API, to allow the consumer to use the payment service for a current purchase. Accordingly, the merchant will present a checkout process congruent with the use of the service as a payment option.
- An architecture and process flow diagram 100 corresponding to one embodiment of the invention is shown in
FIG. 1 , while a flowchart further describing the operations performed via the architecture is shown inFIG. 2 . The process begins in ablock 200 in which the merchant signs an agreement with the payment service to use the payment service API for facilitating consumer payment via the service. An administrator or the like at the payment service then enables the merchant for API access. In one embodiment the merchant is enabled for API access via an admin tool that is used to administrate user's accounts. - Next, in a
block 202, the merchant specifies a return URL for its website. In one embodiment user's of the payment service, including merchants, are enabled to provide one or more return URLs for respective sites operated by the merchant via a user profile page hosted by the service, such as depicted inFIG. 3 . The merchant simply enters the URL address for each web page that merchant wants the flow to be re-directed from the payment service site, as described below in further detail. - The final step for enabling use of the API is completed when the merchant incorporates the payment service's API into appropriate web pages on its web site, as depicted by a
block 204. These web pages will typically include one or more pages leading to a check out flow for the site. The one or more pages are collectively represented bymerchant page 1 in FIG. 1—it will be understood that the provisions discussed below corresponding tomerchant page 1 should be included in each of the web pages corresponding to the initial portion of a check out process. At this point, the merchant and service websites are configured to facilitate consumer payments via the payment service. - During subsequent ongoing operations, various consumers are enabled to provide payment for products purchased from the merchant via the payment service in the following manner. Generally, consumer's will access the merchant website via a web-enabled device, such as a Macintosh
computer 102, personal computer (PC) 104, andlaptop 106 depicted inFIG. 1 . It is noted that these are merely exemplary web-enabled devices that consumer may use, with other devices including but not limited to PDA's, pocket PC's, web-enabled phones, workstations, etc. For clarity, augmentations to the network architecture for supporting non-HTML browsers, such as the micro-browsers used in PDA's and web-enabled phones, are not shown or discussed herein; infrastructure for extending web access to such devices are well-known in the art. - Continuing in a block 206, a consumer operating the web-enabled device, visits the merchant's website and selects one or more products for purchase, e.g., via “placing” the products in an electronic shopping cart. The consumer then initiates the site's check out process by activating an appropriate button displayed on
Merchant page 1, such as a “Check Out”button 108. In response, a set of operations corresponding toblocks - First, in
block 208 the consumer (i.e., the browser on the consumer's device) is directed to merchant page 1.3, which comprises a blank page (with regard to visual content). Merchant page 1.3 is embedded with code to redirect the device's browser to page 1.6 hosted by the payment service. During this operation, information identifying the merchant (i.e., a merchant ID) is passed from the merchant's web server to the service's server. For example, in one embodiment, the browser is redirected to the service's server using a URL having the following format: -
https://<service_web_address>/cgi-bin/webscr?cmd=_user-check&MID= X@Y.com&URL=http://www.Y.com/cgi-bin/checkoutpg2
where <service_web_address> is the address for the payment service's home page, and “MID” is the merchant ID with the payment service, which in the current example comprises a primary email address (X@Y.com) of the merchant. “URL” is the return URL of the web page to where the consumer user is to be redirected to. - Upon receiving the merchant ID, the service server checks its user profile data to verify that the merchant is enabled for API use in block 210. In one embodiment, data embedded in the foregoing URL format provides a built-in security measure, wherein the MID and URL values are checked against user profile information for the merchant to authenticate the request. Accordingly, if the merchant decides to rename its “
page 2” URL, the merchant will need to update the corresponding URL entered in the user profile above in connection withblock 202 andFIG. 3 . If the merchant is not enabled, an indicator is sent back to the merchant server indicating such via the reply discussed below. - Upon verifying that the merchant is enabled for API use, a CGI (common gateway interface) command (script) is executed on the service's server to interpret the consumer's service cookie. In conjunction with the redirect to service URL above, the browser on the consumer's device automatically forwards a copy of the cookie back to the service server. This is a process that is automatically performed by modern browser's that support cookies in response to being directed to a website that issued the cookie, and does not require any modification on the client (i.e., consumer device) side. In essence, a cookie is merely a pied of text that a web server sends to a client (e.g., a browser running on the consumer's device) to have stored on the client for subsequent use. Each cookie contains information comprising name-value pairs that may be used by the issuing web site during subsequent interactions with the site to transfer information to the site without requiring any action by the user. Typically, such information includes user ID's and the like.
- Based on the merchant's return URL, the CGI command redirects the browser back to the merchant's web server to
merchant page 2, which begins the augmented check out flow. In conjunction with this, a reply is passed to the server (e.g., embedded as a variable in a pre-formatted URL in one embodiment) that indicates whether or not the consumer is authorized to use the payment service. In one embodiment respective reply variable values are also used to indicate an authentication failure and a cookie cannot be interpreted. - The merchant server extracts the reply variable passed from service page 1.6 and dynamically changes the flow of the check out process beginning at
merchant page 2. For example, if a cookie is not received from the consumer's device, the consumer is not authorized to use the payment service. Accordingly, the reply will indicate such, and the portion of the check out flow beginning withmerchant page 2 will continue with a check out process that doesn't present the consumer with an option to pay via the payment service. In contrast, if the reply indicates the consumer is an authorized user, themerchant page 2 will lead to one or more subsequent pages (not shown) that will enable the user to pay for the purchase via the payment service. Typically, these pages will be coded by the merchant to fit the particular check-out process preferred by the merchant. Generally, the checkout process will perform a behind-the-scenes interaction with the payment service to complete a payment transaction in response to a consumer's authorization to pay for the product using the payment service. Further details of this process are known in the art, and, as such, are not disclosed herein. - The foregoing scheme provides an efficient mechanism for enabling e-commerce merchants to offer purchase payments via third-party payment services. This is advantageous to both the merchant and consumers. The cost associated with credit card transactions fees are eliminated for most payment service transactions. Like credit cards, payments issued by the payment services are trustworthy. Consumers also enjoy the benefit of being able to purchase products on-line in a secure manner that doesn't require disclosure of credit card information, or even require the consumer to possess a credit card.
- With reference to
FIG. 4 , a generallyconventional computer server 400 is illustrated, which is suitable for use in connection with practicing the embodiments of the present invention discussed above. For example,computer server 400 may be used for running software modules and components on the merchant web server and service server to facilitate the operations in the flow diagrams and flowcharts discussed above. Examples of computer systems that may be suitable for these purposes include stand-alone and enterprise-class servers operating UNIX-based and LINUX-based operating systems, as well as servers running the Windows NT or Windows 2000 Server operating systems. -
Computer server 400 includes achassis 402 in which is mounted amotherboard 404 populated with appropriate integrated circuits, including one ormore processors 406 and memory (e.g., DIMMs or SIMMs) 408, as is generally well known to those skilled in the art. Amonitor 410 is included for displaying graphics and text generated by software programs and program modules that are run by the computer server. A mouse 412 (or other pointing device) may be connected to a serial port (or to a bus port or USB port) on the rear ofchassis 402, and signals frommouse 412 are conveyed to the motherboard to control a cursor on the display and to select text, menu options, and graphic components displayed onmonitor 410 by software programs and modules executing on the computer. In addition, akeyboard 414 is coupled to the motherboard for user entry of text and commands that affect the running of software programs executing on the computer.Computer server 400 also includes a network interface card (NIC) 416, or equivalent circuitry built into the motherboard to enable the server to send and receive data via anetwork 418, such as the Internet, enabling the server to be connected to the world-wide web. - File system storage for storing server-side data, such as user profiles, electronic catalogs, CGI scripts, etc. may be implemented via a plurality of
hard disks 420 that are stored internally withinchassis 402, and/or via a plurality of hard disks that are stored in anexternal disk array 422 that may be accessed via aSCSI card 424 or equivalent SCSI circuitry built into the motherboard. Optionally,disk array 422 may be accessed using a Fibre Channel link using an appropriate Fibre Channel interface card (not shown) or built-in circuitry. Other hard disk interfaces may also be used. -
Computer server 400 generally may include a compact disk-read only memory (CD-ROM) drive 426 into which a CD-ROM disk may be inserted so that executable files and data on the disk can be read for transfer intomemory 408 and/or into storage onhard disk 420. Similarly, afloppy drive 428 may be provided for such purposes. Other mass memory storage devices such as an optical recorded medium or DVD drive may also be included. The machine instructions comprising the software components that cause processor(s) 406 to implement the operations of the embodiments discussed above will typically be distributed onfloppy disks 430 or CD-ROMs 432 (or other memory media) and stored in one or morehard disks 420 until loaded intomemory 408 for execution by processor(s) 406. Optionally, the machine instructions may be loaded vianetwork 418 as a carrier wave file. - Thus, embodiments of this invention may be used as or to support a software program executed upon some form of processing core (such as the CPU of a computer) or otherwise implemented or realized upon or within a machine-readable medium. A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium can include such as a read only memory (ROM); a random access memory (RAM); a magnetic disk storage media; an optical storage media; and a flash memory device, etc. In addition, a machine-readable medium can include propagated signals such as electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.).
- The above description of illustrated embodiments of the invention, including what is described in the Abstract, is not intended to be exhaustive or to limit the invention to the precise forms disclosed. While specific embodiments of, and examples for, the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize.
- These modifications can be made to the invention in light of the above detailed description. The terms used in the following claims should not be construed to limit the invention to the specific embodiments disclosed in the specification and the claims. Rather, the scope of the invention is to be determined entirely by the following claims, which are to be construed in accordance with established doctrines of claim interpretation.
Claims (20)
1. A method comprising:
communicating a web page, over a network, to a merchant server associated with a merchant, the web page including a plurality of input mechanisms for receiving a plurality of reference return network addresses;
receiving a first reference return network address, over a network, from a merchant, the first reference return network address being received at a payment service server, the first reference return network address identifying an interface that is hosted by a first merchant web site that is operated by the merchant and being utilized as a first landing page to which a consumer user is redirected to by the payment server to execute a transaction between the consumer user and the merchant; and
storing the first reference return network address at the payment service server in user profile information that is associated with the merchant.
2. The method of claim 1 , further comprising receiving a cookie and merchant information, over the network, from a browser that is associated with the consumer user, the merchant information identifying the merchant and the cookie identifying the consumer user.
3. The method of claim 2 , wherein the merchant information includes a merchant identifier (MID) that identifies the merchant.
4. The method of claim 3 , wherein the MID includes an email address.
5. The method of claim 2 , wherein the receiving the merchant information includes receiving a return network address that identifies the interface hosted by the first merchant web site.
6. The method of claim 1 , further comprising:
receiving a second reference return network address, over the network, from the merchant, the second reference return network address being received at the payment service server, the second reference return network address identifying a second interface hosted by a second merchant web site that is operated by the merchant.
7. The method of claim 6 , wherein the second interface hosted by the second merchant web site is a second landing page to which the consumer user is redirected to by the payment service server to execute a transaction between the consumer user and the merchant.
8. The method of claim 1 , wherein the plurality of input mechanisms includes a first input mechanism, wherein the first input mechanism is utilized to receive the first reference return network address.
9. The method of claim 1 , wherein the plurality of input mechanisms includes a second input mechanism, wherein the second input mechanism is utilized to receive the second reference return network address.
10. The method of claim 1 , further comprising communicating a reply that includes an authorization to use the payment service server.
11. A non-transitory machine readable medium that stores instructions that, when executed by a machine, cause the machine to:
communicate a web page, over a network, to a merchant server associated with a merchant, the web page includes a plurality of input mechanisms to receive a plurality of reference return network addresses;
receive a first reference return network address, over a network, from a merchant, the first reference return network address is received at a payment service server, the first reference return network address identifies an interface that is hosted by a first merchant web site that is operated by the merchant and is utilized as a first landing page to which a consumer user is redirected to by the payment server to execute a transaction between the consumer user and the merchant; and
store the first reference return network address at the payment service server in user profile information that is associated with the merchant.
12. The non-transitory machine readable medium of claim 11 , wherein the machine receives a cookie and merchant information, over the network, from a browser that is associated with the consumer user, the merchant information identifies the merchant and the cookie identifies the consumer user.
13. The non-transitory machine readable medium of claim 12 , wherein the merchant information includes a merchant identifier (MID) that identifies the merchant.
14. The non-transitory machine readable medium of claim 13 , wherein the MID includes an email address.
15. The non-transitory machine readable medium of claim 12 , wherein the machine receives a return network address that identifies the interface hosted by the first merchant web site.
16. The non-transitory machine readable medium of claim 11 , wherein the machine receives a second reference return network address, over the network, from the merchant, the second reference return network address is received at the payment service server, the second reference return network address identifies a second interface hosted by a second merchant web site that is operated by the merchant.
17. The non-transitory machine readable medium of claim 16 , wherein the second interface hosted by the second merchant web site is a second landing page to which the consumer user is redirected to by the payment service server to execute a transaction between the consumer user and the merchant.
18. The computer implemented non-transitory machine readable medium of claim 11 , wherein the plurality of input mechanisms includes a first input mechanism, wherein the first input mechanism is utilized to receive the first reference return network address.
19. The computer implemented non-transitory machine readable medium of claim 11 , wherein the plurality of input mechanisms includes a second input mechanism, wherein the second input mechanism is utilized to receive the second reference return network address.
20. The computer implemented method of claim 11 , wherein the machine communicates a reply that includes an authorization to use the payment service server.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/348,511 US20120150688A1 (en) | 2003-03-21 | 2012-01-11 | Payment service to efficiently enable electronic payment |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US45650403P | 2003-03-21 | 2003-03-21 | |
US10/749,684 US7457778B2 (en) | 2003-03-21 | 2003-12-31 | Method and architecture for facilitating payment to e-commerce merchants via a payment service |
US12/198,664 US20080313053A1 (en) | 2003-03-21 | 2008-08-26 | Payment service |
US13/160,316 US8112353B2 (en) | 2003-03-21 | 2011-06-14 | Payment service to efficiently enable electronic payment |
US13/348,511 US20120150688A1 (en) | 2003-03-21 | 2012-01-11 | Payment service to efficiently enable electronic payment |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/160,316 Continuation US8112353B2 (en) | 2003-03-21 | 2011-06-14 | Payment service to efficiently enable electronic payment |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120150688A1 true US20120150688A1 (en) | 2012-06-14 |
Family
ID=33101249
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/749,684 Active 2026-01-17 US7457778B2 (en) | 2003-03-21 | 2003-12-31 | Method and architecture for facilitating payment to e-commerce merchants via a payment service |
US12/198,664 Abandoned US20080313053A1 (en) | 2003-03-21 | 2008-08-26 | Payment service |
US12/416,082 Expired - Lifetime US7831510B2 (en) | 2003-03-21 | 2009-03-31 | Payment service to efficiently enable electronic payment |
US12/871,766 Expired - Lifetime US7930247B2 (en) | 2003-03-21 | 2010-08-30 | Payment service to efficiently enable electronic payment |
US13/160,316 Expired - Fee Related US8112353B2 (en) | 2003-03-21 | 2011-06-14 | Payment service to efficiently enable electronic payment |
US13/348,511 Abandoned US20120150688A1 (en) | 2003-03-21 | 2012-01-11 | Payment service to efficiently enable electronic payment |
Family Applications Before (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/749,684 Active 2026-01-17 US7457778B2 (en) | 2003-03-21 | 2003-12-31 | Method and architecture for facilitating payment to e-commerce merchants via a payment service |
US12/198,664 Abandoned US20080313053A1 (en) | 2003-03-21 | 2008-08-26 | Payment service |
US12/416,082 Expired - Lifetime US7831510B2 (en) | 2003-03-21 | 2009-03-31 | Payment service to efficiently enable electronic payment |
US12/871,766 Expired - Lifetime US7930247B2 (en) | 2003-03-21 | 2010-08-30 | Payment service to efficiently enable electronic payment |
US13/160,316 Expired - Fee Related US8112353B2 (en) | 2003-03-21 | 2011-06-14 | Payment service to efficiently enable electronic payment |
Country Status (4)
Country | Link |
---|---|
US (6) | US7457778B2 (en) |
EP (3) | EP1609104B1 (en) |
CN (1) | CN102880954B (en) |
WO (1) | WO2004086190A2 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080313053A1 (en) * | 2003-03-21 | 2008-12-18 | Ebay Inc. | Payment service |
US20170256003A1 (en) * | 2014-03-31 | 2017-09-07 | Monticello Enterprises, Llc | System and method for providing a payment handler api and a browser payment request api for processing a payment |
WO2017189917A1 (en) | 2016-04-28 | 2017-11-02 | Paypal, Inc. | User authentication using a browser cookie shared between a browser and an application |
US10432667B2 (en) * | 2015-08-27 | 2019-10-01 | Mastercard International Incorporated | Systems and methods for monitoring computer authentication procedures |
US20200097959A1 (en) * | 2018-09-21 | 2020-03-26 | Mastercard International Incorporated | Payment transaction process employing dynamic account expiry and dynamic token verification code |
Families Citing this family (88)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8077040B2 (en) | 2000-01-24 | 2011-12-13 | Nextreme, Llc | RF-enabled pallet |
KR100670058B1 (en) * | 2000-03-30 | 2007-01-16 | 삼성전자주식회사 | A liquid crystal display |
US7567937B2 (en) * | 2001-01-17 | 2009-07-28 | Xprt Ventures, Llc | System and method for automatically effecting payment for a user of an electronic auction system |
US7610244B2 (en) * | 2001-01-17 | 2009-10-27 | Xprt Ventures, Llc | System and method for effecting payment for an item offered for an electronic auction sale |
US7483856B2 (en) * | 2001-01-17 | 2009-01-27 | Xprt Ventures, Llc | System and method for effecting payment for an electronic auction commerce transaction |
US7627528B2 (en) | 2001-01-17 | 2009-12-01 | Xprt Ventures, Llc | System and method for effecting a real-time payment for an item won on an electronic auction |
US7606925B2 (en) * | 2003-09-02 | 2009-10-20 | Microsoft Corporation | Video delivery workflow |
US7562045B2 (en) * | 2003-11-18 | 2009-07-14 | Bgc Partners, Inc. | System and method for managing relationships between brokers and traders |
US7860749B2 (en) | 2004-04-16 | 2010-12-28 | Sap Ag | Method, medium and system for customizable homepages for network-based auctions |
US7788160B2 (en) | 2004-04-16 | 2010-08-31 | Sap Ag | Method and system for configurable options in enhanced network-based auctions |
US7877313B2 (en) * | 2004-04-16 | 2011-01-25 | Sap Ag | Method and system for a failure recovery framework for interfacing with network-based auctions |
US20050234804A1 (en) * | 2004-04-16 | 2005-10-20 | Yue Fang | Method and system for auto-mapping to network-based auctions |
US8326764B1 (en) * | 2004-09-30 | 2012-12-04 | Rockwell Automation Technologies, Inc. | Factory automation transactions |
US20060248009A1 (en) * | 2005-05-02 | 2006-11-02 | Hicks Sydney S | System and method for processing electronic payments |
US7774402B2 (en) | 2005-06-29 | 2010-08-10 | Visa U.S.A. | Adaptive gateway for switching transactions and data on unreliable networks using context-based rules |
US7895115B2 (en) | 2005-10-31 | 2011-02-22 | Sap Ag | Method and system for implementing multiple auctions for a product on a seller's E-commerce site |
US8095428B2 (en) | 2005-10-31 | 2012-01-10 | Sap Ag | Method, system, and medium for winning bid evaluation in an auction |
US7835977B2 (en) | 2005-11-03 | 2010-11-16 | Sap Ag | Method and system for generating an auction using a template in an integrated internal auction system |
US8095449B2 (en) | 2005-11-03 | 2012-01-10 | Sap Ag | Method and system for generating an auction using a product catalog in an integrated internal auction system |
US20080103923A1 (en) * | 2006-10-31 | 2008-05-01 | Digital River, Inc. | Centralized Payment Gateway System and Method |
US8694428B2 (en) * | 2006-12-28 | 2014-04-08 | International Business Machines Corporation | Consumer oriented services system and method |
US20100010906A1 (en) * | 2007-01-23 | 2010-01-14 | William Grecia | Point of sale payment method for multiple recipients using a digital payment service |
US9524496B2 (en) * | 2007-03-19 | 2016-12-20 | Hugo Olliphant | Micro payments |
US9119783B2 (en) | 2007-05-07 | 2015-09-01 | Insmed Incorporated | Method of treating pulmonary disorders with liposomal amikacin formulations |
US8204825B2 (en) * | 2007-07-16 | 2012-06-19 | American Express Travel Related Services Company, Inc. | System, method and computer program product for processing payments |
US8233600B1 (en) * | 2007-07-17 | 2012-07-31 | Juniper Networks, Inc. | Automated creation of multiple provider services |
US8799109B2 (en) * | 2007-08-20 | 2014-08-05 | Ebay Inc. | System and method for payment on call in a networked environment |
US8214291B2 (en) | 2007-10-19 | 2012-07-03 | Ebay Inc. | Unified identity verification |
FR2924510B1 (en) * | 2007-12-03 | 2014-01-17 | Limonetik | ONLINE PAYMENT SYSTEM |
US8145569B2 (en) * | 2007-12-13 | 2012-03-27 | Google Inc. | Multiple party on-line transactions |
US20090192911A1 (en) * | 2008-01-29 | 2009-07-30 | Revolution Money Inc. | Payment redirection for online transactions |
US8082187B2 (en) * | 2008-05-07 | 2011-12-20 | AcademixDirect, Inc. | Method of generating a referral website URL using website listings in a cookie |
US9324098B1 (en) * | 2008-07-22 | 2016-04-26 | Amazon Technologies, Inc. | Hosted payment service system and method |
US8285640B2 (en) * | 2008-07-23 | 2012-10-09 | Ebay, Inc. | System and methods for facilitating fund transfers over a network |
US8090650B2 (en) | 2008-07-24 | 2012-01-03 | At&T Intellectual Property I, L.P. | Secure payment service and system for interactive voice response (IVR) systems |
US9760921B2 (en) * | 2008-08-21 | 2017-09-12 | Digital River, Inc. | Half-graphical user interface order processing system and method |
US9747621B1 (en) * | 2008-09-23 | 2017-08-29 | Amazon Technologies, Inc. | Widget-based integration of payment gateway functionality into transactional sites |
US8838503B2 (en) * | 2008-12-08 | 2014-09-16 | Ebay Inc. | Unified identity verification |
GB2466676A (en) | 2009-01-06 | 2010-07-07 | Visa Europe Ltd | A method of processing payment authorisation requests |
GB2466810A (en) | 2009-01-08 | 2010-07-14 | Visa Europe Ltd | Processing payment authorisation requests |
US20110035294A1 (en) * | 2009-08-04 | 2011-02-10 | Authernative, Inc. | Multi-tier transaction processing method and payment system in m- and e- commerce |
US20110087568A1 (en) * | 2009-10-14 | 2011-04-14 | Dipak Sheth | Integrated profile and payment exchange |
WO2011082467A1 (en) * | 2010-01-11 | 2011-07-14 | Toposis Corporation | Systems and methods for online commerce |
US10169308B1 (en) | 2010-03-19 | 2019-01-01 | Google Llc | Method and system for creating an online store |
WO2011148873A1 (en) * | 2010-05-25 | 2011-12-01 | 日本電気株式会社 | Method for managing payment means over a network using electronic wallet, payment means management device, and payment means management program |
US8543508B2 (en) | 2010-07-09 | 2013-09-24 | Visa International Service Association | Gateway abstraction layer |
US8762451B2 (en) * | 2010-09-03 | 2014-06-24 | Visa International Service Association | System and method for custom service markets |
US20120266059A1 (en) * | 2010-10-05 | 2012-10-18 | Ixaris Systems Limited | Networked financial processing system |
US8725644B2 (en) | 2011-01-28 | 2014-05-13 | The Active Network, Inc. | Secure online transaction processing |
US20120215584A1 (en) * | 2011-02-18 | 2012-08-23 | Leapset, Inc. | Tracking off-line commerce and online activity |
US20130024323A1 (en) * | 2011-07-20 | 2013-01-24 | Tomassen Thomas Hj | System for completing an online transaction |
CA2845602C (en) * | 2011-10-12 | 2021-10-19 | Boost Payment Solutions, LLC | Electronic payment processing |
US8595059B1 (en) | 2011-10-12 | 2013-11-26 | Google Inc. | Forwarding offers for payment by others |
US11514435B2 (en) | 2011-10-12 | 2022-11-29 | Boost Payment Solutions, Inc. | Electronic payment processing using adjusted interchange rate |
US11488142B2 (en) * | 2011-10-12 | 2022-11-01 | Boost Payment Solutions, Inc. | Electronic payment processing |
US9830596B2 (en) | 2011-11-01 | 2017-11-28 | Stripe, Inc. | Method for conducting a transaction between a merchant site and a customer's electronic device without exposing payment information to a server-side application of the merchant site |
FI20125123L (en) * | 2012-02-03 | 2013-08-04 | Markku Tolonen | Procedure and system for purchasing an item |
US9092776B2 (en) * | 2012-03-15 | 2015-07-28 | Qualcomm Incorporated | System and method for managing payment in transactions with a PCD |
US9105021B2 (en) | 2012-03-15 | 2015-08-11 | Ebay, Inc. | Systems, methods, and computer program products for using proxy accounts |
US10311506B1 (en) | 2012-03-30 | 2019-06-04 | David Frederick | System and method for e-commerce accessibility |
US9430784B1 (en) | 2012-03-30 | 2016-08-30 | David Frederick | System for E-commerce accessibility |
US11023960B1 (en) | 2012-03-30 | 2021-06-01 | David Frederick | System and method for e-commerce accessibility |
TWI517066B (en) * | 2012-05-04 | 2016-01-11 | 普萊普雷股份有限公司 | Product reservation system and method tehreof |
US10026119B2 (en) | 2012-09-10 | 2018-07-17 | Google Llc | Efficient transfer of funds between accounts |
US11210648B2 (en) | 2012-10-17 | 2021-12-28 | Royal Bank Of Canada | Systems, methods, and devices for secure generation and processing of data sets representing pre-funded payments |
US9082119B2 (en) * | 2012-10-17 | 2015-07-14 | Royal Bank of Canada. | Virtualization and secure processing of data |
US11080701B2 (en) | 2015-07-02 | 2021-08-03 | Royal Bank Of Canada | Secure processing of electronic payments |
US9092777B1 (en) * | 2012-11-21 | 2015-07-28 | YapStone, Inc. | Credit card tokenization techniques |
US9754245B1 (en) | 2013-02-15 | 2017-09-05 | Amazon Technologies, Inc. | Payments portal |
JP6128958B2 (en) * | 2013-05-28 | 2017-05-17 | キヤノン株式会社 | Information processing server system, control method, and program |
WO2015003050A1 (en) * | 2013-07-02 | 2015-01-08 | Boku, Inc. | Merchant hosted checkout |
US10147131B2 (en) | 2013-07-02 | 2018-12-04 | Boku, Inc. | Merchant hosted checkout at a merchant server |
US10438183B2 (en) | 2013-07-02 | 2019-10-08 | Boku, Inc. | Merchant hosted checkout at a billing server |
KR101574156B1 (en) * | 2013-09-03 | 2015-12-07 | 엔에이치엔엔터테인먼트 주식회사 | Method and system for payment |
US20150149308A1 (en) * | 2013-11-26 | 2015-05-28 | Daniel Lin | Method and System for Credit Card Selection at a Point of Sale |
CN107004190A (en) | 2014-10-10 | 2017-08-01 | 加拿大皇家银行 | System for handling electronic transaction |
US9710316B1 (en) | 2014-12-18 | 2017-07-18 | Amazon Technologies, Inc. | Flexible scripting platform for troubleshooting |
US9785489B1 (en) * | 2014-12-18 | 2017-10-10 | Amazon Technologies, Inc. | Secure script execution using sandboxed environments |
US11354651B2 (en) | 2015-01-19 | 2022-06-07 | Royal Bank Of Canada | System and method for location-based token transaction processing |
CN113379401A (en) | 2015-01-19 | 2021-09-10 | 加拿大皇家银行 | Secure processing of electronic payments |
US9954962B2 (en) | 2015-02-06 | 2018-04-24 | Bank Of America Corporation | Serving anonymous cookies associated with purchasing analytics |
US11599879B2 (en) | 2015-07-02 | 2023-03-07 | Royal Bank Of Canada | Processing of electronic transactions |
US9832229B2 (en) | 2015-12-14 | 2017-11-28 | Bank Of America Corporation | Multi-tiered protection platform |
US9832200B2 (en) | 2015-12-14 | 2017-11-28 | Bank Of America Corporation | Multi-tiered protection platform |
US9992163B2 (en) | 2015-12-14 | 2018-06-05 | Bank Of America Corporation | Multi-tiered protection platform |
EP3261034A1 (en) * | 2016-06-23 | 2017-12-27 | Mastercard International Incorporated | Method and system for authorizing and processing payment transactions over a network |
CN107038560B (en) * | 2017-01-06 | 2020-09-08 | 阿里巴巴集团控股有限公司 | System, method and device for executing payment service |
US11361284B1 (en) | 2018-05-31 | 2022-06-14 | Stripe, Inc. | Payment processing method and apparatus using an intermediary platform |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6047268A (en) * | 1997-11-04 | 2000-04-04 | A.T.&T. Corporation | Method and apparatus for billing for transactions conducted over the internet |
US20030023549A1 (en) * | 2001-06-27 | 2003-01-30 | American Express Travel Related Services Company, Inc. | Consolidated payment account system and method |
US20040098313A1 (en) * | 2002-11-19 | 2004-05-20 | Ashish Agrawal | Detection of fraudulent associate-based transactions |
US7949600B1 (en) * | 2000-06-27 | 2011-05-24 | Western Union Financial Services, Inc. | Method for facilitating payment of a computerized transaction |
Family Cites Families (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6535880B1 (en) | 2000-05-09 | 2003-03-18 | Cnet Networks, Inc. | Automated on-line commerce method and apparatus utilizing a shopping server verifying product information on product selection |
US6212556B1 (en) | 1995-11-13 | 2001-04-03 | Webxchange, Inc. | Configurable value-added network (VAN) switching |
US5778178A (en) | 1995-11-13 | 1998-07-07 | Arunachalam; Lakshmi | Method and apparatus for enabling real-time bi-directional transactions on a network |
US5983208A (en) * | 1996-06-17 | 1999-11-09 | Verifone, Inc. | System, method and article of manufacture for handling transaction results in a gateway payment architecture utilizing a multichannel, extensible, flexible architecture |
US6324525B1 (en) | 1996-06-17 | 2001-11-27 | Hewlett-Packard Company | Settlement of aggregated electronic transactions over a network |
US5931917A (en) | 1996-09-26 | 1999-08-03 | Verifone, Inc. | System, method and article of manufacture for a gateway system architecture with system administration information accessible from a browser |
US6058373A (en) | 1996-10-16 | 2000-05-02 | Microsoft Corporation | System and method for processing electronic order forms |
US5796952A (en) * | 1997-03-21 | 1998-08-18 | Dot Com Development, Inc. | Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database |
CA2910997A1 (en) * | 1999-04-30 | 2000-11-09 | Paypal, Inc. | System and method for electronically exchanging value among distributed users |
US7035817B1 (en) * | 1999-07-09 | 2006-04-25 | Verizon Laboratories Inc. | Electronic catalog method |
US6873974B1 (en) * | 1999-08-17 | 2005-03-29 | Citibank, N.A. | System and method for use of distributed electronic wallets |
US7096268B1 (en) * | 1999-09-01 | 2006-08-22 | Matsushita Electric Industrial Co., Ltd. | Copyrighted data processing method and apparatus |
US7966259B1 (en) * | 1999-12-09 | 2011-06-21 | Amazon.Com, Inc. | System and methods for facilitating transactions on, and personalizing web pages of, third party web sites |
US6540135B1 (en) * | 1999-12-17 | 2003-04-01 | International Business Machines Corporation | Method and system for expediting service to a user by defaulting to typical preferences of the user at a service-oriented user interface terminal |
US7072856B1 (en) * | 2000-01-18 | 2006-07-04 | Al Nachom | Communication enhancement means |
US7103566B2 (en) * | 2000-02-23 | 2006-09-05 | Lucent Technologies Inc. | Applications of executable shopping lists |
FR2805626B1 (en) * | 2000-02-29 | 2004-08-06 | Inovatel | METHOD AND SYSTEM FOR GRANTING PRIVILEGES BY AN ACCESS MANAGER WITHIN A COMMUNICATION NETWORK |
CA2411979A1 (en) * | 2000-07-11 | 2002-01-17 | Paypal, Inc. | System and method for third-party payment processing |
US7558743B2 (en) * | 2000-08-01 | 2009-07-07 | Razumov Sergey N | System for purchase check-out arrangement in retail system |
US20020083178A1 (en) * | 2000-08-11 | 2002-06-27 | Brothers John David West | Resource distribution in network environment |
US6728767B1 (en) * | 2000-08-18 | 2004-04-27 | Cisco Technology, Inc. | Remote identification of client and DNS proxy IP addresses |
US7072859B1 (en) * | 2000-08-21 | 2006-07-04 | Black & Decker Inc. | Electronic commerce checkout system |
US7536351B2 (en) * | 2000-10-30 | 2009-05-19 | Amazon.Com, Inc. | User-to-user payment service with payee-specific pay pages |
US7356507B2 (en) * | 2000-10-30 | 2008-04-08 | Amazon.Com, Inc. | Network based user-to-user payment service |
US7542943B2 (en) * | 2000-10-30 | 2009-06-02 | Amazon Technologies, Inc. | Computer services and methods for collecting payments from and providing content to web users |
US20050240518A1 (en) * | 2000-11-30 | 2005-10-27 | Ricoh Company Ltd. | Method and system for on-line communication based on an off-line transaction |
US20030088483A1 (en) * | 2000-12-28 | 2003-05-08 | Bissell, Inc. | System, method and computer program product for an enhanced E-commerce graphical user interface |
US20020107746A1 (en) * | 2001-02-02 | 2002-08-08 | T.C. Jacoby & Company, Inc. | Computerized commission based trading operations |
US20020120714A1 (en) * | 2001-02-26 | 2002-08-29 | Borislav Agapiev | Distributed-code, custom-generated dynamic internet inclusion agent |
GB2400963B (en) * | 2001-05-02 | 2004-12-29 | Virtual Access Ltd | Secure payment method and system |
US20030018587A1 (en) * | 2001-07-20 | 2003-01-23 | Althoff Oliver T. | Checkout system for on-line, card present equivalent interchanges |
US7254549B1 (en) * | 2001-07-23 | 2007-08-07 | At&T Corp. | Real-time addresses for direct mail using online directories |
US7191151B1 (en) * | 2001-08-23 | 2007-03-13 | Paypal, Inc. | Instant availability of electronically transferred funds |
US20030095660A1 (en) * | 2001-10-15 | 2003-05-22 | Overpeer, Inc. | System and method for protecting digital works on a communication network |
US20050080635A1 (en) * | 2002-02-28 | 2005-04-14 | Groff Bradley K. | Direct distribution system for consumer goods and services |
US7110399B2 (en) * | 2002-03-28 | 2006-09-19 | International Business Machines Corporation | System and method for redirecting network addresses for deferred rendering |
US20040078331A1 (en) * | 2002-10-17 | 2004-04-22 | Fakih Adonis El | Payment system using electronic stamps |
US7548746B2 (en) * | 2002-11-01 | 2009-06-16 | At&T Mobility Ii Llc | General purpose automated activation and provisioning technologies |
US7457778B2 (en) | 2003-03-21 | 2008-11-25 | Ebay, Inc. | Method and architecture for facilitating payment to e-commerce merchants via a payment service |
US9734524B2 (en) * | 2008-05-16 | 2017-08-15 | Ginger Casey | Systems and methods for virtual markets with product pickup |
-
2003
- 2003-12-31 US US10/749,684 patent/US7457778B2/en active Active
-
2004
- 2004-03-18 EP EP04757993.3A patent/EP1609104B1/en not_active Expired - Lifetime
- 2004-03-18 EP EP13154722.6A patent/EP2592591A1/en not_active Ceased
- 2004-03-18 CN CN201210150174.7A patent/CN102880954B/en not_active Expired - Lifetime
- 2004-03-18 WO PCT/US2004/008683 patent/WO2004086190A2/en active Application Filing
- 2004-03-18 EP EP13154723.4A patent/EP2592592A1/en not_active Withdrawn
-
2008
- 2008-08-26 US US12/198,664 patent/US20080313053A1/en not_active Abandoned
-
2009
- 2009-03-31 US US12/416,082 patent/US7831510B2/en not_active Expired - Lifetime
-
2010
- 2010-08-30 US US12/871,766 patent/US7930247B2/en not_active Expired - Lifetime
-
2011
- 2011-06-14 US US13/160,316 patent/US8112353B2/en not_active Expired - Fee Related
-
2012
- 2012-01-11 US US13/348,511 patent/US20120150688A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6047268A (en) * | 1997-11-04 | 2000-04-04 | A.T.&T. Corporation | Method and apparatus for billing for transactions conducted over the internet |
US7949600B1 (en) * | 2000-06-27 | 2011-05-24 | Western Union Financial Services, Inc. | Method for facilitating payment of a computerized transaction |
US20030023549A1 (en) * | 2001-06-27 | 2003-01-30 | American Express Travel Related Services Company, Inc. | Consolidated payment account system and method |
US20040098313A1 (en) * | 2002-11-19 | 2004-05-20 | Ashish Agrawal | Detection of fraudulent associate-based transactions |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080313053A1 (en) * | 2003-03-21 | 2008-12-18 | Ebay Inc. | Payment service |
US20170256003A1 (en) * | 2014-03-31 | 2017-09-07 | Monticello Enterprises, Llc | System and method for providing a payment handler api and a browser payment request api for processing a payment |
US9922381B2 (en) * | 2014-03-31 | 2018-03-20 | Monticello Enterprises LLC | System and method for providing a payment handler API and a browser payment request API for processing a payment |
US10432667B2 (en) * | 2015-08-27 | 2019-10-01 | Mastercard International Incorporated | Systems and methods for monitoring computer authentication procedures |
US11310281B2 (en) | 2015-08-27 | 2022-04-19 | Mastercard International Incorporated | Systems and methods for monitoring computer authentication procedures |
WO2017189917A1 (en) | 2016-04-28 | 2017-11-02 | Paypal, Inc. | User authentication using a browser cookie shared between a browser and an application |
US20170316400A1 (en) * | 2016-04-28 | 2017-11-02 | Paypal, Inc. | User authentication using a browser cookie shared between a browser and an application |
EP3449447A4 (en) * | 2016-04-28 | 2019-11-20 | PayPal, Inc. | User authentication using a browser cookie shared between a browser and an application |
US11321700B2 (en) * | 2016-04-28 | 2022-05-03 | Paypal, Inc. | User authentication using a browser cookie shared between a browser and an application |
US20220180349A1 (en) * | 2016-04-28 | 2022-06-09 | Paypal, Inc. | User authentication using a browser cookie shared between a browser and an application |
US20200097959A1 (en) * | 2018-09-21 | 2020-03-26 | Mastercard International Incorporated | Payment transaction process employing dynamic account expiry and dynamic token verification code |
Also Published As
Publication number | Publication date |
---|---|
US7457778B2 (en) | 2008-11-25 |
WO2004086190A3 (en) | 2005-06-09 |
EP1609104B1 (en) | 2019-03-13 |
US8112353B2 (en) | 2012-02-07 |
US7930247B2 (en) | 2011-04-19 |
EP2592591A1 (en) | 2013-05-15 |
US7831510B2 (en) | 2010-11-09 |
US20100057589A1 (en) | 2010-03-04 |
EP1609104A2 (en) | 2005-12-28 |
EP2592592A1 (en) | 2013-05-15 |
EP1609104A4 (en) | 2006-12-20 |
CN102880954A (en) | 2013-01-16 |
WO2004086190A2 (en) | 2004-10-07 |
US20110246367A1 (en) | 2011-10-06 |
US20080313053A1 (en) | 2008-12-18 |
US20100325042A1 (en) | 2010-12-23 |
CN102880954B (en) | 2016-07-06 |
US20050065881A1 (en) | 2005-03-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8112353B2 (en) | Payment service to efficiently enable electronic payment | |
US10776857B2 (en) | Systems and methods for facilitating financial transactions over a network | |
US10963932B2 (en) | User enhanced authentication system for online purchases | |
US10580070B2 (en) | Distributed system for commerce | |
KR100620192B1 (en) | Stored value electronic certificate processing | |
US8152054B2 (en) | Money transfer systems and methods | |
US10169748B2 (en) | Alternative payment implementation for electronic retailers | |
US20120010993A1 (en) | Proxied consumer e-commerce transactions | |
WO2001052127A1 (en) | Secure private agent for electronic transactions | |
US11062339B2 (en) | Upselling to customers following initial online purchase | |
CN105913245A (en) | Internet payment method, device and server | |
US11610245B2 (en) | Online shopping system and method facilitating foreign transactions | |
US20130046656A1 (en) | Method and System for Navigation Free Online Payment | |
KR101569046B1 (en) | Product purchase user interface providing system and providing method thereof | |
CN1791887A (en) | Method and architecture for facilitating payment to e-commerce merchants via a payment service | |
EP1454273A2 (en) | Method and apparatus for facilitating electronic commerce via an itemized statement |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EBAY INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LI, DAVID CHING;KANG, DAVID YOUNG-JUNE;LISTWON, BENJAMIN GREGG;AND OTHERS;SIGNING DATES FROM 20041115 TO 20041202;REEL/FRAME:034840/0302 |
|
AS | Assignment |
Owner name: PAYPAL, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EBAY INC.;REEL/FRAME:036169/0798 Effective date: 20150717 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |