Loan Servicing Software Payment Integration Compared
Industry Payment Guides

LoanPro vs. Nortridge vs. TurnKey Lender: Payment Features

Compare loan servicing software payment integration in LoanPro, Nortridge and TurnKey Lender so you can change processors without losing borrower data.

Woman in glasses and a black blazer working at a desktop computer in a bright office, with a binder on the desk

Photo: Pixabay

On this page 6 sections
  1. What Loan Servicing Software Payment Integration Must Cover
  2. LoanPro: Payment Processors and Posting Logic
  3. Nortridge: Integrations and Batch Processing
  4. TurnKey Lender: Borrower Portal and Autopay
  5. Retry Controls for CFPB and Nacha Compliance
  6. Switching Processors Without Losing Authorizations

Key takeaways

  • Before you sign, find out who holds the card vault. If your processor holds it, changing processors can mean asking every borrower for their card again.
  • Write ACH authorizations in your lending entity's name so they still work after a processor change.
  • In our illustrative example, one retry timed to the borrower's payday recovered more payments with far fewer returns than blind next-day retries.
  • Retry limits can come from network rules, from law and from your processor's contract. Your platform needs settings for each, and counsel should review the schedule.

When you compare LoanPro, Nortridge and TurnKey Lender on payments, two questions decide most of the outcome. The first is which processors each platform can connect to. The second is who holds the stored card and bank data. How the system decides when to retry a failed payment matters almost as much, because it shapes your relationship with your processor and your exposure under the rules. Good loan servicing software payment integration lets you change processors later without asking every borrower for new payment details.

That matters more for lenders than for most businesses. Processors underwrite consumer lending as high risk. A lender can end up changing processors after a rate increase or a reserve demand, and sometimes after an account is closed with little notice. If your servicing platform works with only one payment provider, that provider effectively controls how you collect on every loan you hold.

One caution before the comparison. Vendors change their integration lists and payment components over time, and contract terms differ by deal. This guide does not describe each platform's current feature set. It gives you the questions to settle in each demo, grouped around the payment area that matters most for each vendor. Get every answer about processors and data export in writing.

What Loan Servicing Software Payment Integration Must Cover

Start by deciding what you're testing. Problems with loan management software payments usually show up months after go-live, when a processor changes terms or a borrower disputes a debit. The table lists the features behind most of those problems and the question that tells you whether a platform handles each one.

FeatureWhy it matters for lendersAsk the vendor
Processor and gateway choiceYour first processor may not be your lastWhich processors are live today, and can I connect my own merchant account?
Vault ownershipCard tokens usually work only where they were createdWho stores card data, and will you support a PCI-compliant export to a new processor?
Payment postingEach payment has to be allocated across the loan's balancesWhen an ACH payment is returned, does the posting reverse automatically?
Retry rulesNetwork rules and law can both limit re-presentmentCan retries be set by return reason and by per-borrower failure count?
Authorization recordsUnauthorized-debit disputes are decided on proofDo you store the exact authorization text the borrower accepted, with a timestamp?
Borrower portal and autopaySelf-service cuts phone payments and staff timeDoes changing an autopay date or bank account capture a fresh authorization?
Agent-keyed paymentsPhone payments put card numbers in front of staffDo agents enter cards into hosted fields that keep card data out of your system?

The last row is easy to overlook. Collections teams take payments by phone every day. If agents type card numbers into a free-text field in the servicing system, PCI DSS scope expands to that system and to the workstations that touch it. A platform with hosted payment fields, or a separate virtual terminal for phone payments, keeps card data out of the servicing database.

LoanPro: Payment Processors and Posting Logic

Open the LoanPro demo with where card and bank data lives. If the platform stores credentials in its own PCI-compliant vault and routes transactions to a processor you pick, you can point new payments at a different processor without collecting card numbers again. If the processor holds the vault, you can't. Ask which arrangement your contract gives you and whether the payment component carries its own fees. Then get the list of processors that are live today, and ask whether a merchant account from a high-risk provider can be connected.

Posting logic deserves the same scrutiny. Every loan payment has to be applied in the order your loan agreement sets, and overpayments and payoff quotes need their own rules. Ask to see how that order is configured, not just told that it is.

Then test the reverse, because that's where servicing systems break. Post a payment, return it as insufficient funds a few days later, and check that the platform unwinds the allocation and re-accrues interest correctly. If your agreement allows a returned-payment fee, the system should add it without anyone doing it by hand. A platform that posts cleanly but reverses poorly will leave your balances wrong after every bounced payment.

Also confirm that the platform can tell debit cards from credit cards. Whether you can take credit cards on a loan at all depends on card network rules and your processor's policy. Our guide on whether lenders can accept credit cards for loan payments covers what decides it.

Nortridge: Integrations and Batch Processing

For a lender weighing LoanPro vs. Nortridge, the payment question usually comes down to architecture. Does ACH run through real-time integrations, or through a batch file you control? Ask Nortridge which model your deployment would use. Also confirm whether you'd run the system on your own servers or as a hosted service, because that decides who is responsible for securing stored bank data.

In a batch model, the servicing system builds a Nacha-formatted file of scheduled debits and sends it to your originating bank or ACH processor. A returns file comes back later and posts against the loans. The advantage is easy to miss: the Nacha file format is standard. Any originating bank or ACH processor that accepts file uploads can take it, so switching ACH providers is mostly a matter of setting up a new connection.

The trade-off is operational. Someone has to confirm that each file went out. Returns then have to post before the next autopay cycle runs, and if they post late, the platform can schedule a new debit on an account that already bounced. That second return costs you a fee and adds to your return history.

So ask Nortridge whether returns import automatically and how same-day ACH fits into the schedule. On the card side, ask which processors connect directly and which need a third-party gateway in between. For the provider side of this decision, our guide to ACH processing for online lenders covers what to look for.

TurnKey Lender: Borrower Portal and Autopay

With TurnKey Lender, focus the demo on the borrower portal. Ask how much of the borrower journey it handles under your own brand, from autopay enrollment through rescheduling a payment. For lenders without a development team, a portal that covers that whole path is the main reason to choose an end-to-end platform over a servicing core.

That makes the loan servicing autopay integration the part to examine most closely. Enrollment usually happens at signing, so the authorization the borrower accepts in the portal is the record you will rely on months later if they say they never agreed. Confirm that the portal saves the exact authorization text the borrower saw, with a timestamp. Then make a change during the demo, such as a new bank account or a moved payment date, and check that it creates a new authorization record instead of quietly editing the old one.

Bank account validation belongs in the same conversation. Ask whether the portal checks an account before the first debit. That step catches closed or mistyped accounts before they turn into returns, and processors watch those return types closely. Our explainer on Nacha account validation for borrower bank accounts covers what the rules expect and the methods available.

Finally, ask which payment gateways the platform connects to today. If swapping one out requires the vendor's paid professional services, put that cost into your comparison now.

Retry Controls for CFPB and Nacha Compliance

Retry limits don't come from one rulebook, and they don't all carry the same weight. Keep these four sources separate when you configure a platform:

  • Nacha Operating Rules. These are network rules for ACH. They govern whether and how a returned debit can be presented again. Confirm the current limits with your ACH provider rather than relying on a vendor's default settings.
  • Visa and Mastercard rules. These network rules cover retrying declined card transactions. Some decline responses signal that a retry won't be approved. Ask your processor which responses it treats as final and whether repeated attempts carry fees.
  • Federal and state law. Law may limit repeat withdrawal attempts on some loan types, and requirements differ by product and state. Our CFPB and state compliance plan tracks where federal and state oversight stands.
  • Your processor's contract. A processor may set its own return or decline thresholds that trigger reviews or reserves. Those are one processor's terms, not network rules, and they vary between providers.

Retry timing has a bigger effect than most lenders expect. The numbers below are illustrative assumptions, not data from any lender or platform.

Assume a lender has 4,000 borrowers on autopay, each with one payment due this cycle. Of the first attempts, 400 come back for insufficient funds. Under a blind schedule, the lender retries the next business day and again the day after, and only one in ten retries clears because most borrowers haven't been paid yet. Under a payday-aligned schedule, the lender makes one retry timed to each borrower's next pay date, and half of those clear.

ScheduleTotal attemptsTotal returnsFailed payments recovered
Blind: two next-day retries4,7601,08476
Payday-aligned: one timed retry4,400600200

The blind schedule works out this way: 400 retried, 40 clear and 360 return; then 360 retried, 36 clear and 324 return. The aligned schedule retries 400 once, and 200 clear while 200 return.

Under these assumptions, the aligned schedule recovers 124 more payments with 484 fewer returns. The blind schedule produces about one return for every four or five attempts, against about one in seven for the aligned schedule. Each return can carry a fee from your processor and adds to the history your bank reviews. A third attempt right after two failures is also the kind of pattern that may run into legal limits on some covered loans, so have counsel review your schedule before you set it.

Whichever platform you choose, check that it can do the following:

  1. Apply different retry behavior to each return reason, so insufficient-funds returns get retried and closed-account or unauthorized returns stop.
  2. Schedule retries relative to the borrower's pay date instead of a fixed number of days.
  3. Count consecutive failures per borrower across both card and ACH, since a borrower who fails on ACH and then on card has still failed twice.
  4. Stop automatically when a limit is reached, send the borrower a notice and log the reason.
  5. Read card decline responses and honor do-not-retry instructions.

For the return thresholds processors and banks watch, see our breakdown of Nacha return rate limits for lenders. This section is general information, not legal advice. Confirm your obligations with a qualified compliance attorney.

Switching Processors Without Losing Authorizations

A processor switch involves two separate things: the borrower's permission to debit them, and the stored credential you charge.

ACH is the easier half. The authorization runs between the borrower and your lending company, and the routing and account numbers sit in your servicing system. A new ACH processor can generally originate against the same authorization if it names your lending entity and not the old processor. Keep the company name on borrowers' bank statements recognizable through the change. When borrowers suddenly see an unfamiliar name, unauthorized-debit claims tend to rise. Our guide to winning unauthorized loan payment disputes covers the evidence that holds up.

Cards are harder. A token created by one processor usually means nothing to another. If your old processor holds the vault, you need its cooperation for a PCI-compliant export, and a contract that doesn't require timely cooperation leaves you waiting. Card networks also have rules for storing and reusing card credentials. Ask whether a migration carries over the records you'd need to show the borrower agreed to stored charges.

The cleanest setup keeps the vault away from any single processor, either inside the servicing platform or at a gateway built to sit in front of a merchant account. If you route through a gateway such as Authorize.net or NMI, ask whether the stored tokens stay usable when you change the merchant account behind it. When you do switch:

  1. Get data-export terms in writing before you sign, not when you're leaving.
  2. Board new loans on the new processor first and migrate existing loans in batches.
  3. Test a payment and a return end to end before moving autopay volume.
  4. Tell borrowers ahead of time if the name on their statements will change.

This week, email your current servicing vendor two questions: which processors and payment gateways can connect today, and who holds the card vault. If the answers tie you to one lending software payment processor, start lining up a backup before you need it. Our guide to why payday lenders get declined for merchant accounts explains what underwriters review. MannyPay offers high-risk merchant accounts for businesses that processors classify as high risk, and you can request a free processing quote to hear from a specialist within one business day.

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading