Jotform Clover Payments vs Typeform: Which Fits Small Firms

Key Takeaways

• Your current card processor should decide this. Jotform's Clover connection fits a team that already takes card payments through Clover, and a team that already runs Stripe can use either tool, so compare form logic, plan limits and price.

• Jotform's help article says the Clover connection supports one-time payments only, so it does not replace a subscription billing system.

• Clover's processing rate depends on your reseller and volume tier. The Clover figures in this comparison come from third-party pages, so get your own rate in writing before you compare.

• Typeform's pricing page shows two different sets of monthly prices for the same plans. This article uses the plan cards, and you should recheck them before you buy.

• Either form can start the payment, but the buyer owns retries, duplicate protection, review steps and maintenance for any handoff to a CRM or accounting tool.

Short answer and plain definition

A payment form is a web form whose final step sends the payer to a card processor, so the form tool and the processor each own part of the transaction.

TL;DR: If your card payments already run through Clover, Jotform's connection is the closer fit. If they run through Stripe, both tools connect, so compare them on form logic, plan limits and price. On the vendor pages read for this comparison, the Clover connection and Typeform's pricing page describe no recurring subscription billing inside the form, so for a small B2B software company both work best for one-time invoices, deposits, setup fees and paid requests, while the billing system stays the record of truth.

What Jotform launched on November 9, 2026

Jotform announced on November 9, 2026 that its forms now connect to Clover, so a customer can enter order, booking or donation details and pay in one flow, as described in Jotform's launch post. The post names three payment types: Sell Products, User-Defined Amount and Collect Donations. It says customers are sent to Clover's hosted checkout page to pay after they submit.

Jotform's help article lists the setup: connect a Clover account in the payment field, map the required customer email field, choose a payment type, and enter the Jotform webhook URL in Clover's Hosted checkout settings under Ecommerce. The same article says the currency is fetched from the Clover API and that the connection supports one-time payments only. Jotform also says Clover has been one of its most requested integrations, but the post gives no request counts.

For each of the following, the vendor has not published this: a fee schedule for the Clover connection, whether a Clover software plan is required, how refunds are handled, and what the webhook sends. Those gaps matter for a finance workflow, so ask for them in writing before launch.

For a team already on Clover, the change is that the form itself becomes the payment step. For a team on Stripe, the choice does not change: Jotform has a built-in Stripe connection, described on Jotform's Stripe help page, and Typeform's pricing page names Stripe for payment questions, so the Clover launch does not alter that comparison.

How we evaluated these tools

This section is our analysis, not vendor data. The weights below are ours. They reflect what a small software team actually decides: which processor it already runs, whether it needs recurring billing, and what the monthly cost is at its volume.

Weights total 100%. Where a vendor page is silent, the comparison says so instead of filling the gap, and no score is given for a criterion the pages cannot support.

Side-by-side feature matrix

The matrix shows a split. Jotform's payment details are more specific: it names a Clover connection with setup steps and currencies. Typeform's pricing page is more specific on form logic, webhooks and branding, and it names Stripe as its payment route. Neither vendor's pages describe a monthly subscription collected inside the form.

Pricing and plan costs

Pricing checked November 9, 2026.

Bronze plan: $39 per month, $408 billed yearly according to Jotform (2026). Jotform's Bronze plan allows 100 payment submissions a month and its Gold plan allows 1,000.

Plus plan: $79 per month, or $56 per month billed yearly according to Typeform (2026). Typeform's Basic plan includes 100 responses a month, conditional logic, webhooks and integrations, according to Typeform (2026).

Typeform's pricing page also has a comparison table with monthly prices that differ from its plan cards for the same plans. This article uses the plan cards, and so does the table below, so recheck both on the day you buy.

The table shows list prices only. It does not include add-ons, seat counts or processing fees, which are covered in the next section.

Processing fees and one worked example

Clover's own rate page did not load in the research for this article, so the Clover figures below come from a review site and a bank's Clover gateway page. NerdWallet's Clover review notes that its prices assume Fiserv as the merchant service provider, so a reseller's rate may differ.

Online rate: 3.5% plus $0.10 per transaction according to NerdWallet (2026). A bank's Clover gateway page lists 3.50% plus $0.15 per online transaction when monthly volume is under $40,000, plus a $9.95 monthly merchant account fee per location, according to Wells Fargo (2026).

Domestic cards: 2.9% plus 30¢ per successful transaction according to Stripe (2026). Stripe adds 0.5% for manually entered cards and 1.5% for international cards, according to Stripe (2026). Stripe also says original processing fees are not returned on refunds, so the original fee stays with you when a payment is refunded.

Because Typeform's pricing page names Stripe for payment questions, the card fee on that path is Stripe's rate, shown above.

Illustrative example, not a customer: a services firm sends 40 one-time invoices a month at $450 each, so monthly card volume is $18,000 (40 × $450). At the 3.5% plus $0.10 online rate, the Clover fee is $634: $630 for 3.5% of $18,000 plus $4 for 40 transactions at $0.10. At the 3.50% plus $0.15 gateway tier, it is $636. At Stripe's 2.9% plus $0.30 domestic rate, the fee is $534: $522 plus $12. On the Stripe side, the payment_intent.succeeded event marks a completed payment. The gap is $100 a month, or $1,200 a year, before plan prices and before any manually keyed or international card. On the Clover side, the setup depends on the webhook: Clover's hosted checkout settings need the Jotform endpoint https://ipn.jotform.com/ipns/cloverWebhook.php saved before the first live invoice goes out, per Jotform's help article.

Who this is for

Who this is for: Teams that already have a Clover account and collect one-time payments from forms, such as the order, deposit, appointment and donation flows named in the launch post. For a small B2B software company, that usually means setup fees, deposits and paid requests rather than the core subscription.

Red flags: recurring subscription billing inside the form, no Clover account and no plan to open one, or a need for a payment method that neither vendor's pages list.

Teams in regulated professions have their own comparisons, such as Jotform vs Typeform for insurance agencies and Jotform vs Typeform for accounting firms.

Vendor profiles and who should choose each

Jotform with Clover

Best fit: a team on Clover that wants a branded order, deposit or donation form whose payment step goes to Clover's checkout. The payer leaves the form for that checkout page, so the form's look stops at submit.

Limitations: one-time payments only, per the help article. The customer email field must be mapped, the currency follows the Clover account, and the vendor has not published a fee schedule for the connection.

Implementation: connect Clover in the payment field, map the customer email, choose the payment type, then enter the webhook URL in Clover's Hosted checkout settings under Ecommerce. The help article says setup is not complete until that webhook is configured. This needs admin access to the Clover dashboard.

Human review: the vendor has not published refund handling for this connection, so decide before launch who approves refunds and where that approval is logged.

Jotform said in a July 26, 2021 post that it does not charge additional transaction fees. That post predates this launch, so confirm the current terms before assuming the position still holds.

Typeform

Best fit: a Stripe-based team that wants a design-led form with conditional logic and a payment question. The pricing page places conditional logic, webhooks and integrations in the Basic plan, and removes Typeform branding and adds a custom subdomain in the Plus plan.

Limitations: the pricing page names Stripe for payment questions and names no other processor. It does not describe recurring billing, and its plan cards and comparison table disagree. Typeform's help center could not be read during this research, so confirm its payment-question rules there before you build.

Implementation: connect a Stripe account to a payment question and map the form fields that describe the charge.

Human review: refunds. The original processing fee stays with you, as covered above.

Where the handoff breaks: build it or use a proposed workflow

The payment is rarely the hard part. The hard part is the handoff: the payment has to reach a billing record, a CRM contact and a finance task without duplicates. Zapier is the usual build-it-yourself route. Pro plan: $19.99 per month billed annually according to Zapier (2026), for 750 tasks. Zapier's pricing page lists multi-step Zaps, paths and customized error settings on Pro, and adds 25 seats and an audit log on Team. Those tools can support run histories, retries, error branches and audit evidence when configured. The buyer still designs duplicate protection so a retried event does not create two invoices, decides who is alerted when a run fails, controls access to billing data, and maintains the flows as the forms change.

A proposed US Tech Automations design for the Jotform path would start with a trigger: a completed submission of the payment form. The action reads the mapped customer email, the payment type and the amount, then writes one billing or CRM record through the target system's API, or through a scheduled export if no API is available. The output is one matched record and a finance task. Before build, confirm three prerequisites: API or export access to Jotform submissions, API credentials for the billing or CRM system, and the customer email mapping, which Jotform requires for Clover. Human review points are any refund request, any amount that does not match the invoice, and any payment a processor marks as disputed.

US Tech Automations would configure the Stripe version the same way, with the trigger set to a Typeform payment-question submission and the action reading the matching Stripe charge. If the Stripe export includes the processing fee, the record carries the net amount; if not, the fee is added from Stripe's report before finance review. Refunds still need a person, because the original fee is not returned.

Firms with client intake have their own version of this handoff, covered in the law firm comparison.

Common mistakes

• Treating a payment form as a subscription. The Clover connection supports one-time payments only, so recurring fees need the billing system.

• Comparing plan prices and ignoring the processing rate. The plan is a fixed cost, while the card fee grows with every payment.

• Skipping the webhook. The help article says the Clover setup is not complete until the webhook URL is saved in Clover.

• Leaving out the customer email mapping, which Jotform requires for Clover.

• Quoting Typeform prices from one view of its page. The plan cards and the comparison table disagree.

• Assuming your reseller's Clover rate matches a review-site figure. Rates vary by reseller and volume tier.

Decision checklist

• Which processor holds your card account today: Clover, Stripe, or neither?

• Are all the payments you want to collect one-time? If any are recurring, keep billing in the billing system and use the form only for the first step.

• Do you have admin access to the Clover dashboard or the Stripe account before you start?

• Who approves refunds, and where is that approval recorded?

• Did you check the plan price on the vendor pricing page on the day you buy?

When NOT to use US Tech Automations: skip a custom handoff when your payment count is small enough to reconcile by hand each week, when the built-in connection already writes to the system you use, or when your billing platform already issues recurring invoices and the form only collects quotes. In each case a simpler setup, or the form's own payment connection, beats an automation layer.

Signal vs Speculation

Stated by the vendors

• Jotform announced its Clover connection on November 9, 2026, with three payment types.

• Jotform's help article says the connection supports one-time payments only and needs the webhook saved in Clover.

• Typeform's pricing page names Stripe for payment questions.

• Jotform says Clover was one of its most requested integrations and that the two companies share many customers. The post gives no counts.

Our speculation, not vendor data

• Recurring billing may come to the Clover connection later. Nothing published says it will.

• The launch post frames the connection around restaurants, retailers, service providers and nonprofits, so the Clover route may suit Clover-first merchants more than software companies.

• Adoption is unknown. The vendor has not published adoption figures for the connection.

Frequently asked questions

Does Jotform's Clover connection support recurring subscriptions?

No, the connection supports one-time payments only.

Do I need a Clover account to use Jotform's Clover payments?

Yes, setup requires connecting a Clover account in the payment field, and the vendor has not published whether a Clover software plan is also required.

Does Typeform add its own fee on payment questions?

The Typeform pricing page does not state a Typeform per-transaction fee in the text read for this comparison, so the card cost you can check is Stripe's published processing rate shown above.

Which option costs less at $18,000 of monthly card volume?

On the rates in this article, Stripe's domestic rate comes out about $100 a month lower than NerdWallet's Clover online rate, before plan prices. The worked example above shows the math.

Can Zapier handle the handoff instead of a custom workflow?

Yes, for simple flows, because Zapier's paid plans add multi-step Zaps and paths. You still design retries, duplicate protection and review steps.

Is either option right for annual contracts?

Only for the one-time parts such as setup fees or deposits, because neither vendor page describes recurring invoices for the payment step.

Conclusion

For most small B2B software teams, the processor narrows the decision. Clover users should look at Jotform's connection, Stripe users can use either tool and should compare form logic, plan limits and price, and everyone should check the one-time limit before building. Before you commit, confirm the plan price, the processing rate in your own contract and the webhook steps on the day you set up. To see how US Tech Automations configures a handoff after the payment, see how US Tech Automations configures this.