Quantcast

SmartPay Introduces Payment Gateway Log for Added Convenience

January 3, 2013

SmartPay is excited to announce the addition of a Payment Gateway Log to their electronic invoicing solution. http://www.gosmartpay.com

Fargo, ND (PRWEB) January 02, 2013

SmartPay is excited to announce the addition of a Payment Gateway Log to their electronic billing and invoicing solution.

The Payment Gateway Log is a feature within SmartPay that records all transactions that have been submitted through a company´s payment gateway. SmartPay merchants can see if transactions have been approved or denied and if there is an error code, what the code means.

The report defaults to failed transactions over the last 30 days, but all transactions are recorded and stored in the system. Specific transactions can be located through detailed filter options that modify the transaction criteria, which helps when troubleshooting specific customer issues.

“This new feature gives SmartPay merchants the tools needed to help their customers as quickly and efficiently as possible, without having to seek outside assistance from our team or their Gateway Provider,” said Karn Jilek, Director of Operations at SmartPay.

SmartPay merchants have full access to the Payment Gateway Log now and have been mailed the new SmartPay User´s Guide, which includes a list of their payment gateway´s error codes.

For more information about SmartPay, please visit http://www.gosmartpay.com.

SmartPay is a powerful, flexible, enterprise-level online billing system designed to save your business time and money. SmartPay is a Cloud Based Electronic Bill Presentment and Payment Sass Solution suitable for medium to large businesses. It allows an increase in cash flow by sending large batches of invoices and statements electronically while increasing accuracy and customer satisfaction by allowing customers to pay online easily and securely. For more information about SmartPay, please visit http://www.gosmartpay.com or call 1.866.667.4277. Twitter @_SmartPay_

For the original version on PRWeb visit: http://www.prweb.com/releases/prweb2013/1/prweb10279049.htm


Source: prweb



comments powered by Disqus