Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Pink
Assigned To: Alan Williams
Created By: Cory Warden
Created Date/Time: 8/5/2020 12:41 pm
 
Action Status: Completed
Show On The Web: Yes - (public)
Priority: 0
Finished/Done: Yes - 5/12/2021 9:18 am
Finished/Done By: Cory Warden
Budgeted/Estimated Value: 2,000.00  
Actual/Real Value: 15,000.00   [donate]
Invoice/Quote Status: Blank (n/a)
General Amount: $0.00
 
Time Id: 1845
Template/Type: Community Funded Projects
Title/Caption: EMV Chip Integration
Start Date: 8/5/2020
End Date: Unknown... (open or blank)
Total Time: Unknown... (open or blank)
Target/Due Date: 8/5/2020
Main Status: Active

Sorry, no photos available for this element of time.


Notes:
As of 4/13/21: $13,709.90
As of 2/26/21: Eric wrote the code and it is in code review by Alan. Should be finished with review this week.
Then back to Eric for testing.
8/25/2020: As of today, chip reader is en route to Alan's so he will have that for setup and testing.

Alan asked to add this link to the project:
Sent from the client:

Here is the link to Usaepay developers sandbox system login info. Hope it helps you. Are you using java script to call API?
Please call me @ 303-506-7088 I will explain you in detail. 


Developer Portal

Password : Highland1234

Usaepay Sandbox


User name : highlandvinyards
Password : Highland1234


Generating an API key: 

1. Click on settings
2. Click on API keys
3. Click on +Add API Key
4. Provide a name
5. Provide a Pin (if required)
6. Click on Save

The sandbox server is a complete replica of the production environment with a few exceptions:

It is self-contained and will not send any data to outside processing platforms (Visa, MC, or any banks). Charging a "live" credit card will not result in a charge showing up on the cardholder's bill.
While "live" credit cards will work on the sandbox server,  it is recommended that you use the test card numbers. A list of testcards can be found in the developer's center.
The sandbox is designed for testing functionality,  and is not a load testing environment. Transaction throughput is intentionally throttled.
The transaction database is cleared every few months.


Direct any questions regarding the sandbox to sandbox@usaepay.com

Here is a link to our developer center: https://sandbox.usaepay.com/_developer/app/login SOAP WSDL’s and REST Endpoints are generated here. 

Please don’t hesitate to reach out if you need assistance. Here is a link to our developer page: https://help.usaepay.info/developer/  for examples and to help you get started.


8/5/2020: The second project was the EMV chip integration project. This project got to the point of where I got the go ahead to order the card reader and then they pulled me off because they weren't getting many people asking for it, so it has been sitting for over a year now. Still no card reader and zero development has been done. As far as project timeline goes, once I have a card reader and test card, it shouldn't take too long. Typically there are 3 stages:

  1. Get the card reader setup - biggest unknown. Should be quick, but some of the other integrations I did took close to 50 hrs to figure out what the heck was wrong with the card reader connecting to their software. My guess and hope would be an hr or 2.
  2. API integration - my guess would be $500-$750 (10-15 hrs).
  3. Certification - we will have to go through a series of tests with USAePay to verify what we sent and got back from them is the same which usually takes a couple hours.
So I would say it would fall in the range of 13 - 20 hrs to complete the project, but in my experience these integrations tend to take a little longer because it usually take a day or 2 to get responses back from the merchant provider and then several days if they have to send new cards/hardware.

If things super smooth and we have no issues it wouldn't surprise me if it was done in 8 hrs, but I have yet to experience that :)