What PaymentCloud actually is
PaymentCloud sells merchant accounts to businesses that mainstream acquirers decline. Its published industry list runs to adult, CBD and hemp, nutraceuticals, firearms dealers, online pharmacy, debt consolidation and credit repair, dropshipping, subscription and continuity billing, bail bonds, tech support, alcohol, travel and timeshare. That list is the product. Everything else — gateways, terminals, chargeback advice — is resold from someone else.
It is not a payment processor in the sense most buyers mean, and read closely it does not claim to be. Its partner page describes its role as "finding the best home at the best rates." Its high-risk page says it offers "multiple acquiring bank options." Both describe a broker: a company that packages an application, shops it to acquirers, and earns on the resulting account.
The mechanics follow from that. A merchant submits an application with the usual high-risk documentation: processing history, bank statements, chargeback ratios, licenses, product pages, refund policy. PaymentCloud packages the file, presents it to acquirers it has relationships with, and services whatever account results. The acquirer sets the terms — pricing, reserve, volume cap, monitoring conditions. PaymentCloud does not hold your settlement funds, does not set your reserve, and cannot overrule a freeze or reverse a termination; it can only advocate to the party that made the decision.
The technology sits with third parties too. PaymentCloud publishes no API of its own; developers integrate against whichever gateway the merchant is placed on, and it is a listed Authorize.Net reseller. Recurring billing, virtual terminals, hosted payment pages, ACH and eCheck, and the marketed cryptocurrency acceptance all come from partners it does not name. Even the legal identity is inconsistent: the footer says PaymentCloud, LLC, the Terms of Service page says PaymentCloud Inc., and the Better Business Bureau lists Payment Cloud, LLC.
Nobody will tell you who underwrites the account
This finding outranks everything else in this profile, so it is worth stating without hedging: PaymentCloud names no acquiring bank anywhere on its public website, and publishes no registered ISO/MSP disclosure.
The parent is where the only named banks in the group appear. Kurv — the trading name of Electronic Merchant Systems, LLC, which acquired PaymentCloud in January 2024 — discloses that it is a registered ISO/MSP of BMO Bank, N.A., Central Bank of St. Louis, Esquire Bank, N.A. and Merrick Bank. It would be reasonable to guess PaymentCloud merchants land at some of those banks. It would also be a guess: no source confirms it, and the whole pitch is that applications are shopped across several acquirers, which implies at least some placements go to third parties unrelated to Kurv.
Why this matters in practice: the acquiring bank sets your reserve, decides how long funds are held, sets the chargeback threshold at which your account is reviewed, and makes the call to terminate. A high-risk merchant needs to know whether that is a large institution with a stable high-risk book or a small acquirer that may exit the vertical when losses tick up.
How PaymentCloud prices
It does not publish pricing in any form: no rate, no fee schedule, no monthly minimum, no contract length, no auto-renewal terms, no cancellation policy, no sample merchant agreement. Its high-risk page says only that cost "varies depending on the type of transactions you process and your business's risk profile," and notes that tiered and interchange-plus models both exist without saying which a merchant would be offered.
PaymentCloud's own FAQ covers application requirements, approval timelines, high-risk classification, volume limits, chargebacks and credit checks. It does not address pricing or contract terms at all — a notable omission in a document whose purpose is to answer buyer questions. No reserve policy is published either, though high-risk accounts routinely carry one, and the site's Terms of Service governs website use rather than the merchant relationship. The honest summary is that cost, term and exit conditions cannot be evaluated before applying or from the public record afterwards.
Where it is genuinely strong
Three things are real, and they are why the company has customers.
- Breadth of accepted verticals. PaymentCloud maintains dedicated pages and stated underwriting familiarity for a long list of restricted categories. For a merchant who has already been declined by a mainstream acquirer or offboarded mid-term, a broker who knows which acquirer currently has appetite for nutraceutical continuity billing is worth something that a published rate card is not.
- A human answers. The site publishes a toll-free number and staffs a live-chat channel with named agents. That sounds trivial until you compare it with the email-only, form-only high-risk brokers that dominate search results for these keywords. Getting an underwriter's questions answered in a phone call materially shortens a high-risk application.
- Gateway and hardware neutrality. Because PaymentCloud resells rather than builds, a merchant can usually keep an existing gateway and choose terminal hardware from a specific manufacturer — Verifone, Ingenico, PAX, Dejavoo, MagTek or Clover — rather than accepting a proprietary locked device. Merchants switching acquirers without rebuilding their checkout benefit from this.
E-commerce acceptance is the strongest technical area, with hosted gateways, shopping-cart plug-ins and a large library of platform integrations. Subscription and continuity billing — a category most mainstream acquirers restrict outright — is explicitly served.
Where it falls short
Fee transparency is rated none, and that rating is not a close call: nothing about cost, term or exit is published anywhere. Combined with the missing sponsor-bank disclosure, a merchant applying to PaymentCloud cannot identify either what they will pay or who they will be paying.
There is no first-party developer surface: no API, no SDK, no documentation. A business that expects to build against its processor rather than a gateway should look elsewhere.
Cross-border capability is unclear rather than absent. A third-party Authorize.Net directory listing claims service across North America and the EU, but PaymentCloud publishes no multi-currency detail, no settlement-currency options, no offshore acquiring information and no money transmitter, NMLS or foreign registration supporting service outside the US. Cryptocurrency acceptance appears in the marketed payment-method list with no provider, coin set, settlement mechanism or documentation behind it. Fraud tooling is marketed but never specified. Real-time rails such as RTP and FedNow are not supported, and there is no payment-facilitator product or orchestration layer — the "multiple acquiring bank options" pitch describes a person shopping an application, not technical routing or failover.
One documented complaint deserves mention for what it alleges rather than its volume. A Better Business Bureau complaint filed on 17 February 2026 alleges PaymentCloud abruptly closed a merchant account without adequate explanation after approving it and processing transactions, citing restricted portal access that prevented the merchant reviewing their contract, undisclosed early-termination fees and withheld funds from settled transactions. It was unanswered by the business at the time of research. Payment Cloud, LLC is not BBB accredited and had two complaints in the preceding three years — a small number, but the substance tracks the transparency gaps above exactly.
Ownership, and the churn behind the brand
PaymentCloud was founded in 2015 by Shawn Silver, working initially from his garage, with co-founder Neal Hoffman. It stayed independent until January 2024, when Electronic Merchant Systems — a Cleveland ISO founded in 1988 — announced its acquisition. Silver became group chief revenue officer and Hoffman chief marketing officer, and PaymentCloud kept its brand and Los Angeles operation.
Six months later, in August 2024, private equity firm BharCap Partners announced a majority investment in Electronic Merchant Systems. EMS was described then as processing roughly $6 billion in volume for 25,000 merchants across brands including PaymentCloud, MaxxPay, Total Touch and Paysley, with founder Jim Weiland retaining a minority stake and a board seat. EMS now trades as Kurv and has said it intends to be an active player in the M&A market.
Two ownership changes in seven months, with a private-equity buyer that intends to keep buying, describes an unsettled corporate structure. For a merchant on a multi-year agreement in a vertical with few alternatives, the practical question is whether the people who approved the account will still be answering the phone in two years. No regulatory action, consent order, FTC or CFPB matter, or class action against PaymentCloud was found in this research.
How to evaluate PaymentCloud before you apply
A submitted high-risk application creates a record. Get these answers first, in writing, and treat a refusal to answer as information.
- Name the acquiring bank. Ask which institution will hold the account before you sign, not after. Ask whether it is one of the banks Kurv discloses or an unrelated third-party acquirer. If nobody will name it, you cannot assess the counterparty that controls your money.
- Ask for the registered ISO/MSP disclosure. A registered ISO can produce its sponsor-bank statement on request. Its absence from the website proves nothing on its own, but the answer to a direct question is worth having on paper.
- Get the reserve in writing. Share withheld, holding period, release schedule, and what triggers an increase — usually the largest hidden cost of a high-risk account.
- Get the full fee schedule and the term. Contract length, auto-renewal mechanism, notice period, early-termination fee, PCI fees, chargeback fees, monthly minimums and gateway fees — each as a separate line, and each before you sign.
- Read the merchant agreement, not the website terms. The site's Terms of Service governs the website; the document governing your account is the acquirer's agreement. Get your own copy before signing, not through a portal you may later lose access to.
- Confirm who owns the gateway relationship. If the gateway account is opened in PaymentCloud's name rather than yours, changing processors later means renegotiating two contracts instead of one.
- Test the self-reported claims. The "over a 98% approval rate" figure on the high-risk page has no published methodology, no definition of what counts as an application and no independent verification. Ask what happens to your file if you fall in the remaining share.
Capability assessment
Every company profiled on this site is assessed against the same eighteen dimensions, so the profiles can be read against one another. Each rating carries one sentence of evidence. There is no score out of ten, because a score is not defensible and a sentence is.
Core strength means a primary, differentiating capability. Supported means genuinely offered and documented, but not a differentiator. Limited means partial, geographically restricted, gated behind an enterprise tier, or delivered through a third party. Not offered means what it says. Unclear means the company markets the capability but does not document it well enough to judge — which is itself a finding.
Who PaymentCloud suits
- US merchants in a category a mainstream acquirer has declined or offboarded — adult, CBD, nutraceuticals, firearms, online pharmacy, debt consolidation, subscription continuity — who need someone to shop the application across several acquirers.
- Merchants who want a named human to walk an application through underwriting: PaymentCloud staffs a toll-free phone line (800-988-2215) and live chat, which many online-only high-risk brokers do not.
- Businesses that want to stay on a familiar gateway such as Authorize.Net while changing the underlying merchant account — PaymentCloud is a listed Authorize.Net reseller.
- Merchants who need terminal hardware from a specific manufacturer rather than a proprietary locked device, since PaymentCloud resells Verifone, Ingenico, PAX, Dejavoo and Clover.
Who PaymentCloud is a poor fit for
- Any merchant who wants to know who their acquiring bank will be before applying. PaymentCloud says it offers 'multiple acquiring bank options' but names none of them anywhere on its site, publishes no registered-ISO/MSP disclosure, and its Terms of Service govern only website use, not the merchant relationship — so the counterparty that actually holds the money and can close the account is unknown until an offer arrives.
- Merchants who need to compare cost before applying. No rate, fee schedule, monthly minimum, contract length, auto-renewal or cancellation term is published anywhere on the site, and the FAQ, which does cover application requirements and chargebacks, does not address pricing or contract terms at all.
- Merchants who cannot absorb an abrupt account closure. A Better Business Bureau complaint filed 17 February 2026 alleges PaymentCloud 'abruptly closed my merchant account without adequate explanation' after approval and processing, and cites restricted portal access preventing contract review, undisclosed early-termination fees and withheld funds; the business had not responded to that complaint at the time of research.
- Merchants who dislike ownership churn. PaymentCloud changed hands in January 2024 to Electronic Merchant Systems (now trading as Kurv), which itself took majority private-equity investment from BharCap Partners in August 2024 and stated an intention to be 'an active player in the M&A market' — the entity servicing the account today may not be the one servicing it in two years.
- Merchants who need genuine developer control. PaymentCloud has no API or documentation of its own; the integration surface belongs to whichever third-party gateway the merchant is placed on, so migrating processors later means renegotiating with the gateway as well.
- Merchants outside the US who need documented licensing. No money transmitter, NMLS, FCA or equivalent registration is published, and the only cross-border claim found is a line in a third-party directory listing.
Competitors and alternatives
| Company | Why a business would choose it instead |
|---|---|
| Durango Merchant Services | A comparable US high-risk placement specialist that does disclose a sponsor bank (Fifth Third Bank, N.A.) on its own website. |
| Soar Payments | Another US high-risk ISO competing for the same verticals with a similarly consultative sales model. |
| Host Merchant Services | Competes for hard-to-place merchants while publishing interchange-plus pricing structurally. |
| Easy Pay Direct | Targets the same high-risk and multi-account e-commerce merchants with load-balancing across multiple merchant accounts. |
| Stripe / Square | For merchants who turn out not to be high-risk after all, published flat pricing and instant onboarding is cheaper and faster than a brokered account. |
| Kurv (its own parent) | Merchants can approach the parent ISO directly, which does publish its sponsor banks, rather than going through the PaymentCloud brand. |
PaymentCloud — frequently asked questions
Who actually underwrites a PaymentCloud merchant account?
PaymentCloud does not disclose this. As of July 2026, no sponsor bank is named and no registered ISO/MSP statement appears on its homepage, About page, high-risk page, partner page, FAQ or Terms of Service. Its parent, Kurv (Electronic Merchant Systems), discloses on its own site that it is a registered ISO/MSP of BMO Bank, N.A., Central Bank of St. Louis, Esquire Bank, N.A. and Merrick Bank — but no source confirms PaymentCloud-originated merchants are boarded to those banks rather than to unrelated third-party acquirers.
Is PaymentCloud a payment processor or a broker?
A broker, on its own description. PaymentCloud sells and places merchant accounts; the account itself is issued and underwritten by a third-party acquiring bank. Its partner page describes the role as "finding the best home at the best rates" and its high-risk page offers "multiple acquiring bank options." Its parent, Kurv/Electronic Merchant Systems, is the registered ISO/MSP entity in the group.
How much does PaymentCloud cost?
PaymentCloud publishes no rates, fee schedule, monthly minimum, contract term or cancellation policy anywhere on its site, and its FAQ does not address pricing at all. Its high-risk page says only that cost varies with transaction type and risk profile, and that both tiered and interchange-plus models exist. High-risk accounts commonly carry a rolling reserve, but PaymentCloud does not publish its reserve policy.
Who owns PaymentCloud?
Electronic Merchant Systems, now trading as Kurv, acquired PaymentCloud in a deal announced on 30 January 2024. BharCap Partners, a private equity firm, took a majority investment in EMS on 1 August 2024, with EMS founder Jim Weiland retaining a minority stake. PaymentCloud continues to operate under its own brand from the Los Angeles area.
What industries does PaymentCloud accept?
Its published list includes adult, alcohol, CBD and hemp, subscription and continuity billing, debt consolidation and credit repair, dropshipping, firearms and ammunition, nutraceuticals and supplements, online pharmacy, travel and timeshare, bail bonds, document preparation, digital downloads, SaaS and tech support. Acceptance in any given category still depends on the acquiring bank underwriting the individual application.
Does PaymentCloud really have a 98% approval rate?
PaymentCloud states "over a 98% approval rate" on its own high-risk page. It is a self-reported marketing figure with no published methodology, no stated definition of what counts as an application and no independent verification. Treat it as advertising rather than as a measured statistic.
Can I reach a person at PaymentCloud?
Yes. The company publishes a toll-free telephone number and runs a live-chat channel showing available agents, which is better than the email-only or form-only support offered by many high-risk brokers. Direct human contact is one of the more substantive advantages it has over comparable placement specialists.
Sources
This profile was built from the following primary and secondary sources. Where sources disagreed, the disagreement is stated in the text rather than resolved silently.
- https://paymentcloudinc.com/
- https://paymentcloudinc.com/about/
- https://paymentcloudinc.com/high-risk/
- https://paymentcloudinc.com/partners/
- https://paymentcloudinc.com/faq/
- https://paymentcloudinc.com/terms/
- https://www.prnewswire.com/news-releases/electronic-merchant-systems-ems-expands-with-acquisition-of-la-based-
- https://www.prnewswire.com/news-releases/electronic-merchant-systems-announces-strategic-majority-investment-f
- https://kurvpay.com/
- https://www.bbb.org/us/ca/encino/profile/payment-processing-services/payment-cloud-llc-1216-924639/complaints
- https://www.authorize.net/resources/reseller-directory/payment-cloud.html
- https://www.emscorporate.com/news/electronic-merchant-systems-announces-strategic-majority-investment-from-bha
- WHO UNDERWRITES AND WHO THE SPONSOR BANK IS — the central unresolved question. PaymentCloud names no acquiring bank anywhere on its public site. The only documented sponsor banks in the group belong to its parent Kurv (BMO Bank, N.A.; Central Bank of St. Louis; Esquire Bank, N.A.; Merrick Bank), and no source confirms PaymentCloud-originated merchants are boarded to those banks rather than to unrelated third-party acquirers. Do not state a sponsor bank for PaymentCloud in published copy.
- Legal entity name. The site footer says 'PaymentCloud, LLC', the Terms of Service page says 'PaymentCloud Inc.', and the BBB lists 'Payment Cloud, LLC'. No state filing was checked.
- Employee headcount, merchant count and processing volume for PaymentCloud specifically. The only figures found ($6bn volume, 25,000 merchants) are for the whole EMS/Kurv group as of August 2024, not for PaymentCloud.
- The '98% approval rate' and 'over 80% of top digital ISOs and ISVs use PaymentCloud' claims are self-reported marketing statements repeated in PaymentCloud's own press release and directory listings, with no published methodology or independent confirmation.
- Contract length, auto-renewal, early-termination fee and reserve policy — none published, and no merchant agreement is available on the public site. The early-termination-fee allegation comes solely from an unanswered BBB complaint.
- Whether PaymentCloud can serve EU merchants. Only a third-party Authorize.Net directory listing makes the North America and EU claim; no licensing or entity supporting EU service was found.
- Which gateway and cryptocurrency providers sit behind the marketed capabilities — the site names hardware manufacturers but not its gateway or crypto partners, except that it is a listed Authorize.Net reseller.
- Current PaymentCloud-specific leadership. The About page lists a leadership team headed by Afshin Yazdian as Executive Chairman & CEO, which appears to be the parent group's leadership rather than a PaymentCloud-only team; founders Shawn Silver and Neal Hoffman moved into group CRO and CMO roles in 2024.