Extensible Interface for Synchronous and Asynchronous Payment

Abstract

An applications programming interface (API) or other interface may be configured for use with a plurality of e-commerce applications and/or a plurality of payment systems. The API may be associated with an operating system of a client or may be otherwise located in an e-commerce system or network. The API may receive a call regarding a purchase transaction. The purchase transaction may be examined to determine if a payment method is synchronous or asynchronous. An appropriate payment system may be activated to perform the purchase transaction based at least in part on the determination made by the examination of the purchase transaction. A result of the purchase transaction may be sent to the e-commerce program. By revision of the API, developers of e-commerce applications are freed from the burden of revising code in response to the need to utilize additional or differently operated payment systems.

What is claimed is: 
     
         1 . One or more computer-readable media storing computer-executable instructions that, when executed, cause one or more processors to perform acts comprising:
 exposing an interface, configured for communication with a plurality of payment systems, to calls by an e-commerce application;   receiving a call at the interface regarding a purchase transaction;   examining the purchase transaction to determine if a payment method is synchronous or asynchronous;   communicating with a payment system to perform the purchase transaction based at least in part on the determination made by the examination of the purchase transaction; and   providing a result of the purchase transaction to the e-commerce application.   
     
     
         2 . One or more computer-readable media as recited in  claim 1 , additionally comprising:
 providing a user interface to a user of the e-commerce application; and   collecting data by operation of the user interface for use by an asynchronous payment system.   
     
     
         3 . One or more computer-readable media as recited in  claim 1 , additionally comprising:
 determining that the payment method is asynchronous; and   providing a user interface to a user of the e-commerce application, wherein the user interface is configured to wrap a webpage from a payment site associated with the asynchronous payment method.   
     
     
         4 . One or more computer-readable media as recited in  claim 1 , additionally comprising:
 providing a user interface to a user of the e-commerce application to allow the user to communicate with a payment site associated with the asynchronous payment method; and   providing a user interface element configured to occupy the user while a store poles a commerce platform to determine if a result is success or failure.   
     
     
         5 . One or more computer-readable media as recited in  claim 1 , wherein exposing the interface comprises exposing the interface by:
 a software development kit;   an operating system of a computing device;   a commerce platform;   a cloud service environment; and   a website.   
     
     
         6 . One or more computer-readable media as recited in  claim 1 , additionally comprising:
 extending a number of payment systems for which the interface is configured to handle purchase transactions;   wherein a format of calls to the interface is unchanged after the extending.   
     
     
         7 . One or more computer-readable media as recited in  claim 1 , wherein:
 the interface is extensible to allow expansion of a number of asynchronous payment methods and a number of synchronous payment methods; and   the interface is configured to maintain an unchanged appearance to the e-commerce application after expansion.   
     
     
         8 . One or more computer-readable media as recited in  claim 1 , wherein exposing the interface comprises exposing a consistent interface for purchase transactions utilizing any of a plurality of payment systems, including synchronous and asynchronous payment systems. 
     
     
         9 . One or more computer-readable media as recited in  claim 1 , additionally comprising:
 providing a user-facing dialog box until an asynchronous transaction is completed.   
     
     
         10 . One or more computer-readable media as recited in  claim 1 , additionally comprising:
 receiving an error message due to an attempt to process the purchase transaction incorrectly as a synchronous purchase transaction; and   providing a webpage associated with an asynchronous payment system to a user of the e-commerce application, wherein the webpage is wrapped by a webpage of the interface.   
     
     
         11 . One or more computer-readable media as recited in  claim 1 , additionally comprising:
 detecting an exit by a user of the e-commerce application from which the call to the interface was received; and   performing cleanup of the purchase transaction, including determining if a license is granted to the user and returning status of the purchase transaction to the e-commerce application.   
     
     
         12 . A method, comprising:
 under control of one or more processors configured with executable instructions:   receiving a call regarding a purchase transaction from an e-commerce application, the call received at an interface configured for communication with a plurality of payment systems;   examining the purchase transaction to determine a payment system that is indicated;   communicating with the payment system to provide information required by the payment system; and   providing a result of the purchase transaction, received from the payment system, to the e-commerce application.   
     
     
         13 . The method as recited in  claim 12 , additionally comprising:
 wrapping a user interface of a payment system within a consumer-facing user interface; and   providing a dialog box configured to occupy the user as payment is completed.   
     
     
         14 . The method as recited in  claim 12 , additionally comprising:
 distinguishing an asynchronous payment system from payment systems including synchronous payment systems; and   providing a user interface to a user of the e-commerce application, wherein the user interface is configured to wrap a webpage of the asynchronous payment system.   
     
     
         15 . The method as recited in  claim 12 , additionally comprising:
 recognizing that a payment site indicated by the call is associated with an asynchronous payment method; and   providing a result to the e-commerce application indicating one of success or failure.   
     
     
         16 . The method as recited in  claim 12 , wherein:
 a number of payment systems for which the interface is configured to handle purchase transactions is extended; and   a format of calls to the interface is unchanged after the extending.   
     
     
         17 . The method as recited in  claim 12 , wherein:
 communicating with the payment system comprises communicating with a procedure extensible to allow communication with additional payment systems; and   the interface, after extension of the procedure to communicate with the additional payment systems, remains unchanged to existing e-commerce applications.   
     
     
         18 . The method as recited in  claim 12 , additionally comprising:
 persisting a user-facing dialog box until an asynchronous transaction is completed.   
     
     
         19 . A system, comprising:
 a commerce platform server to contact one of a plurality of payment systems depending on a type of transaction; and   an interface, in communication with the commerce platform server and an e-commerce program, the interface configured to:
 receive a call regarding a purchase transaction from the e-commerce program; 
 examine the purchase transaction to determine if a payment system indicated by the purchase transaction is synchronous or asynchronous; 
 provide a user interface to a user of the e-commerce program based at least in part on the examination; 
 collect data by operation of the user interface for use by a payment system indicated by the call; 
 communicate with the payment system to perform the purchase transaction; and 
 provide a result of the purchase transaction to the e-commerce program. 
   
     
     
         20 . The system of  claim 19 , wherein:
 the interface is extensible to allow expansion in a number of asynchronous payment methods and a number of synchronous payment methods; and   the interface is configured to maintain an unchanged appearance to the e-commerce program after the expansion.