Complete code or improve design of Laravel(PHP) Web Service

I'm looking for any of the following products: - optimization of the current code (arrangement/creation/design of classes) or - completion of the webservice I'm building a Laravel webservice that verifies different types of information against remote APIs (each of these APIs are implemented as plugins). These verifications are part of an e-commerce system intended to scrubb the payer before allowing payment. Important: - Not required to perform real integration with these APIs, except for simple simulations enough to test the system (send request, get response). I will provide most of the simulation tools (i.e.: html forms to make requests to the this webservice, and simulated remote API functions) - Response analysis procedures are simple on this stage, just enough to produce a result for the system to continue. Main steps of the webservice: 1. receives a post request with a bunch of parameters from third party 2. webservice determines which remote APIs it needs to call (scrubbers), and which functions it needs to call (types or scrubber types) 3. iterates through valid scrubbers 4. >>iterates through valid types 5. >>>>prepares and sends request to scrubber 6. >>>>gets result 7. >>>>analyses result 8. at the end of both iterations it will produce a final conclusion of the process and returns it to the requester I will provide the following: - Initial mockup of the application code(mix of source code, pseudo-code, comments) - Database at 90% - xml configuration files at 90% and the classes that will parse and serve these xmls - flowchart of the application (see attachment) - class diagram Some notes: - The scrubbing request may specify the remote APIs to use or not. If no APIs or types of verification are specified the application will determine both by itself (by using the xmls provided). - The webservice works as a black-box, it just receives a bunch of data, and tries to make sense of it. - Each Scrubbers is added into the system as a plugin. The plugin is a collection of classes and xml files that aim to telling the scrubber how to behave. Requirements of the final product: - Proper Laravel/MVC/OOP practices - Great implementation of OOP polymorphism - Stateless implementation (no session variables) - Need to control the transaction process together with database inserts and updates - Need to keep track of all results, for in-process and final analysis of results (maybe together with previous item) - Some parts of the webservice are not intended for full completion, there is some information that is not available at this time, and/or is still under discussion, but this won't stop us from being able to test through the full webservice. This means we won't deal with microscopic issues. My main points of concern: - Proper use of interfaces, abstraction and extension of classes: .ScrubberInterface: Interface of all scrubbers .BaseScrubber: wrapper scrubber class that instantiates the main Scrubber classes .Iovation and AquityTec main Scrubber classes that implement the interface .IovationScrubber and .AcuityTecScrubber that Extend Iovation and AcuityTec classes - proper handling of shared clases: .I don't like the way I'm passing arround the ScrubberRresultHandles, there most be a more elegant and clean way to do this .I use ScrubberResultHandles to keep results and data in one place. .check use ScrubberDataHandler and ScrubberDataHandlerResponse, and their relationship with ScrubberResultHandles .Similar to ScrubberResultHandles need to keep track of transactional data (like header_id, journal_id, transaction_id, token id, etc.) - need to make the "id" available throughout service request (the $id is part of the original url, in [login to view URL]: "Route::post('scrubb/{id}', 'ScrubberController@Index');") Current code is here: -app/Http/Controllers/[login to view URL] -app/Http/[login to view URL] -app/Scrubber/*.* -app/Scrubber/plugins/*.*