Skip to content
Cameron Hetzler edited this page May 9, 2020 · 1 revision

What is SMEX?

SMEX is the backend logic for a larger project. In essence, this acts as the interface for the database that this logic controls.

Then what is this project?

I am creating a service that will allow people to buy into a subscription plan that you are paying for and manage the billing of invoices to everyone so you don't have to remember who has access to the service or what the current price is when splitting between everyone.

How is this supposed to work?

Well, since this is just the backend logic of the service, there will be a front for a user (either you or a 'customer') to select a service that was added into the system and request to buy into it. Once information, like email, is provided and vetted, then a request will be sent to SMEX via a web servlet acting as a RESTFul interface. After some information rangling and when the time comes, an invoice will be created through PayPal's RestAPI using the information stored in the database [SMEXDB] and will be sent out to the emails that were supplied at the beginning. Money that is paid to the PayPal invoices will be sent to the owner of the Bussiness PayPal account's own PayPal account.

Are there any security problems?

To be frank, absolutely. I am always making sure that personal information is secured and behind walls to prevent unwanted people from viewing that information, but there are certainly risks in assuring that you will be paid. There is no way to force someone to pay an invoice and even if there were there are always work arounds to get out of it. I will be having to rely on PayPal and their own systems to make sure that you get the money that you need.

Clone this wiki locally