Authorize.net
Authorize.net is a payment gateway that provides online processing of bank card payments. Using Authorize.net, you can process card payments online, without any physical swiping. If Authorize.net fits your lending practices and you would like to use the service, it can be configured through LoanPro's integration with Secure Payments. This article explains the process.
Integration
LoanPro—with the integration of our other product, Secure Payments—makes it possible to process credit and debit card payments directly inside LoanPro. Additionally, the integration will return error codes for failed payments, facilitate the reversal of payment transactions, and let you toggle your Authorize.net account between demo and live mode directly within your LoanPro settings.
To use Authorize.net, you will need a merchant services provider; we recommend Select Bankcard.
Add a processor
You can add an Authorize.net processor in either the LMS or Secure Payments.
From LMS
To add your Authorize.net account in LMS, navigate to Settings > Company > Merchant > Secure Payments inside your company account in LoanPro.
To add a new Authorize.net processor, navigate to the Debit/Credit Card tab and select 'Add Processor'.
Here, you will need to enter your credentials. The necessary credentials include your API Login ID and Transaction Key, which Authorize.net will have given you once you sign up and get approved. You'll also need to set a name for your processor and configure a few settings. Here is a breakdown of what each setting does:
Setting | Description |
Sandbox |
This option allows you to toggle your Authorize.net account and a general sandbox account. Authorize.net has a sandbox account and a production account, and these are independent environments. However, you will need to request a sandbox account from Authorize.net if you would like access; it does not occur by default. In addition, credentials for an Authorize.net account are unique to each account. Thus, if you have a production account and you wish to use a sandbox account instead, you’ll need to contact Authorize.net to get a sandbox account with an independent credentials setup. This setting is also located within Secure Payments and lets you indicate the environment in which you desire to point the transactions. |
Test | This option allows you to send transactions to your Authorize.net account without processing the payment. (Transactions will be sent to either a live account or sandbox account, based on the configuration of the Authorize.net account.) This will let you test to see if transactions from LoanPro are being sent to Authorize.net properly. It is also meant to test the configuration and communication between the two platforms. |
Default | This option allows you to set this processor as your default. |
Auto Reversal | This option determines if transactions that are charged back and reversed within Authorize.net are also reversed within LoanPro automatically. |
When finished, click 'Save' to save the processor.
From Secure Payments
To add an Authorize.net processor in Secure Payments, navigate to Processors > Bank Card > Authorize.Net and click the blue plus icon at the top right.
The following information should be entered for the processor:
Field | Description |
Name | This name should distinguish this processor from others you might create |
API Login ID | Your Authorize.net API Login ID |
Transaction Key | Your Authorize.net Transaction Key |
Sandbox | If you choose “Yes”, your payments will be sent to the Authorize.net sandbox account instead of your live account. |
Test Mode | If you choose “Yes”, your Authorize.net account will be set to test mode and your payments won’t actually be processed. |
Version | This is the version of the integration with the Authorize.net API. Choose “V2” for this, as V1 will be deprecated at the end of 2024. |
When you are done, click the blue save button in the top right corner, and the new processor will be saved.
Payment IDs
Once integrated, the LoanPro account number and payment ID are added into the memo line for each payment inside of Authorize.net. This will help you match transactions made in Authorize.net with transactions in LoanPro. If an Authorize.net transaction is posted, you will be able to see both the Transaction ID and Batch ID in Secure Payments as well.
Authorize.net will only accept one incoming transaction per minute with the same amount. If a user attempts to place more than one charge/transaction per minute, Authorize.net processors reject any incoming transactions that are of the same amount. An error message will be displayed stating, "A duplicate transaction has been submitted."
Once you've completed these steps, you might also be interested in setting up Merchant Processor.
Was this article helpful?