Alternative payment implementation for electronic retailers

• US 10,157,375 B2
• Filed: 06/03/2009
• Issued: 12/18/2018
• Est. Priority Date: 06/03/2008
• Status: Active Grant

• Current Assignee: CardinalCommerce Corporation (Visa, Inc.)
• Original Assignee: CardinalCommerce Corporation (Visa, Inc.)
• Inventors: Balasubramanian, Chandra S., Keresman, III, Michael A., Goodman, Eric, Ratica, Adam, Rauhe, Scott
• Primary Examiner(s): ADE, OGER GARCIA
• Application Number:
  US12/477,483
• Publication Number:
  US 20090313147A1
• Time in Patent Office: 3,485 Days
• Field of Search: 705 30
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/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
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

A method of processing a transaction between a merchant and a buyer over a communication network is provided. The transaction is processed using one of a plurality of alternative payment options and each of the alternative payment options are provided by one of a plurality of alternative payment providers. Each of the alternative payment providers uses a different alternative payment implementation. The method includes: obtaining transaction information from the merchant; returning a redirection URL and an order identifier to the merchant; obtaining a transaction message from the merchant, where the transaction message specifies the type of operation; performing the operation type specified in the transaction message with the appropriate alternative payment provider; and returning a processing message to the merchant containing the results from performing the operation type specified in the transaction message.

Claims

1. A method of processing a transaction between a merchant system and a consumer over a communications network by at least one server operated by a third party, said method comprising:

obtaining, with the at least one server, customer transaction information from the merchant system received through a merchant website, wherein said customer transaction information identifies an alternative payment option of an alternative payment provider being used and selected by the consumer, and wherein the third party is independent of the alternative payment provider;

returning, with the at least one server, a redirection Uniform Resource Locator (URL) and an order identifier to the merchant system, wherein said redirection URL is dependent upon the identified alternative payment option of the alternative payment provider and the order identifier exists for a life cycle of the customer transaction, and wherein the redirection URL is configured to redirect a device operated by the consumer away from the merchant website to collect additional payment information from the consumer or obtain authentication from the consumer;

receiving, with the at least one server, a transaction message from said merchant system after the device operated by the consumer is redirected back to the merchant system, wherein said transaction message format includes a unified message format and said transaction message includes an operation type;

performing, with the at least one server, the operation type specified in the received transaction message with the alternative payment provider corresponding to the identified alternative payment option in accordance with a specific alternative payment implementation of the alternative payment option; and

returning, with the at least one server, a processing message to the merchant system containing results from performing the operation type specified in the received transaction message, wherein said processing message format includes the unified message format.

2. The method of claim 1, wherein performing the operation type specified includes:

using message formats, response codes and communication protocols of an alternative payment implementation corresponding to the identified alternative payment option of the alternative payment provider.

3. The method of claim 1, further comprising:

initiating the transaction with the alternative payment provider corresponding to the identified alternative payment option, prior to returning the redirection URL and the order identifier to the merchant.

4. The method of claim 1, further comprising:

detecting the availability of the identified alternative payment provider; and

in response to the alternative payment provider not being available, notifying the merchant system prior to returning the redirection URL and the order identifier to the merchant.

5. The method of claim 1, wherein the redirection URL points to the alternative payment provider of the identified alternative payment option.

6. The method of claim 1, wherein the redirection URL points to the at least one server of the third party, a system implementing the method, wherein the at least one server of the third party system is operative to collect additional payment information.

7. The method of claim 1, wherein the operation type includes at least one of:

authorize, capture and refund.

8. The method of claim 1, wherein the alternative payment provider of the identified alternative payment option communicates asynchronously.

21. The method of claim 1, wherein:

in response to the redirection URL being used to collect additional payment information, the redirection URL points to the at least one server of the third party.

22. The method of claim 1, wherein:

in response to the redirection URL being used for consumer authentication, the redirection URL points to an alternative payment server of the alternative payment provider.

23. The method of claim 1, wherein:

the redirection URL is dependent upon whether the identified alternative payment option of the alternative payment provider requires the consumer to directly authenticate and enter additional information with the alternative payment provider.

9. A system for supporting the processing of transactions between merchant systems and consumers over a communications network, said system, comprising:

one or more computer servers of a third party configured with;

a merchant layer configured to exchange communications with the merchant systems and receive customer transaction information and an operation type for each transaction, wherein said customer transaction information for each transaction includes payment information and identifies an alternative payment option of an alternative payment provider selected to be used by a consumer from a plurality of alternative payment providers through a merchant website;

a plug-in layer including a plurality of plug-in components, wherein each of the plurality of plug-in components administers a different one of the plurality of alternative payment providers in accordance with a respective alternative payment implementation, wherein the third party and the one or more computer servers of the third party are independent of the plurality of alternative payment providers; and

a logic layer residing between the merchant layer and the plug-in layer, wherein said logic layer is adapted to route communications between the merchant layer and selected plug-in components in the plug-in layer, wherein said operation type and said transaction information for each transaction are routed to the plug-in component responsible for administering the alternative payment option of the alternative payment provider associated with the customer transaction information for each transaction, and wherein said logic layer is adapted to return a redirection Uniform Resource Locator (URL) and a payment network routable order identifier to the merchant systems for each transaction, the redirection URL returned before receipt of the operation type, and wherein the redirection URL is configured to redirect devices operated by consumers away from a respective merchant website to collect additional payment information from the consumer or obtain authentication from the consumer.

10. The system of claim 9, further comprising a data layer, wherein the data layer stores the customer transaction information for each transaction.

11. The system of claim 9, wherein the logic layer is operative to disable a plug-in component if the alternative payment provider associated with the plug- in component is unavailable.

12. The system of claim 9, wherein the logic layer is operative to provide the merchant systems with daily summary reports of transactions.

13. The system of claim 9, wherein the logic layer is operative to communicate transactions to at least one processor.

14. The system of claim 9, further comprising a web layer, where said web layer receives additional payment information from the consumer, and where the redirection URL points to the system.

15. The system of claim 9, wherein the merchant layer communicates with the merchant systems using a unified message format.

16. The system of claim 9, wherein at least one of the plurality of plug-in components of the plug-in layer is adapted to receive asynchronous messages associated with the alternative payment provider of an alternate payment implementation.

17. The system of claim 9, wherein the plug-in layer allows selected plug-in components to be added, removed and modified without disrupting other plug-in components residing in the plug-in layer.

18. The system of claim 9, wherein the redirection URL points to the alternative payment provider of the identified alternative payment option.

19. The system of claim 9, wherein each operation type includes at least one of:

authorize, capture, and refund.

20. A system for processing a transaction between a merchant system and a consumer over a communications network, said system comprising:

one or more servers of a third party programmed to;

obtain transaction information for the transaction from the merchant system through a merchant website, wherein said transaction information identifies an alternative payment option of an alternative payment provider being used for the transaction and which is selected by the consumer, and wherein the third party is independent of the alternative payment provider;

return a redirection Uniform Resource Locator (URL) and an order identifier to the merchant system to obtain additional transaction information for the transaction, wherein said redirection URL is dependent upon the alternative payment option identified by the obtained transaction information, and wherein the redirection URL is configured to redirect a device operated by the consumer away from the merchant website to collect additional payment information from the consumer or obtain authentication from the consumer;

after the additional transaction information is collected and after the device operated by the consumer is redirected back to the merchant website, receive a transaction message from said merchant system, wherein said transaction message format includes a unified message format and said transaction message includes an operation type;

perform the operation type specified in the transaction message with the alternative payment provider corresponding to the alternative payment option identified by the obtained transaction information using the obtained transaction information, and a specific alternative payment implementation of the alternative payment option, to complete the transaction; and

,

return a processing message to the merchant system containing results from performing the operation type specified in the transaction message, wherein said processing message format includes the unified message format.