all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||||||||
|
|
|
Blue
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
Currently, all credit card transactions are limited to positive values. We have had a few requests to allow credit cards to be credited or refunded. This is money flowing out of the company. This is allowed by the different gateways, but we have purposely not included any logic and/or permissions for this type of transaction. Currently, the user has to login to their gateway and do the reversal (credit or refund) from the gateway's virtual terminal. They then record the authorization code inside of adilas. The problem lies in rules for doing the reversal. This could be who has access?, what cross checks must be in place?, is there a time span problem?, and how do we limit this type of transaction? Do we tie it to the original invoice or how do we make the connection? It could be done with permissions and/or corp-wide settings. Our current solution is not supporting this transaction type and that is how we are dealing with it. At some point, we may need to add this as a permission and/or a feature. By avoiding it, it makes it easier for us, but it puts the burden on our users (manual steps and possible bottleneck). We may need to rethink this... |