US-20260126981-A1 - AUTOMATED UPDATING OF COMPUTING CODE FOR SOFTWARE PLATFORM INTEGRATIONS WITH COMPUTING SERVICES

US20260126981A1US 20260126981 A1US20260126981 A1US 20260126981A1US-20260126981-A1

Abstract

There are provided systems and methods for automated updating of computing code for software platform integrations with computing services. An online transaction processor or other service provider may provide computing services and platforms to entities including merchants for electronic transaction processing and other account services. To provide for code integrations of the computing services with software platforms, the service provider may provide a tool where merchants may update legacy code integrations of the computing services on their software platforms to new computing code for new code integrations, such as to facilitate the use of new APIs, endpoints, and the like. The tool may provide mappings for legacy code parameters to new code parameters, which may each be associated with code limitations in the legacy code and new code integrations. Further, the tool may provide an automatic converter of the legacy code to the new code using these mappings.

Inventors

Janani Chandiran
Hui-Tsung Liang
Robert Thomas McGovern

Assignees

PAYPAL, INC.

Dates

Publication Date: 20260507
Application Date: 20241104

Claims (20)

1 . A system comprising: a non-transitory memory; and one or more hardware processors coupled to the non-transitory memory and configured to execute instructions to cause the system to: detect a software integration of a software platform of a merchant with a computing service associated with a service provider; determine information associated with the software integration and the merchant, wherein the information is associated with computing code being used for the software integration and an account of the merchant; convert the computing code to new computing code using a code transformer and based on one or more mappings of input parameters associated with the computing code to new parameters of the computing service after one or more changes to the computing service; generate a new software integration for the software platform of the merchant with the computing service based on the new computing code; and output the new software integration to the merchant via a user interface.
2 . The system of claim 1 , wherein detecting the software integration comprises: receiving a request to access an interface of a service that migrates the software integration to the new software integration; and determining the software integration using a tool that retrieves account information for the account of the merchant and executes application programming interface (API) calls to a merchant API of the software platform of the merchant.
3 . The system of claim 1 , wherein the software integration comprises a legacy software integration that utilizes at least one of a past software development kit (SDK) or a past API specification for API request and response parameters previously used by an API of the computing service, and wherein the new computing code, when executed, updates the computing code based on at least one of an updated SDK or an updated API specification.
4 . The system of claim 3 , wherein the updated API specification utilizes one or more representational state transfer (REST) endpoints associated with a REST API for the computing service.
5 . The system of claim 1 , wherein each of the one or more mappings comprises one of the input parameters for a legacy API call structure mapped to one of the new parameters for a new API call structure, and wherein the one of the input parameters is associated with a legacy code limitation and the one of the new parameters is associated with a new code limitation.
6 . The system of claim 5 , wherein the legacy API call structure and the new API call structure are associated with at least one of an endpoint or a data object, and wherein the new code limitation provides a notification of a change or a warning based on the endpoint or the data object specified by the new API call structure.
7 . The system of claim 1 , wherein the instructions are further configured, when executed, to cause the system to: call an API of the code transformer based on the information, wherein calling the API includes requesting the code transformer convert the computing code to the new computing code using the one or more mappings and a sample of an API call for the software integration.
8 . The system of claim 1 , wherein detecting the software integration is based on a request from the merchant via a chatbot associated with the code transformer, wherein the information is determined, in part, from the merchant during a chat session between the merchant and the chatbot, and wherein outputting the new software integration to the merchant is via the chatbot.
9 . The system of claim 1 , wherein converting the computing code to the new computing code is further based on an API call structure provided by the merchant for the software integration.
10 . A method comprising: determining a first software integration of a platform of an entity with a computing service associated with a service provider based on a request to update the first software integration, wherein the first software integration is associated with first computing code for first application programming interface (API) calls to a first API of the computing service previously used by the platform; determining account information for an account of the entity, wherein the account information indicates one or more usages of the computing service on the platform; generating second computing code that, when executed, updates the first computing code for second API calls to a second API of the computing service using a code transformer and based on one or more mappings of API parameters associated with the first API to the second API; and communicating, to the entity, the second computing code that enables a second software integration.
11 . The method of claim 10 , wherein each of the one or more mappings of the API parameters comprise a first API parameter associated with a first code limitation mapped to a second API parameter associated with a second code limitation.
12 . The method of claim 11 , wherein the first code limitation and the second code limitation comprise computing code that, when executed, enable the first API calls and the second API calls, respectively, to the computing service.
13 . The method of claim 10 , wherein the code transformer generates the second computing code by converting first data in API fields in the first API calls to second data in the API fields for the second API calls.
14 . The method of claim 10 , wherein the determining the first software integration is performed using a detection tool, and wherein the method further comprises: executing, using the detection tool, one or more third API calls to the platform of the entity.
15 . The method of claim 14 , wherein the one or more third API calls are used to detect the first software integration of the platform with the computing service.
16 . The method of claim 10 , wherein the first software integration comprises a legacy integration using legacy code for the computing service, and wherein the second software integration is utilized to update the legacy code to new code currently utilized with the computing service.
17 . The method of claim 10 , wherein the communicating the second computing code to the entity is performed using at least one of a user interface or a chatbot provided by the service provider to the merchant.
18 . The method of claim 10 , wherein the generating the second computing code is further based on an API call structure provided by the merchant for the second software integration.
19 . A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising: receiving a request for software integration of a platform of a merchant with a computing service associated with a service provider, wherein the request identifies first computing code for first application programming interface (API) calls to an API of the computing service, and wherein the software integration changes the first computing code to second computing code for second API calls to the API; determining a mapping of a first API parameter for the first API calls to a second API parameter of the second API calls, wherein the mapping identifies a first code limitation for the first API parameter and a second code limitation for the second API parameter; generating the second computing code associated with the second API calls based on the mapping; and communicating, to the merchant via user interface viewable by the merchant, the second computing code that enables the software integration.
20 . The non-transitory machine-readable medium of claim 19 , wherein prior to the receiving the request, the operations further comprise: populating the user interface with a plurality of current software integrations of the merchant with a plurality of computing services of the service provider.

Description

TECHNICAL FIELD The present application generally relates to computing code updates of software integrations, and more particularly to providing an automated tool and interface for updating legacy code integrations of software platforms with computing services. BACKGROUND Online service providers may offer various services to end users, merchants, and other entities. This may include providing computing services through different software applications, websites, platforms, and resources, such as those that may be involved with digital transaction processing. For example, computing services may include those used to process transactions through electronic transaction processing data flows, services, and other computing resources. Further, the service provider may provide and/or facilitate the use of applications and websites for online payments, peer-to-peer (P2P) transfers, and/or marketplaces to different entities including merchants. Establishment and use of these computing services require that merchants and other entities implement computing code for application programming interface (API) calls and other operations to be executed with these computing services and their APIs. However, a service provider may have many merchants, partner platforms, customers, and other entities that may be integrated with the service provider's computing services, which may utilize legacy patterns of executable computing code from past, previous versioned, or legacy software development kits (SDKs) and APIs. Internal teams of the service provider may not have a central system and tool that provides visibility into the integration patterns and code used by these entities to make informed decisions on guiding the entities to the latest tools, computing code, APIs, and services offered by the service provider. As such, there exists a need for a more streamlined and accessible platform and tool that automates computing code updates from legacy computing code to new computing code that allows for use of the latest computing services and their implementations with the service provider. BRIEF DESCRIPTION OF THE DRAWINGS FIGS. 1A and 1B are block diagrams of networked systems suitable for implementing the processes described herein, according to an embodiment; FIGS. 2A and 2B are exemplary diagrams of a detection tool for detection and presentation of integration patterns and code utilized by software platforms with corresponding updates available for new computing code, according to an embodiment; FIGS. 3A and 3B are exemplary diagrams of a code transformation tool that transforms legacy computing code for integrations of software platforms with computing services to new computing code, according to various embodiments; FIG. 4 is a flowchart for automated updating of computing code for software platform integrations with computing services, according to an embodiment; and FIG. 5 is a block diagram of a computer system suitable for implementing one or more components in FIG. 1, according to an embodiment. Embodiments of the present disclosure and their advantages are best understood by referring to the detailed description that follows. It should be appreciated that like reference numerals are used to identify like elements illustrated in one or more of the figures, wherein showings therein are for purposes of illustrating embodiments of the present disclosure and not for purposes of limiting the same. DETAILED DESCRIPTION Provided are methods for automated updating of computing code for software platform integrations with computing services. Systems suitable for practicing methods of the present disclosure are also provided. Conventionally, during setup of an account and software platform for use and integration with computing services provided by a service provider, merchants and other entities may onboard with the service provider and implement computing code for cross-platform API calling, communications, and service usage. For example, a merchant may onboard to obtain access to accounts and computing services and utilize corresponding services during the course of their business or other interactions with customers, clients, and the like. This may include accessing computing service setups including software development kits (SDKs) and SDK setup/documentation, API call configurations and samples, API documentation and call structures, code snippets and packages, and other data for code integrations of the service provider's computing service(s) with the merchant's software platform. Other software platform setups may include code configurations and integrations for applications and/or websites. However, the service provider's computing architecture may evolve over time as new computing services become available, code and processors become updated or upgraded, new or updated APIs are released, and the like. Merchants and other entities would be required to manually search for and locate these new integrations and code for com