Store Credit card Info

Regarding collection of payment card data required upon approval: For OTC (over-the-counter) customers we will continue to retain data as usual (write it on a post-it note and attach to printed ticket) and for Ship-in customers, I will probably send repair completion notice with payment link (calling customer for payment info or having customer call us is not very efficient, however it is always preferable that we retain payment card info upon approval). The reason we do not take payment upon approval is because camera repairs can take anywhere from a few days to several months, depending on the job, parts availability, seasonal work volume and service level. Therefore, we try to retain payment card info upon approval, then charge the card upon completion of repair, however long it takes. Every camera repair shop that I know of, whether Canon factory service, Nikon factory service or large old-establishment repair shops like Precision Camera in CT or my shop, we all require payment info upon approval and charge upon completion. We can develop our own non-paper system to retain payment card data however, ultimately, it would be preferable if we could capture this data within RD. Payment card tokenization would be a very good way to handle this. OTC customers could swipe their card for data capture. Ship-in customers could provide data upon approval via website or payment link. We would also need a virtual terminal function to manually enter payment card data if needed (in the case of payment card info taken over the phone).