System and method for multi-level container sequencing

1. A system for user-based customization of a transaction product comprising:

a network-connected product configuration computer comprising a processor, a memory, and a first plurality of programming instructions, the first plurality of programming instructions, when executed by the processor, cause the processor to:

create a plurality of products corresponding to an electronic wallet, each product comprising, at least one product account, each product account associated with one type of value unit of a plurality of value units that can be calculated to have at least one exchange rate;

receive a plurality of connections, over a network, from a plurality of partner user devices;

receive a plurality of connections, over the network, from a plurality of external services;

generate, by the product creator, a graphical user interface, the graphical user interface displayed on a graphical display associated with a first partner user device, of the plurality of partner user devices, the graphical user interface operable to:

configure instrument product data;

submit change requests, the change requests associated with, at least, a plurality of limitations;

receive, at the product creator, the instrument product data, from the graphical user interface of the first partner user device, the instrument product data defining the creation of a first product and comprising configuration, the configuration comprising the plurality of limitations defining limits for at least one electronic transaction, the at least one electronic transaction associated with at least one external services wherein the plurality of limitations comprise, at least, an allowed quantity, at least one allowed geography, blocked external services, and a velocity;

wherein at least one limitation, of the plurality of limitations, is associated with the at least one electronic transaction;

a transaction product computer comprising a processor, a memory, and a second plurality of programming instructions, the second plurality of programming instructions, when executed by the processor, cause the processor to:

receive a plurality of connections from the plurality of external services;

receive, from the first partner user device, a first predefined sequence to determine an order of usage for the at least one product account;

send the first predefined sequence, the at least one product account, and a cumulative quantity of the plurality of value units associated with the at least one product account, to the graphical user interface associated with the first partner user device, the graphical user interface operable to enable the at least one product account to be customized through a toggle that prioritizes each value unit corresponding to at least one electronic transaction type to be at least one of exchanged, withdrawn or used for purchases;

receive the at least one electronic transaction from a first external service of the at least one external services;

match a value unit type of the at least one electronic transaction with a value unit type of the at least one product account within the predefined wallet sequence;

limit the at least one electronic transaction based on the at least one limitation;

receive, from the first partner user device, a customization for the at least one matched product account;

create a secondary sequence comprising the customized at least one matched product account, the second sequence determining an order of usage of the customized at least one matched product account, wherein the order of usage of the customized at least one matched product account is based on a sequence of the customized at least one matched product account consistent with the order of usage defined within the first predefined sequence, wherein the secondary sequence is transformed into at least one application programming interface (API) used to create multiple utilization products for the first partner user device and other partner user devices;

create a utilization product defining an order of usage for processing the limited at least one electronic transaction based on the value unit type of the at least one electronic transaction, the order of usage determined by a sequence of: the customized at least one matched product account from the secondary sequence followed by remaining product accounts from the first predefined sequence; and

display the utilization product on the graphical user interface of the first partner user device.

2. The system of claim 1 , wherein the instrument product data comprises a plurality of parameters associated with the first partner user device.

3. The system of claim 2 , wherein the at least one limitation further comprises risk data, and wherein the second plurality of programming instructions when executed by the processor, cause the processor to:

limit a one time, one day, or seven-day:

withdrawal amount;

purchase amount;

adjustment amount;

refund count; or

refund amount;

limit a number of pin failures;

limit blocked categories; or

any combination thereof.

4. The system of claim 1 , wherein the graphical user interface is operable to submit change request for limiting transaction on a per-transaction basis for the at least one electronic transaction.

5. A computer-implemented method for user-based customization of a transaction product comprising:

creating, at a network-connected product configuration computer, a plurality of products corresponding to an electronic wallet, each product comprising, at least one product account, each product account associated with one type of value unit of a plurality of value units that can be calculated to have at least one exchange rate;

receiving, at the network-connected product configuration computer, a plurality of connections, over a network, from a plurality of partner user devices;

receive, at the network-connected product configuration computer, a plurality of connections, over the network, from a plurality of external services;

generating, by a product creator, a graphical user interface, the graphical user interface displayed on a graphical display associated with a first partner user device, of the plurality of partner user devices, the graphical user interface operable to:

configure instrument product data;

submit change requests, the change requests associated with, at least, a plurality of limitations;

receiving, at the product creator, the instrument product data, from the graphical user interface of the first partner user device, the instrument product data defining the creation of a first product and comprising configuration, the configuration comprising the plurality of limitations defining limits for at least one electronic transaction, the at least one electronic transaction associated with at least one external services wherein the plurality of limitations comprise, at least, an allowed quantity, at least one allowed geography, blocked external services, and a velocity;

wherein at least one limitation, of the plurality of limitations, is associated with the at least one electronic transaction;

receiving, at a transaction product computer, a plurality of connections from the plurality of external services;

receiving, at the transaction product computer, from the first partner user device, a first predefined sequence to determine an order of usage for the at least one product account;

sending, by the transaction product computer, the first predefined sequence, the at least one product account, and a cumulative quantity of the plurality of value units associated with the at least one product account, to the graphical user interface associated with the first partner user device, the graphical user interface operable to enable the at least one product account to be customized through a toggle that prioritizes each value unit corresponding to at least one electronic transaction type to be at least one of exchanged, withdrawn or used for purchases;

receiving, at the transaction product computer, the at least one electronic transaction from a first external service of the at least one external services;

matching, by the transaction product computer, a value unit type of the at least one electronic transaction with a value unit type of the at least one product account within the predefined wallet sequence;

limiting, by the transaction product computer, the at least one electronic transaction based on the at least one limitation;

receiving, at the transaction product computer, from the first partner user device, a customization for the at least one matched product account;

creating, by the transaction product computer, a secondary sequence comprising the customized at least one matched product account, the second sequence determining an order of usage of the customized at least one matched product account, wherein the order of usage of the customized at least one matched product account is based on a sequence of the customized at least one matched product account consistent with the order of usage defined within the first predefined sequence, wherein the secondary sequence is transformed into at least one application programming interface (API) used to create multiple utilization products for the first partner user device and other partner user devices;

creating, by the transaction product computer, a utilization product defining an order of usage for processing the limited at least one electronic transaction based on the value unit type of the at least one electronic transaction, the order of usage determined by a sequence of: the customized at least one matched product account& from the secondary sequence followed by remaining product accounts from the first predefined sequence; and

display the utilization product on the graphical user interface of the first partner user device.

6. The method of claim 5 , wherein the plurality of limitations further comprises, at least, risk data, the risk data comprising:

a one time, one day, or seven-day:

withdrawal amount;

purchase amount;

adjustment amount;

refund count; or

refund amount;

a number of pin failures;

blocked categories; or

any combination thereof.

7. The method of claim 5 , wherein the graphical user interface is operable to submit change request for configuration on a per-transaction basis for the at least one electronic transaction.