Reynolds and Reynolds Payment Integration: A Complete Walkthrough

Reynolds and Reynolds has been in the dealer software business since the 1920s. That's not a typo — they've been around for a century. Their systems run thousands of dealerships, particularly in the franchise dealer space.

If you're on Reynolds ERA (or the older ERA-Ignite), you know it's a capable system. You also know that Reynolds tends to prefer you stay within their ecosystem. Payment integration with third-party processors has historically been... let's say "limited."

But options exist. This guide covers how to actually get payment integration working with Reynolds, what to expect, and where the limitations are.

The Reynolds Ecosystem

Understanding Reynolds' Approach

Reynolds operates differently than CDK. Where CDK has opened up via Fortellis, Reynolds remains more controlled. They prefer you use their approved partners and solutions.

This isn't necessarily bad — it means integrations that do exist are typically well-supported. But it limits your options.

Reynolds Payment Solutions

Reynolds offers payment processing as part of their ecosystem. Like CDK's offering, it's tightly integrated but may not be the most competitive on rates.

Considerations:

• Integration is seamless (same vendor)
• Rates may be higher than market
• Switching later means integration work

Third-Party Integration Options

Approved Partners

Reynolds has partnerships with select payment processors. These partnerships mean:

• Integration has Reynolds' blessing
• Support paths are clear
• Updates are coordinated

To find out if your processor (or a prospective one) is an approved partner:

• Ask your Reynolds rep
• Ask the processor directly
• Check Reynolds' partner documentation

Custom/Direct Integrations

Some processors have built integrations with Reynolds outside of formal partnerships. Quality varies significantly:

• Some work well and are maintained
• Some are fragile and break with updates
• Support responsibility is often unclear

Proceed with caution on non-approved integrations. Get references from dealerships using the specific integration.

What Integration Looks Like with Reynolds

The Good Scenario

With a properly integrated processor:

1. Transaction is processed on terminal
2. Payment data flows to Reynolds ERA automatically
3. Customer account updates in real-time
4. Refunds sync back when processed
5. Reconciliation is minimal

The Common Scenario

With partial or poor integration:

1. Transaction is processed on terminal
2. Cashier manually keys payment info into Reynolds
3. Errors happen
4. Reconciliation takes forever
5. Everyone is frustrated

What to Verify

Before committing to a processor, verify:

• Does payment post automatically to the deal/RO?
• What specific data fields transfer?
• Is it real-time or batch?
• How are refunds handled?
• What happens when Reynolds updates their system?

Implementation Considerations

Reynolds' Involvement

Unlike more open systems, Reynolds integration often requires Reynolds' participation:

• They may need to enable certain features
• Configuration might require their support
• Testing may involve their team

Plan for this. Implementation timelines with Reynolds tend to be longer than you'd expect.

Training and Change Management

Reynolds users are often longtime Reynolds users. Changing the payment workflow means:

• Retraining staff who've "always done it this way"
• Updating documented procedures
• Potential resistance to change

Build in adequate training time.

Testing Thoroughly

Before going live:

• Test every transaction type (sale, refund, void)
• Test in every department (service, parts, sales)
• Verify data appears correctly in Reynolds
• Test exception scenarios (declines, partial payments)

Common Reynolds Integration Challenges

"Reynolds says they don't support that processor"

Reality check: Reynolds is protective of their ecosystem. This might mean:

• No formal partnership exists
• The processor hasn't pursued Reynolds certification
• Reynolds prefers you use their solution

Options:

• Choose an approved partner
• Ask your processor to pursue partnership
• Accept manual workarounds

"Integration worked but broke after an update"

Why it happens: Reynolds system updates can affect integrations, especially non-approved ones.

Prevention: Use approved partners who coordinate with Reynolds on updates.

Recovery: Contact your processor immediately. Escalate to Reynolds if needed.

"Only some data posts automatically"

Common issue: Partial integrations where amount posts but not card type, or transaction posts but not to the correct deal.

Solution: Clarify exactly what data transfers before implementation. If critical fields don't sync, that's not real integration.

Reynolds vs. Other DMS Platforms

If you're evaluating DMS platforms or considering a switch:

Reynolds strengths:

• Mature, full-featured system
• Strong in franchise automotive
• Reliable and well-supported

Reynolds limitations:

• More closed ecosystem
• Fewer third-party integration options
• Can feel inflexible

Payment integration specifically:

• More limited options than CDK
• Approved partners work well
• Non-approved integrations are risky

Making It Work

If You're Committed to Reynolds

1. Identify approved payment partners
2. Evaluate based on rates, features, and integration depth
3. Verify integration capabilities with references
4. Plan implementation with realistic timelines
5. Train staff thoroughly

If You're Evaluating Options

Consider whether Reynolds' more closed approach works for your needs. Some dealerships prefer the control; others find it limiting.

Payment integration is one factor among many in DMS evaluation.

Our Experience with Reynolds

Dealerships come to us with Reynolds for two main reasons:

1. They're using Reynolds Payments and want better rates — but fear losing integration.

2. They're manually keying payments and want real automation.

Both are solvable. With an approved integration approach, you get competitive rates and real-time posting. It just requires working within Reynolds' framework rather than around it.

---

See Reynolds Integration →

We'll show you how payments flow from terminal to Reynolds ERA, with your specific setup.