A method for executing proactive and reactive transaction requests using a communication channel, the method comprising the processor implemented steps of: receiving a transaction request sent by a user controlled transaction engine, wherein the transaction request is a proactive transaction request or a reactive transaction request, wherein for a reactive transaction request, a user responds to an email or an SMS received, via the communication channel, in order to execute the reactive transaction request, and wherein for a proactive transaction request, the user initiates generation of the proactive transaction request by sending an email or an SMS, by communicating via the communication channel, wherein the communication channel comprises an email channel or an SMS channel, wherein the transaction request comprises a user ID, a short code, and for a reactive transaction request also a reply capture ID, RCID, code; and executing the transaction request comprising: checking a validity of the short code in the transaction request by checking presence of the short code in a database and presence of a business logic class mapped with the short code and sending an error message if the short code is invalid, else when the short code is valid, checking presence of the RCID code in the transaction request; and checking validity of the RCID code in the transaction request if the RCID code is present in the transaction request by checking presence of the RCID code in an RCID code table, and sending an error message; that the RCID code is invalid if the RCID code is not present in the RCID code table; checking a validity of the user by using the user ID when the transaction request is the proactive transaction request or the reactive request, and sending an error message if the user is invalid, else; fetching a first line of the email body containing one or more action items, by an email parser or fetching the SMS by an SMS parser, and preparing an xml from the first line of the email body or from the SMS; invoking a solution specific API to process the transaction by querying the short code from the transaction request in a database table to fetch a business logic class mapped with the short code; and executing the transaction by executing the business logic class along with the xml and sending a success-failure response to the user indicating a transaction request status. checking a validity of the short code in the transaction request by checking presence of the short code in a database and presence of a business logic class mapped with the short code and sending an error message if the short code is invalid, else when the short code is valid, checking presence of the RCID code in the transaction request; and checking validity of the RCID code in the transaction request if the RCID code is present in the transaction request by checking presence of the RCID code in an RCID code table, and sending an error message; that the RCID code is invalid if the RCID code is not present in the RCID code table; checking a validity of the user by using the user ID when the transaction request is the proactive transaction request or the reactive request, and sending an error message if the user is invalid, else; fetching a first line of the email body containing one or more action items, by an email parser or fetching the SMS by an SMS parser, and preparing an xml from the first line of the email body or from the SMS; invoking a solution specific API to process the transaction by querying the short code from the transaction request in a database table to fetch a business logic class mapped with the short code; and executing the transaction by executing the business logic class along with the xml and sending a success-failure response to the user indicating a transaction request status.