As of July 31st, 2020, you can use Authorize.net with CP Pay to take card-present transactions. We have tested our integration with the BBPOS Chipper. The Tech ID Augusta will not work. See our getting started article and hardware overview article for more information.
Please note, Authorize.net does NOT support all processors with in-person (card-present) transaction. See their FAQ for more information.
Although CP Pay has integrated to Authorize.net's EMV offering, it does not automatically mean that you will be able to leverage it. Authorize.net has limited processor support. Please see their FAQ for the latest information.
These settings can be found in Authorize.net’s settings under Settings > Transaction Form Settings > Payment Form > Form Fields. These settings control which fields are required by the API but do not control appearance.
There is a limitation in Authorize.net's API that does not allow us to pass in personal information to pre-fill the form when adding a card outside of a transaction.
Authorize.net only allows 10 payment methods to be saved under one customer. You can confirm this by looking up the customer in Authorize.net's Customer Information Manager
No, Authorize.net does not allow a refund greater than the amount of the original transaction. Over-refunding will give you an error that states, "5001: The sum of credits against the referenced transaction would exceed original debit amount."