Jotform Clover payments explained: what it changes

What launched, and what the vendor left out

Jotform now lets a form take payment through Clover, and the customer finishes paying on Clover's hosted checkout page, according to Jotform, in a launch post dated November 9, 2026. For a small B2B service business, the category decision is which processor collects card money behind a form, so this launch adds Clover as one processor option inside a form tool you may already use.

The post is vendor marketing, not an independent review. It names three payment types, Sell Products, User-Defined Amount, and Collect Donations, and it lists use cases for restaurants, retailers, service providers, and nonprofits. Setup runs across two dashboards: in Jotform's Form Builder you open Form Elements, the Payments tab, and choose Clover, then connect the Clover account, pick a payment type, and map the required customer email field. In the Clover dashboard you open Settings, go to Hosted checkout under Ecommerce, paste the Jotform webhook URL, and save.

For a service firm that takes deposits or consultation fees, the change is that the payment step can sit on the same form that collects the job request. The post's own examples are appointments, consultations, service requests, and event deposits. Two limits appear in Jotform's help article rather than the launch post. The help article says "The Clover integration supports one-time payments only," and it requires a mapped customer email field (Jotform help article).

Here is what the vendor has not published. For fees on this route, transaction or amount limits, supported countries, a go-live date, and what happens if the webhook is not configured, the vendor has not published this. We checked Jotform's own pages and the Clover developer docs for these, and they do not state them.

Two naming points matter for buyers reading older material. Jotform's 2022 gateway article lists "First Data (now Fiserv)," and it does not mention Clover (Jotform gateway article). NerdWallet's Clover review names Fiserv as Clover's parent company, according to NerdWallet (last updated May 20, 2026). Before this launch, the gateway list named Stripe, PayPal Business, Square, and Authorize.net. Clover was not on it.

Key Takeaways

• Jotform's Clover option sends form payments to Clover's hosted checkout. The launch post is dated November 9, 2026.

• Jotform's help article says the Clover integration supports one-time payments only, so we found no support for subscriptions.

• The vendor has not published Clover-route fees, limits, or a go-live date. Clover's pricing page did not load in our session, so this article prints no Clover rate.

• Stripe is the rival that matters most. Its standard US online card rate is 2.9% + 30¢ per successful domestic transaction, on its own pricing page.

• Jotform's Bronze plan caps payment submissions at 100 a month. A payment-heavy form moves you up to Silver or higher.

• Act this month only if Clover is already your processor and you can confirm the fee on your own statement. Otherwise, this launch does not change your choice.

Signal vs Speculation

Signals are facts documented in the sources we opened. The launch post is dated November 9, 2026, and describes the integration as available. Jotform's help article was last updated September 23, 2026, and it limits the integration to one-time payments. A Jotform support reply dated September 22, 2026 says "The Clover integration you requested is now available on Jotform" (Jotform community thread). The same thread shows that in May 2023 support first said Clover was not available, then said it was on the approved list, then said it was not. Older threads can mislead.

Clover's developer docs say the hosted checkout webhook fires after a completed payment, with status APPROVED or DECLINED. They also say each message carries a Clover-Signature header that is checked with HMAC-SHA256, according to Clover. Make's connector for Clover POS and Jotform does not cover payments at all, according to Make.

Speculation is our reading, not a vendor claim. The September 2026 help article and support reply predate the November 9 launch post, so the post probably marks promotion more than first availability. We cannot confirm that from the pages we opened. Jotform's setup steps do not mention the signing secret that Clover's docs say the webhook generates. We cannot tell from public pages whether the Jotform integration checks signatures, so ask Jotform support before you rely on payment-status logic. We also think the one-time-only limit is the main blocker for subscription businesses. That is an inference from the help article, not a Jotform statement.

How we evaluated these two routes

We compare the two routes a small B2B team actually faces: Jotform with Clover, which is new, and Jotform with Stripe, the route Jotform's gateway list already named. We weight seven decisions by how much each one changes the buying decision. The weights are our judgment, not vendor data. Card fees recur on every sale, which is why processing cost carries the most weight. Card payments are also the main noncash method. The Federal Reserve counted 236.6 billion noncash payments in 2024, and cards were over three quarters of them by number, according to Federal Reserve (2026).

Head-to-head on the seven decisions that matter

Checked November 9, 2026: we re-opened Stripe's pricing page and Jotform's Clover help article that day. The matrix below uses only what the pages we opened say. "Not checked" means we did not read a source for that cell in this research.

On the evidence we could read, Stripe looks clearer on cost, and that is only because Stripe's pricing page was readable. A missing Clover rate is a gap in our research. It is not evidence that Clover costs more.

What it costs to run: pricing and TCO

Jotform's plan prices, according to Jotform's pricing page, are $0 on Starter, $39 a month on Bronze, $49 on Silver, and $129 on Gold. Yearly billing comes to $408, $468, and $1,188 a year for Bronze, Silver, and Gold. Enterprise is quote-based. Each plan also caps payment submissions per month: 10 on Starter, 100 on Bronze, 250 on Silver, and 1,000 on Gold, and Enterprise is unlimited.

Bronze plan: $39 a month with 100 payment submissions according to Jotform (2026). Jotform's 2021 post on transaction fees says the company does not charge transaction fees on payments, but it does not address processor fees (Jotform blog).

Stripe's standard US online card rate is 2.9% + 30¢ per successful transaction, and Stripe says the rate applies to domestic cards. International cards add 1.5%, currency conversion adds 1% when required, and manually entered cards add 0.5%, according to Stripe (2026). Stripe lists no monthly fees on standard pricing, and says it has "No setup fees, monthly fees, or hidden fees."

Stripe online rate: 2.9% + 30¢ per domestic card according to Stripe (2026). On a $20 payment, the fixed 30¢ alone is 1.5% of the ticket, so small tickets feel the fixed fee most.

Payment submission caps set which Jotform plan fits a given volume, assuming Clover-routed payments count toward them, which the vendor has not said.

Consider a hypothetical services firm that collects 200 card payments a month, averaging $150 each. At Stripe's standard domestic online rate of 2.9% + 30¢, each payment costs $4.65 ($150 × 2.9% = $4.35, plus $0.30), so 200 payments cost $930 a month in processing. Bronze caps payment submissions at 100 a month, so 200 payments requires Silver, at $49 a month or $39 effective on yearly billing, per the Jotform pricing page. The pages we opened do not say whether Clover-routed payments count toward that cap. The Clover side of this math needs your own Clover statement, because the Clover rate was not read here. The webhook URL that Jotform's help article gives for the Clover dashboard is ipn.jotform.com/ipns/cloverWebhook.php.

Per-vendor profiles

Jotform with Clover

Best fit: a small business that already runs Clover for payments and wants one-time payments on forms, such as deposits, consultation fees, service requests, or donations. A restaurant that already uses Clover for point of sale should read the Toast vs Clover comparison for restaurants before deciding anything about its processor.

Limitations: one-time payments only, according to the help article. The customer leaves the form for Clover's hosted checkout page, and the Clover account must be connected. The vendor has not published fees, limits, or whether a particular Clover plan is required. NerdWallet says that if Clover is your processor, you may face early termination fees if you cancel within three years, and that processing may require a long-term contract. NerdWallet also says its rates assume Fiserv as the merchant service provider and that other providers may charge differently.

Early termination risk: cancel within 3 years according to NerdWallet (2026).

Implementation: the setup is short, but the webhook step is where things break. Clover's docs describe a signing secret, generated in the Hosted Checkout settings, and a signed Clover-Signature header. Jotform's setup steps do not mention the signing secret, so confirm with Jotform support how the integration handles it before you build anything on payment status. Primary evidence: Jotform's launch post, Jotform's help article, and Clover's webhook docs.

Jotform with Stripe

Best fit: a team that wants a processor whose standard pricing is fully published and that does not already run Clover. Jotform's 2022 gateway article lists Stripe, including Stripe Checkout and Stripe ACH.

Limitations: the domestic rate is 2.9% + 30¢, and the surcharges for international cards, currency conversion, and manually entered cards add to it, as covered above. The fixed 30¢ weighs heavily on small tickets. We did not walk through Stripe's setup inside Jotform in this research, so we make no claim about its setup steps.

Primary evidence: Stripe's pricing page and Jotform's 2022 gateway article, which is dated May 31, 2022 and says it covers 23 gateways. The article's footer says 40 or more, so we do not use a gateway count.

Configure it or build it: where a workflow fits

A buyer can build the same flow in Zapier, Make, or n8n. We opened only Make's Clover POS and Jotform connector page for this article. It lists one Jotform trigger, "Watch for Submissions," and Clover actions for customers, orders, and line items. It does not mention payments, run history, error handling, or retries. Those tools can keep run histories, retries, and error branches when you configure them. You still own the design of idempotency, so a retried submission does not create a second booking, along with escalation, access controls, and upkeep. We did not check Zapier's or n8n's pages, so we make no claim about their connectors.

A proposed, configurable workflow for the Clover route would start when a Jotform payment submission arrives, read the mapped customer email, and look up the matching customer in the buyer's CRM or job tool. The output would be an updated customer record with the submission attached and the payment status recorded. A person would review any record where the status is not approved, or where the email matches more than one customer. The prerequisites are API or export access to Jotform submissions on your plan, which we did not confirm for each plan, and a payment status field that the vendor has not documented for Clover payments. US Tech Automations could configure that routing, but it would not change what Clover or Jotform charge.

A second proposed workflow suits a service business that books appointments. It would trigger on a submission with an approved payment status, create a booking in the scheduling tool, and send the customer a confirmation built from the form's own fields. A submission with no customer email would go to a review queue, because the Clover route requires that field. The owner would approve any booking above a value the business sets. The prerequisites are the scheduling tool's API access and a written refund rule, which the Jotform and Clover pages we opened do not describe. US Tech Automations could configure this sequence, and it would still need staff to confirm bookings before the calendar is final. For the follow-up step after a payment lands, see how to connect monday.com to Slack for automation. For a payments-to-records example in another industry, see how to automate LawPay payments to Clio matters.

When NOT to use US Tech Automations: skip a custom workflow if a Jotform confirmation email and a manual check by your office manager cover your volume, if you only need to take one-time payments on a form with no follow-up in another system, or if you need recurring billing. The Clover route does not support recurring billing according to Jotform's help article, so no workflow fixes that gap.

Who this is for

Choose the Clover route if you already run Clover, take one-time payments through forms, and can read the fee on your own Clover statement. Choose Jotform with Stripe if you want a processor whose standard pricing is published in full and you do not already run Clover. The Clover route is one-time only per Jotform's help article, so a subscription business should check Jotform's Stripe subscription option instead.

Red flags: you need subscriptions or recurring billing; you are locked into a processor contract with early termination fees; or you need a fee figure the vendor has not published before you commit.

Common mistakes

• Treating "no transaction fees" as the full cost. Jotform's 2021 post says it does not charge transaction fees on payments, but it does not address processor fees, and we did not read the Clover rate.

• Assuming subscriptions work on the Clover route. The help article says the integration supports one-time payments only.

• Skipping the webhook step. The help article says the Clover setup needs the webhook URL entered in your Clover account.

• Quoting the 2023 support reply that said Clover was not available. The September 22, 2026 reply says it is.

• Using Stripe's rate as a stand-in for Clover's. The two processors price separately, and the Clover rate needs your own statement.

Questions buyers ask first

Does Jotform's Clover option support recurring payments?

No. Jotform's help article says the Clover integration supports one-time payments only.

Do I need a Clover account to use it?

Yes. Setup connects a Clover account through the payment field, and the vendor has not published whether a specific Clover plan is required.

Is the Clover option live now?

Jotform's help article was last updated September 23, 2026, and a support reply dated September 22, 2026 says the integration is available. The vendor has not published a go-live date.

What URL do I give Clover?

Jotform's help article gives ipn.jotform.com/ipns/cloverWebhook.php as the webhook URL to enter under Hosted checkout in the Clover dashboard.

Can Make handle the payment side?

Make's Clover POS and Jotform connector page does not list any payment actions. It lists customer, order, and line-item actions, and it does not mention payments or checkout.

Should I switch processors because of this?

Not on this announcement alone. Switch only if you already run Clover and can confirm the fee on your own statement.

Decision for this month

For most small B2B teams, this launch is a narrow decision. If Clover is already your processor and you take one-time payments through forms, set up a small test form yourself before you move live, and check the fee on your Clover statement. If you need recurring billing, or you are not on Clover, the launch does not change your choice, and Stripe's published standard rate is the clearer baseline. Before you commit, ask Jotform support whether the integration checks Clover's signed webhooks, and ask for the Clover fee in writing from your Clover account team. If you want the configured follow-up after a payment lands, see how US Tech Automations configures this.