Setting up a mtg and Meeting with Clover to see what we need to do to get the ball rolling with the developer account and let them know where we are at with this process.

Emails to Clover trying to get the ball rolling. Meeting with Cory and Steve and made functional video for app. Cannot submit the app live until I get my dev account approved.

Trying to setup mtg with Clover.

Emails have been going to my spam folder, but got email for verification of my developer account. Needs my drivers license and utility bill proving my address and utility bill and gov doc with TIN for Adilas... Got them uploaded into box with conformation emails from Clover.

Building out app live and pulling in all the info needed to submit app for approval. Live needs a functional video of how Adilas works before they will allow me to submit the video.

Emails and updating hours spent working on Clover integration.

Making sure we had everything for the submission and submitted the app for approval.

Sending Clover adilas details and URLs

Looking everywhere on how to make and submit the application submission video that they were talking about. Took forever but finally found it.

Meeting with Cory and Steve and looking at documentation for iFrame to see if we want to incorporate some card not present payments. Looks like we will have to add in a captia if we go that route so think I will skip it for now.

Went back and started testing again and the 500 internal error message is gone so it must have been a Clover server issue. Started going through the submission process for the App and grabbing needed information.

Going through test to verify everything still works with different payment types. Started getting a 500 error and was looking at documentation to see what I needed to do to resolve it. Couldn't see anything that I had changed that would cause the authentication error since I started building out the void/refund piece. Really frustrated. I assume that this is a Clover internal error as the call is being made from the card reader.

Going through docs to see what is needed for submitting the app to see if I am missing anything in the deployment step.

Building out calls for handling voids and refunds. This is a little odd as Clover only holds a void for 24 min instead of a normal batch at the end of the day.

Recording response from clover and testing. Adding in welcome and thank you calls to change display on card reader. Things are pretty much done for taking payments.

Continuing on with pulling in settings and making AJAX call to collect tips and make payments and pushing results to the action page.

Working through the payment process within Adilas. Starting to build out the clover payment page and the AJAX calls to the cloverService.

Meeting with Cory and Steve, then continuing work on card settings. This will need to be worked on later as I only have access to a single device and cannot test this with multiple card readers as this time. All my calls currently are using the card reader in the merchant settings, not from this settings page since they are one and the same.

Working on building out settings page for Clover devices.

continuing work on API calls out for tips, payments, voids, refunds, etc...

Going through API documentation and working on making calls to card reader. Had to download the Cloud pay display app and associate it with my merchant/device before they would work.

Some more DB updates to allow for the settings that we need to work for clover. Doing code review on code written so far.

Meeting with cory and steve. Testing oauth code and making sure things are getting saved and it is passing its validation test.

Now that I can connect to the card reader and get the Oauth stuff done it was time to tie the login process into Adilas. Reading through docs to see if there was any way to allow me to easily know which server and corp I was coming from. Was able to find that I can pass a redirect URL in the oauth 2 call to allow me to redirect to a sub directory, which means I can pass through url vars. Build out landing page from oauth to redirect back to their original server with corp id so settings can be updated and landed back on their homepage/merchant test page, without having to login again.

Meeting with Cory and Steve. Continued work with testing merchant settings to see if credentials worked. Was able to use the device serial number to connect to call to look up all the associated devices with the merchant. This is great progress!

Meeting with Cory and Steve about progress. I think the reason my device call isnt working is because the api code i am storing as a variable is invalid. Working on building out merchant settings to save the auth code and refresh token and dates so I can test if the token is what is wrong with the api calls to the device. Building out the CloverService to automatically check if token is still good and grab a new token using the refresh token if it has expired and updating everything in the merchant settings. Needed to do some database updates as the auth key isn't always the same size.

Got Clover mini associated with my developer account. Still trying to figure out how to get the api call to work with the device keep getting a not authorized error and cannot tell if that is because of the oauth credentials, or if it is something wrong with my call to the card reader.

Working through oauth 2 workflow and planning on how we can use this workflow from all our different servers when we can only have 1 redirect and not knowing which server and corp they were coming from. This is a little frustrating... only thing I can think of is pushing the code and auth key through in the background and force them to login to adilas again but then this loses some of the security if we are passing the key around everywhere just to find out who they are... what if they stop the login process, or switch tabs to login... they have to go through the clover login all over again.

Cory and Steve meeting with Alan on Clover update. Deciding flow and mapping out the new security process.

reading email and going through documentation showing the change from using oAuth v1 vs v2 and working on getting that connection to work.

Reading through email and documentation sent over about getting card reader hooked up to my testing merchant account.

logging  hours and making notes of the process I went through last night to get the app to work.

Went through quite the process, but finally got OAuth to work.

Had to change my 3rd party code to pass me to http instead of https and was able to get the redirect to hit my test page on my local server. When making the api call to get the access token get bad request response with an invalid OAuth credentials message. I went to my app and previewed it in the app market and had the test merchant download the app and opened the app and it would generate the auth code and was able to successfully generate the api token.

I went back to my 3rd Party page and found a link to build an example OAuth Request and noticed it wasn't using the same request as the documentation stated. doc says use oauth/v2/authenticate, but the link from this page uses oauth/authenticate.

After switching that I am able to launch the OAuth and get an Auth Code and in turn make the call to get an API Token from my own generated link to kick the user out to clover to start that process.

Device is still not associated with my account, but I have done the hard part! I sent an email out to Clover contacts to try and get the device connected to my merchant account.

building out a clover test page and reading the clover documentation.

writing the psuedocode in the pages that I will need to update for processing and voiding payments.

Going through documentation to see what I am missing for generating an Auth Code and API Token through the desired process. Emailed Dustin to pass on pieces I would like him to work on in the mean time while I try and get this figured out.

Was able to get access to old account again by resetting my password. Gave up on postman as it still isn't creating any type of handshake. Tried to build out call using API key that I created yesterday but still not getting anything to work. When I send them to the OAuth link, I don't get a redirect back. Getting a little frustrated with this process.

Trying to figure out OAuth process. Going back through documentation. Tried to get calls to work through PostMan. Also got device and installed update and connected to internet. Getting message that it isn't tied to a merchant account. Trying to figure out how to access/setup a merchant account.

Was finally able to figure out the differences in Our Vendor (3rd Party App) account and my testing merchant accounts. Found option to create a merchant API Token. Once I created a token it forced me to add multi factor authentication and it wouldn't let me log into my testing account anymore. Created another developer account so I could still try to get things working in the mean time.

Created Developer account and building out settings. Walking through documentation steps to figure out proper integration flow for us.

adding the table updates for the merchant type Clover.

Emails with Shari to order Clover Mini

Started reading through integration docs that were given in the meeting

Meeting with Jessica and Co going over what the integration will look like. We will be building out a semi integration as we are only going to be doing payments through their devices.

Read through emails and setting up meeting. Reading through integration steps and documentation.