Thank you for your interest in LoanPro. There are more articles in our knowledge center than are currently available to you. To view all content, please log in.

Intro to Secure Payments

The basics of Secure Payments, the sister-software to LMS that handles payment profile tokenization and interactions with payment processors.

Written by Andy Morrise

Updated on June 5th, 2023

Table of Contents


Audience: Loan Servicers or Collectors, Upper Management, Developers, Accounting, Loan Servicing/Collections Managers, Administrators, Compliance, Data


Secure Payments (originally called PCI Wallet) is a LoanPro product that integrates with both LMS and third-party payment processors to facilitate payments. We developed it as a separate software so that it can more easily comply with Payment Card Information (PCI) Data Security Standards (DSS). This means that Secure Payments' code, procedures, and practices all meet a high standard for security, and that's where all of your customers' payment profile information is saved.

While security was the original reason for creating Secure Payments, it has proven helpful to have a separate software for processing payments because it is so important. Secure Payments processes hundreds of millions of dollars each month in payments.

What is Secure Payments?

Secure Payments has a few important functions:

  • Securely store payment profile data
  • Process payments
  • Batch transactions
  • Generate NACHA files

Payment Profile Data

For the sake of clarity, let's define two key terms:

  • Payment Method - A payment method is a category of financial instrument used to make a payment. These are things like cash, credit card, or e-check (ACH).
  • Payment Profile - A payment profile is a specific financial instrument. Rather than just the generic method, it's a specific card or account.

To put it another way, credit cards as a category are a payment method, but the credit card in your wallet is a payment profile.

Payment profile information is tokenized when it is entered into Secure Payments. This means the information is stored and encrypted and then a token is produced that identifies that specific payment profile. The token doesn’t contain any encrypted payment profile data, and it is worthless except as an identifier for the payment profile. Human-readable payment profile data cannot be extracted from Secure Payments once it is put in. This means that if the information was somehow accessed by an unauthorized person, they would not be able to use the information.

A lot of the time, the tokenization is done by payment processors. Because Secure Payments is not a processor, but is integrated with several processors, it gives LoanPro customers more flexibility by simply storing their payment profile information with a single processor.

Processing Payments

Secure Payments transacts a large volume of payments, and it keeps a record of every transaction and response. Because of this volume, Secure Payments' code and infrastructure have been optimized to process payments in the tiniest fraction of a second.

Payment Processing Hub

Secure Payments is a hub for third-party payment processors. These processors can transact bank card payments (credit and debit), eCheck/ACH payments, and Canadian EFT payments. They can also transact the sending of funds to a debit card or bank account. Each processor provides a different service and targets a different market. A lender chooses their processor based on cost and who will approve them.

When an integration is done, the sending and receiving of transactions within each processor is standardized so it looks the same in the Secure Payments user interface (UI) and application programming interface (API). This means: regardless of which or how many processors you use, Secure Payments will make it easy to use and switch back and forth.

Batch Transactions

NACHA stands for National Automated Clearing House Association. NACHA sets the standards for transactions between banks and created the file format banks use to process transactions. This file type is often referred to as a NACHA file.

When a number of transactions are sent to a NACHA processor, the processor compiles those transactions into a batch, which is then compiled in a NACHA file. Batching is useful for lenders that process payments using a NACHA file because it helps ensure that all payments get processed, and that no payments are submitted twice.

A batch is automatically created by Secure Payments every day after the batch cut-off time (the time before which transactions will be included in a batch). Any transactions after the cutoff time will be included in the next batch. Batches can be created manually or through the API.

Generating NACHA Files

NACHA files in the US or CPA-005 files in Canada are file formats that are most generally accepted by banks as a way to provide information for transactions to be processed. These files are very strictly formatted.

What Secure Payments is Not

Secure Payments is not a payment processor. Instead, it facilitates payment processing, by integrating with several payment processors, keeps track of transactions, and securely stores payment data. However, Secure Payments has a limited number of integrated processors. While it is sometimes possible for Secure Payments to integrate with additional payment processors by request, it's not guaranteed that an integration will always happen.

Secure Payments is not Connections. It is integrated only with payment processors and not any of the integrated services offered by Connections.

What's Next?

If you'd like to learn more about how to use Secure Payments, check out the Using Secure Payments article, which will go into more detail about the integrated payment processors and how to use Secure Payments.

Have Questions?

Contact Us