4/20/21

- development environment
- scratch files
	- can we talk to the device?
	- can we do the other transactions - hardcoded
	- can we make it more dynamic? - later on
- they have people who can help (devs)
- they already sell these systems
- we have the api docs
- on the dashboard - what goes there and what is the plan
- based out of canada - but wanting to go into a bigger rollout - expanded market - also in the US
- they have a desktop model that is selfsustained - dosen't connect to anything - no backend POS
- both cash coming in and cash going out... invoices, deposits, expenses, and other payouts
- api/json integration
- push to other cash verticals - they have over 100+ salespersons
- even venture capital cash advances - mini or small loans
- we (adilas) would be the backend software for their device
- these devices are $11K plus service fees $10K
- they are going to offer service plans and monthly options
- possible opportunities
- we need to put them on the 3rd party solutions page
	- we may want the ability to turn on the different sections
		- invoices, bill pay, deposits, expenses, etc.
- we could sell some of our other services to the client who use this
- called paypod
- we looked over some documentation
	- there are pages and pages... what is the MVP (minimal viable product)
	- maybe ask them to help us figure out the MVP
- this could be a multiple relationship - one or more boxes per cash box
- we may need to keep track of virtual cash draws - multi registers
- the developer is Aaron Stone - contact - Cory and Steve have the contact info
- get Bryan and Aaron hooked up - what's the plan and what do we do first?
	- do a deep dive and get Bryan, Aaron, and Brandon on a meeting
	- get some code samples from there - if possible
- Charge $5K to get things started. Then start chipping away at that and bill accordingly
- both coin and note recyclers (two different engines or pieces)
- is there a sandbox or a simulator type thing? web or real device
- we may end up using some sort of AJAX and JQuery type approach - quick, small calls, without refreshing the pages
- we will need to build in some pretty deep error handling, reset, start over, cancel, etc.
- lots of cases - power out, loss of connection, not enough change, other problems
- first plan - read the docs - say 3 hours or so, write up some questions, then let's reach out Aaron