Payment & Scheduling

##Outline Outlined below are all of the things our portion of the projects needs to run, and all the things groups can expect our portion to do.

1. What we need to be sent:

   1. The winning contractor ID, the client ID of the buyer, and the total cost of the job.

      1. May be in the form of am XML file with all of the required information.
      2. If in the form of XML we just need to know how you plan to structure it so we can parse it correctly.
      3. If not let us know how you plan to send it so we can set it up to read correctly
         • I believe the easiest way to do this since the payment/sched is part of the main unit would be to just pass objects around. Build an class in the common module with all the data fields you need to operate, and we'll import your class, fill in the data and pass of a reference to your client. Your communications with the DB would be through the networking team, and I believe they're planning on receiving objs and translating that to XML to ship to the DB. So none of the clients should be build their own XML... unless I'm mistaken of course. -That sounds cleaner and much more organized! I agree with this method, Paul.

2. Our part will then do the following:

   1. Bring up a payment window that the client will use to pay
      1. Payment may be done all at once or a payment plan can be set up to pay over time
      2. If the latter we need to know whether that information will be stored in the Database or in the client/contractor information pages so we know who to send the updated information to. As an example we would send something like a date the next payment is due and for how much.
   2. Will increment the amount in the contractor’s account of the job if paid all at once
      1. Same as above we need to know what part of this project the account info is stored so we can sent the required updates to that info
   3. Will be able to have an automatic payment so the money will come out of the clients account on the specified date.
      1. Will need an error check to ensure that the required money is in the Clients account or it will send a message to the client telling them they do not have enough.
      2. (may have a reschedule option if needed)
   4. The payment system will decrement the required amounts from the client’s account.
      1. As stated earlier this can happen at the time of purchase or can happen if we wanted to do a scheduling system for paying parts at a time.
   5. A scheduling window will appear with a choice of Month, date, and time for the client to decide when the contractor will come out for the appointment.
   6. We decided to go with a tabbed window display. Below are examples of the window the client will see:

3. Groups can expect our part to send the following:

   1. An update for fields regarding money or payment dates.
      1. Need to know where this information has to be sent
      2. Can send this in an XML file if needed. If not we need to know how to send it.
   2. If client does not pay in full we will have it set up to pay automatically on specified date.
      1. First date will be determined at the time of payment.
      2. Subsequent dates will be done either one at a time or can be set up for automatic payment. (Once a month, every other week, etc.)

Let us know if you group needs anything. Our group lead is Emily Novak, email: novak.17@wright.edu

##Questions?