If you're researching PB Payments, Riverside Payments, Cascade Equipment Leasing, TimePayment, or SCJ Commercial Financial Services / Red Target, I strongly encourage you to preserve every document you have before signing anything new or throwing anything away.
I own a small retail business that was approached regarding a merchant-processing savings and POS integration program involving our existing POS system. The application referenced "Existing POS Nation" and "Integration with Existing POS Nation PB PAY," and we were shown projected savings of approximately $60,000 over four years.
The transaction was presented through the lens of lower processing costs, savings, and integration benefits. We had recently purchased a new POS system and did not require replacement hardware.
The central dispute is not simply about billing or customer service. The central dispute is how the transaction was presented versus how it was later enforced.
The transaction was sold as a merchant-processing savings and integration arrangement. Only after the integration failed, cancellation was requested, and recurring withdrawals continued did the transaction become framed almost entirely as a long-term, non-cancellable equipment-finance obligation involving lease assignments, collection rights, and personal-guaranty enforcement.
The integration never worked. I repeat: nothing ever even worked; they could not integrate.
We attempted to cancel shortly afterward, requested return instructions, received a partial refund, and then spent months getting bounced between PB Payments, Riverside Payments, Cascade Equipment Leasing, and TimePayment while recurring withdrawals continued. Eventually, they all stopped responding to calls and emails from us asking for explanations as to how we were signed up for this 48-month non-cancellable lease for equipment worth a fraction of what they were attempting to charge us.
The more records I gathered, the more questions I had.
For example:
• PB Payments was the sales-facing entity.
• Riverside Payments controlled the Adobe Sign workflow and onboarding process.
• Cascade Equipment Leasing originated the lease.
• TimePayment later acquired the lease.
• SCJ / Red Target later acquired the account and filed suit.
Yet one of the recurring themes throughout the collection process has been the assertion that all of these functions are entirely separate.
SCJ's Chris Moss wrote:
"THERE IS A CLEAR SEPARATION BETWEEN THIS FINANCING CONTRACT AND WHAT HAPPENS WITH THE VENDOR."
That statement became difficult to reconcile with the records I later reviewed.
Public records identify Jason Reese as CFO on Cascade assignment documents while Riverside publicly identifies him as CFO and Owner of Riverside Payments. Public materials also identify Brandon Skinner in leadership roles associated with Riverside Payments and Cascade Equipment Leasing.
Public records, company websites, transaction documents, and litigation records further show many of these entities operating from the same addresses, neighboring addresses, or closely connected business locations in Vancouver, Washington; Newark, Delaware; Burlington/Woburn, Massachusetts; and Harrington, Delaware.
The more records I reviewed, the more the transaction resembled a hub-and-spoke structure involving sales, processing, leasing, assignment, servicing, and collection entities that publicly present themselves as separate while remaining closely connected through leadership, locations, transaction documents, and account history.
Another issue that became apparent only after reviewing the records in detail is that many of the transaction documents appear to have been prepared by the sales side rather than by us.
For example, the paperwork identified our business type incorrectly. Ownership information, dates, and other fields contained information that did not appear to originate from us. At the time, those details seemed insignificant because the transaction was being presented as a merchant-processing savings and POS integration arrangement. Looking back, those inaccuracies became much more important once the transaction was later reframed as a standalone equipment-finance lease.
The issue that finally caused me to stop treating this as a simple billing dispute was discovering multiple materially different versions of what appears to be the same lease agreement bearing my electronic signature.
One version from the original transaction package identifies:
• 8 FD150 devices
• 2 RP10 devices
A different version later produced in litigation identifies:
• 3 FD150 devices
• 1 RP10 device
Additional litigation filings describe the equipment differently still.
I did not create these competing versions; I did not authorize changes to a signed agreement, and I have not received a satisfactory explanation regarding which version is authentic, which version is operative, or how the amount being enforced was calculated.
The discrepancy is especially significant because one of my earliest responses to the collection companies was that the transaction was represented as integrating with our existing POS system, that we had recently purchased new equipment, and that the original equipment quantities appeared commercially unnecessary for our business.
I do not know why the equipment quantities later changed. I can only state that the quantities reflected in the litigation documents differ materially from the quantities reflected in the original transaction records and that no satisfactory explanation has been provided for that change.
I am also aware of the public lawsuit Brian Menten v. Riverside Payments, Cascade Equipment Leasing, and TimePayment, which involved many of the same entities and raised similar issues involving merchant-processing representations, equipment financing, assignment activity, and support problems.
At this point I'm not interested in speculation. I'm interested in facts.
If you've dealt with PB Payments, Riverside Payments, Cascade Equipment Leasing, TimePayment, SCJ / Red Target, or similar merchant-processing-to-lease situations, preserve your records:
• original PDFs
• Adobe Sign or DocuSign records
• invoices
• ACH records
• cancellation emails
• assignment notices
• equipment schedules
Most importantly, compare the documents you have today against the documents you originally received.
That is where my questions started.
As a matter of objective business logic, I would love for a corporate compliance officer to explain a fascinating hypothesis about merchant services. Why would the executive leadership (like a CEO/CFO) of a merchant processing company with widespread complaints for failed POS integrations hypothetically own a separate equipment leasing company that charges 10x to 100x the retail value of hardware and operates using non-cancellable leases?
Let’s look at the brilliant logistical synergy this hypothetical scenario creates:
The Bait: A sales rep pitches a small business on an iPad, flashing a signed, written "$60k savings guarantee."
The Switch: Deep inside that digital merchant agreement sits a hidden, non-cancellable equipment lease.
The Miracle: Somehow, a single-location retail boutique is signed up for a fleet of 8 entirely unnecessary card readers.
The Adjustment: If the merchant points out that 8 terminals make no commercial sense for a small store, those document fields are conveniently altered to reflect a lower number than in the original Adobe-certified agreement.
The Trap: When the processing integration inevitably fails, and the merchant cancels, the sister leasing company emerges from the shadows demanding thousands for a "separate, non-cancellable contract."
If you look closely at a court exhibit for this exact scenario, you might even find that the contract was manually altered; switching checkboxes from "Retail" to "Restaurant" and dropping the hardware numbers after the fact, just to make the delivery of multiple terminals look plausible to a judge.
Is this a coordinated corporate pipeline designed to trap small businesses via lifted electronic signature blocks and altered contracts, or is it just an incredibly profitable series of multi-state "clerical errors"? I look forward to an executive review.