US 12,333,468 B1
Extensible custom configurability for stateful API resources
Ji Huang, Bothell, WA (US); and Alexander Thiemann, San Francisco, CA (US)
Assigned to STRIPE, INC., South San Francisco, CA (US)
Filed by STRIPE, INC., San Francisco, CA (US)
Filed on Oct. 6, 2021, as Appl. No. 17/495,713.
Int. Cl. G06Q 10/0631 (2023.01); G06F 9/451 (2018.01); G06F 9/54 (2006.01)
CPC G06Q 10/06315 (2013.01) [G06F 9/451 (2018.02); G06F 9/547 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method for facilitating customized functions and debugging of the customized functions via script execution objects as a controlled interface through which a platform shares selective execution data related to a custom function's execution, the method comprising:
providing, by a server associated with a commerce platform to a merchant server, access to a first resource object that includes logic for performing a function associated with a resource of the commerce platform and customization logic to support a custom function version;
in response to receiving, from a customer device associated with the merchant server, a request to customize the function, providing, by the server to the customer device, a function signature specifying a return value and input arguments available for the custom function version, the input arguments being parameters associated with a subset of a set of application program interfaces (APIs) of the commerce platform;
in response to providing the function signature to the customer device, receiving, by the server from the customer device, a script (i) generated based on the function signature and (ii) defining the custom function version that requires access to a second resource object of the commerce platform, the second resource object not being accessible via the function;
in response to receiving the script, providing, by the server to the custom function version, read-only access to the second resource object of the commerce platform; and
in response to executing the custom function version, storing, by the server, (i) execution loglines corresponding to execution of the custom function version to an execution log that is not accessible to the merchant server and (ii) a subset of the execution loglines to a script execution object that is accessible to the merchant server while the execution log remains inaccessible to the merchant server to enable debugging of the custom function version.