all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Yellow
|
|
|||
|
|||
|
|
|
Notes:
|
|
Merchant Processing available through adilas.biz: Database ideas for merchant accounts: 1. Are they tied to a corp, loc, or bank, or all these? 2. We are currently tied into USAePay and Newtek, do we want to allow for future growth or deal with it when we get there? 3. What about transactions and batches? These are key fields on the remote side. It might be ideal to capture and use them to help with reconciling bank deposits. 4. What if we allowed a feature where the user could view the current batch, pick and choose (create an internal tie between inv. Payment and transaction number), force the batch to close (only the records we want), record the batch number (on the deposit), and create the new deposit. This would be pretty cool. This would keep things all tied together. 5. What about security? The source key and pin key are very important keys to the user’s merchant account. How can I protect myself, adilas, the users, and the companies? This is a big responsibility. 6. Make sure all cc transactions and webservice calls are done over SSL connections. Force it SSL or send to logout. 7. I need to come up with a hash to conceal the source keys and pin values. See part of LTF for some ideas. Tech – Merchant Settings Table & Merchant Types Table (Please see scan in photo gallery) |