Accepting debit and credit card payments in your firm is a great way to increase cash flow and offer convenient payment tools to your clients. Before you get started it is important to learn the best ways to protect yourself from clients disputing or questioning payments made to your firm. This is typically known as a chargeback and it is when a cardholder calls the issuing bank of their credit card to dispute a transaction listed on their account. At LawPay we want to help our firms protect themselves from day one by collecting the following information from cardholders.
1. Obtain authorization from the cardholder for the specific dollar amount being charged. Authorization means a signature from the cardholder and can be collected on paper or electronically.
2. Confirm the name on the card. If the name is different from your actual client, obtain additional approval from the actual cardholder. This is common in certain practice areas such as family law.
3. When accepting credit card information over the phone or through your website, ensure you have a charge authorization or previous client agreement to charge payments on file.
4. Have clients specifically initial the firm's payment and credit card policies in their client agreements. This specifically shows the client was notified of the firm's payment policies and agreed to them. You cannot take away a client's right to dispute a transaction, however you can disclose the fee for your services as non-refundable and have them initial next to this.
5. If you are accepting payments from relatives or other third parties make sure you have the proper documentation. The authorization form or agreement should include the client name, invoice number and matter number if possible. Obtain signature from the third party to confirm they are accepting responsibility for the payment.
6. Obtain client initials next to any specific cancellation policies included in your client agreements.
This information was taken from LawPay's support forum on January 10, 2017 and may be outdated. For the most updated article and any associated documentation, please click here.