Systems and methods for state machine driven programmable payments
Systems and methods for state machine driven programmable payments are disclosed. A method may include: defining a plurality of base state machines; storing definitions for the plurality of base state machines; receiving, via a user interface, a programmable payment instruction (“PPI”) from a user comprising a PPI definition of a PPI trigger, a PPI condition, and a PPI action; dynamically linking a state in one of the plurality of base state machines to the PPI definition; storing the PPI definitions; receiving a payment instruction; identifying, from the payment instruction, a base state machine and the PPI instruction linked to the payment instruction; creating a PPI-specific state machine definition for the PPI instruction linked to the payment instruction; and instantiating a PPI-specific state machine for the PPI-specific state machine definitions. The PPI-specific state machine calls one of the plurality of base state machines to execute portions of the payment instruction.
1 . A method, comprising:
defining, by a computer program executed by an electronic device, a plurality of base state machines;
storing, by the computer program, definitions for the plurality of base state machines wherein the definitions for the plurality of base state machines comprise a deposit state machine, a withdraw state machine, and a transfer state machine;
receiving, by the computer program and via a user interface, a programmable payment instruction (“PPI”) from a user comprising a PPI definition for each of a PPI trigger, a PPI condition, and a PPI action;
dynamically linking, by the computer program, a state in one of the plurality of base state machines to one or more of the PPI definitions;
storing, by the computer program, the PPI definitions;
receiving, by a payment processor computer program, a payment instruction;
identifying, by the payment processor computer program and from the payment instruction, a plurality of base state machines and the PPI linked to the payment instruction, wherein the plurality of base state machines comprise at least one off-chain state machine for an off-chain interaction associated with the PPI and at least one on-chain state machine based for an on-chain interaction associated with the PPI and wherein identifying the plurality of base state machines is performed based on an amount of off-chain interaction and an amount of on-chain interaction associated with the PPI;
detecting, by the payment processor computer program, an event associated with the payment instruction before instantiating the PPI-specific state machine through the event being consumed by an on-chain application or an off-chain application;
creating, by the payment processor computer program, a PPI-specific state machine definition for the PPI linked to the payment instruction; and
instantiating, by the payment processor computer program, a PPI-specific state machine for the PPI-specific state machine definitions, wherein the PPI-specific state machine is configured to call the plurality of base state machines to execute portions of the payment instruction and wherein state transitions of the PPI-specific state machine emit events that are consumed by an on-chain application or an off-chain application to validate programmability conditions and execute actions.
2 . The method of claim 1 , wherein the plurality of state machines are stored in an on-chain environment.
3 . The method of claim 1 , wherein the plurality of state machines are stored in an off-chain environment.
4 . The method of claim 1 , wherein the definitions for the plurality of base state machines comprise base state machine triggers, base state machine conditions, and base state machine actions.
5 . The method of claim 4 , wherein the state machine triggers are event-based or time-based.
6 . The method of claim 1 , wherein the user interface comprises an ‘if this then that” interface.
7 . A non-transitory computer readable storage medium, including instructions stored thereon, which when read and executed by one or more computer processors, cause the one or more computer processors to perform steps comprising:
defining a plurality of base state machines;
storing definitions for the plurality of base state machines wherein the definitions for the plurality of base state machines comprise a deposit state machine, a withdraw state machine, and a transfer state machine;
receiving, via a user interface, a programmable payment instruction (“PPI”) from a user comprising a PPI definition for each of a PPI trigger, a PPI condition, and a PPI action;
dynamically linking a state in one of the plurality of base state machines to one or more of the PPI definitions;
storing the PPI definitions;
receiving a payment instruction;
identifying, from the payment instruction, a plurality of base state machines and the PPI linked to the payment instruction, wherein the plurality of base state machines comprise at least one off-chain state machine based on an amount of off-chain interaction associated with the PPI and at least one on-chain state machine based on an amount of on-chain interaction associated with the PPI and wherein identifying the plurality of base state machines is performed based on an amount of off-chain interaction and an amount of on-chain interaction associated with the PPI;
detecting, by the payment processor computer program, an event associated with the payment instruction before instantiating the PPI-specific state machine through the event being consumed by an on-chain application or an off-chain application;
creating a PPI-specific state machine definition for the PPI linked to the payment instruction;
instantiating a PPI-specific state machine for the PPI-specific state machine definitions; and
calling the plurality of base state machines to execute portions of the payment instruction and wherein state transitions of the PPI-specific state machine emit events that are consumed by an on-chain application or an off-chain application to validate programmability conditions and execute actions.
8 . The non-transitory computer readable storage medium of claim 7 , wherein the plurality of state machines are stored on-chain.
9 . The non-transitory computer readable storage medium of claim 7 , wherein the plurality of state machines are stored off-chain.
10 . The non-transitory computer readable storage medium of claim 7 , wherein the definitions for the plurality of base state machines comprise base state machine triggers, base state machine conditions, and base state machine actions.
11 . The non-transitory computer readable storage medium of claim 7 , wherein the user interface comprises an ‘if this then that” interface.