US 12,405,847 B2
Artificial intelligence based integration frameworks
Dushyant Sharma, Waxhaw, NC (US)
Assigned to PAYMENTUS CORPORATION, Charlotte, NC (US)
Filed by Paymentus Corporation, Charlotte, NC (US)
Filed on Mar. 27, 2024, as Appl. No. 18/618,519.
Application 18/618,519 is a continuation of application No. 17/452,267, filed on Oct. 26, 2021, granted, now 11,972,311.
Prior Publication US 2024/0241777 A1, Jul. 18, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 9/54 (2006.01); G06F 40/20 (2020.01); G06N 20/00 (2019.01)
CPC G06F 9/548 (2013.01) [G06F 40/20 (2020.01); G06N 20/00 (2019.01); G06F 9/541 (2013.01)] 21 Claims
OG exemplary drawing
 
1. A method comprising:
receiving, from a payment processing device, an integration data object associated with a payment processing service being carried out by a payment processor device, the integration data object being configured to initiate or facilitate a communication between the payment processor device and a client device, the integration data object comprising one or more of: security layers of the payment processing service, protocols of the payment processing device, integration requirements of the payment processing device, target functionalities of the payment processing device, an account statement associated with the client device, an invoice associated with the client device, or a bill associated with the client device;
determining, based at least upon the integration data object, based at least in part on an integration machine learning model, one or more integration features associated with the integration data object, the one or more integration features comprising one or more of: a predicted application programming interface (API) model type, a country in which the payment processing device or the client device is operating, computer language capabilities associated with the payment processing device or the client device, data structure requirements associated with the payment processing device or the client device, or system protocols associated with the payment processing device or the client device;
generating, based at least in part on the one or more integration features associated with the integration data objection, an API model corresponding to the integration data object;
generating an API generation data object corresponding to the API model; and
sending the API generation data object corresponding to the API model to the payment processing device for execution by the payment processing device to generate an API for communication between the payment processing device and the client device.