| CPC G06Q 20/027 (2013.01) [G06Q 20/356 (2013.01); G06Q 30/0601 (2013.01); G07F 19/211 (2013.01)] | 17 Claims |

|
1. A method, comprising:
receiving, from an e-commerce application, a call to an application programming interface (API) to initiate a purchase transaction;
determining, by the API examining the purchase transaction, if a payment method for the purchase transaction is synchronous or asynchronous;
communicating, using the API, with a synchronous payment system to perform the purchase transaction in response to determining that the payment method is synchronous;
extending the API with executable statements to handle asynchronous purchase transactions without a change to an interface called by the e-commerce application that would cause a redesign of the e-commerce application in response to determining that the payment method is asynchronous;
communicating, using the API, with an asynchronous payment system to perform the purchase transaction in response to determining that the payment method is asynchronous, wherein the asynchronous payment system is different from the synchronous payment system;
providing a user interface element that prevents interactions with other portions of the e-commerce application while the asynchronous payment system performs the purchase transaction until a user takes an action on the user interface element; and
providing a result of the purchase transaction to the e-commerce application.
|