| CPC G06Q 20/12 (2013.01) [G06Q 20/027 (2013.01); G06Q 20/227 (2013.01); G06Q 20/405 (2013.01)] | 18 Claims |

|
1. A computer implemented method performed by a commerce platform system, comprising:
establishing, by a server system, first communications channels using a first set of application programming interfaces (APIs) that integrate the server system with a plurality of payment type provider platforms that provide a plurality of payment types;
receiving, by the server system, a request from a third-party server via a second communication channel, wherein the request comprises account data associated with an account, and wherein the third-party server and the server system communicate via a second set of APIs over the second communication channel to provide the third-party server access to the plurality of payment types;
generating a query comprising at least a portion of the account data;
executing the query at the plurality of payment type provider platforms;
receiving responses to the query from the plurality of payment type provider platforms, the response indicating whether at least a portion of the account data is associated with information in one or more data resources of the plurality of payment type provider platforms;
identifying available payment types for the account based on the responses;
executing a machine learning model to determine a relevancy score of each of the available payment types with respect to the account data, the relevancy score based at least in part on a probability of the account using each available payment type to complete a transaction, wherein the probability is calculated by the machine learning model;
ranking the available payment types based on the relevancy scores;
selecting, as one or more recommended payment types, available payment types having relevancy scores equal to or greater than a threshold or rank;
communicating, by the server system, the one or more recommended payment types to the third-party server causing the third-party server to provide the one or more recommended payment types within a user interface;
receiving, at the server system, a selection of one of the one or more recommended payment types; and
completing, by the server system, an electronic payment using the selected one of the one or more recommended payment types.
|