|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||||||||||||||||||
|
|
|
Pink
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Uploaded Media/Content & Other Files
(4)
|
||||
| Media Name | File Type | Date | Description | |
| usaepay_emv_chip_overview.mp4 | Video | 12/1/2020 | This is a recording between Eric and Brandon going over ideas for the EMV chip reader stuff for USAePay Wi-Fi chip reader. 28 Minutes. | |
| PIC Middleware and Elavon ICT 250 Setup Guide_V 1.0.1.pdf | Doc/PDF | 11/4/2020 | PIC Middleware Setup Guide | |
| PIC WIN App_Second Terminal_API Documentation V 1.2.pdf | Doc/PDF | 11/4/2020 | PIC API documentation | |
| elavon-tecmj_canada.xlsx | Doc/Spreadsheet | 6/25/2020 | ||
|
Notes:
|
|
As of 4/12/21: 4338.45 + 1000 from Brandon? paid 2600 +1500= $4100 so far. Will need to bill again by the end 10/27/2020: Bryan needs to spend no more than 2 hours looking into this project. Dig around and make sure this is correct. Make a scratch file- does this work? If so, then Bryan will meet with Brandon to move forward. *May need hardware to complete. 10/19/20: $200 spent by Bryan. $300 by Alan. $200 by Cory= $700 total (on the wrong project) 9/24/2020: New merchant processing. Starting piece and database piece. ***Please make sure you look at their documentation. You should start with a blank scratch page so you can build this thing to connect to the gateway. This is the first milestone. Please get sign off with Brandon before moving on with the project. If you have any questions, please get with Brandon before starting. Merchant types is the name of the table. Name it, create a path, where do we go to get their gateway? This usually holds some sort of url path they provide in their documentation. https://developer.elavon.com/ Database update needs to be done for this script. Did a similar one here: update_20140311.cfm (this was for paypal) Not running like 3rd party solution. Run it like a normal merchant processor. The next portion is the admin portion- called merchant account settings. Here is url where this starts: https://data0.adilas.biz/top_secret/secure/merchant_home.cfm - where it starts or we do a new assignments The next page requires a password to get into (you may have been here before): https://data0.adilas.biz/top_secret/secure/add_edit_merchant_accounts.cfm?mode=add&id=new&corp=0&name=new - requires a password Text Brandon if you need it. https://data0.adilas.biz/top_secret/help.cfm?id=347&pwd=merchant - need to update this help file so admin users know how to proceed. Then you need to test. You will need to change the parameters: https://data0.adilas.biz/top_secret/secure/test_merchant_settings.cfm?id=67&corp=263&name=000%20Office - this is the account setup and test page... basically a quick ping. This link comes off of the merchant_home.cfm page Go to these pages and search for USAePay per page. Use them as a handrail so you can see all the pages you need to touch. shop/web_payments_action.cfm 6/25/2020: see quote for details |
|
Additional Comments/Notes - Subs (1)
|
||||
| Title/Caption | Date | Time | Done By | Comment/Note |
| Meeting with developer | 2/4/2021 | 5:17 pm | Brandon Moore |
This is here just as a helper... Talking with the developer about some of the project management pieces for this project. It, the original project, twisted and turned quite a few times at the start. That always makes it kinda rocky. Here were a few of the topics that we talked about: - We may need a new corp or new system for testing - currently, they are testing on a live account - One of the first stepping stones or checkpoints is what we are calling scratch out - meaning a scratch file (able to throw it away) from adilas to the credit card device - One we have the scratch out (temp outbound call) completed, we need to build the scratch in - meaning a response back from the device. - After the scratch pages get signed off (yes, I can talk back and forth with the outside device), we need to look internally and take care of a number of known modes or ways that cards are processed. For example: cart mode, invoice mode, multi pay mode, voiding, clearing cart, viewing transactions, etc. We need to touch all of those pieces. - It would really help if we had our own hardware to test with. Currently, the live client has some hardware but we, ad the developers, don't have direct access to it. That has really complicated the local development process. Along with that, we currently only have access to a live account, no testing account was created, extended, and/or setup. That's another variable that needs to be dealt with. - Due to it's age, going back, the plan was only laid out up to building out the scratch files. We really need to get the rest of the thing planned. What is the process from a-z - plan? - On a sad note, if we don't get some of these variables and/or values fixed, we many not even want to keep this project. It's getting kinda bloody. We've already spent tons of time and it had/has some red flags that need to be addressed. - One of the timing issues with this project is the power is outside of the developer's control. He has to coordinate with a systems admin person, another developer to push up code, and a client, all of this just to do a single test. Very inefficient. We need to fix this. Along with that, the process of turning things on/off (just for testing vs live) is very tedious. It involves, turning on/off certain settings, code changes, hardcoded values, pushing files, and then coordination all of the parties. All of those variables are tough to manage. - When we are ready, we need to go over and come up with a number of different scenarios. This is not a straightforward 1, 2, 3 project. Lots of moving pieces. - The last thing to note is the number of emails back and forth... that alone is daunting. We need to figure out who is the main contact and solve some of the other variables listed above, otherwise this project will fail for sure. |