Captain’s Log
Star(tup)Date: 0032
What we did today
Kept testing variations on the code until I found what was wrong when I put all the payment processor registration components together.
Then, did some commenting and cleanup of the code structure and connected it all the way into the givby database. We’re blasting through!
Next, I’ll package the presentation for registration success and failure, and add in the oauth code that I made in the beginning to add user access tokens.
Then, on to payments! Starting to come out on the other side.

Captain’s Log
Star(tup)Date: 0031
What we did yesterday
Did some more work on the payment processor registration form processing. All the components tested out well, but ran into a snag putting them all together.
Decided to give it a break for a while. Sometimes, coming back to problem code with a fresh start helps you discover what is wrong.
Did some updates for my Save-A-Vet peace dawgs. We now have complete data on MWD (military working dog) euthanasia for the past five years.
(Source: givby.com)
Captain’s Log
Star(tup)Date: 0030
What we did today
Randi and I took Allen to the Northwestern football spring scrimmage today for his birthday. Had a great time — the game was fun, the atmosphere great, saw lots of old friends & former players, and tailgated with him after.
Really exhausted from four straight weeks of givby. Kind of a rest and recovery day. But did manage to integrate Facebook API data into our payment processor API registration form. Still on track to go live by draft day!

Captain’s Log
Star(tup)Date: 0029
What we did today
Tested the payment processor registration form on IE & Firefox, and adjusted code for these browsers. Then moved on to finish rigorous and user-friendly server-side validation of payment registration form data. Grinding few days. Also did a bit more social media chumming. Getting really close.
(Source: givby.com)
Captain’s Log
Star(tup)Date: 0027
What we did yesterday
Finished the design and presentation coding of the payment processor registration form to make if feel simple, safe and inviting to users.
Getting set up for payments will be their single biggest hurdle.

Captain’s Log
Star(tup)Date: 0026
What we did yesterday
Laid out and set up the form page for payment processor registration. This included making decisions on how to tell users about the payment processor and how to organize and present all the data their API requires. Even though I am not a designer, this project still requires some design consideration to give users a clean, credible, consistent look for them to feel comfortable moving forward.
Also did a bit more social media chumming for givby.com, listened to an NPR show on “The Rise of Micro-Labor” for my ChoreMart buddies, and worked with my Save-A-Vet.org dawgs on planning their certified trainer program.
Captain’s Log
Star(tup)Date: 0025
What we did yesterday
Got payment processor API working for new user registration. This is one of the most complex endpoints in their API — using PHP post stream, JSON, and a rich data set. On to integrating this with a web form and our oauth process.

Captain’s Log
Star(tup)Date: 0024
What we did yesterday
Visited Allen and his fellow residents at the Bayside Terrace home for Easter, along with our two dogs who were quite a hit with everyone there.
Did only a few minutes work on givby, but very valuable minutes — got a clearer grasp of the payment processor API structure and methods.
(Source: givby.com)
Captain’s Log
Star(tup)Date: 0023
What we did yesterday
Got payment processor API working through access token acquisition. Hooah!
