Can You Take Payments Through a monday.com Form?
Published on September 02, 2026
You need to collect a deposit, an event fee, or an invoice payment, and you already run intake through a monday.com form. The obvious question is whether the form itself can take the card details, the same way a checkout page would. It comes up often enough in the monday.com community that it’s worth a straight answer.
It can’t, not natively. Neither WorkForms nor FormFlow has a payment field. This post covers what monday.com’s own Stripe integration actually does (it isn’t what most people expect), and the two workaround patterns teams use instead.
Quick answer
- No native payment field exists on WorkForms or FormFlow forms today.
- monday.com’s own Stripe integration pulls Stripe subscriptions and invoices into monday.com boards as items — it does not add a payment step to a form.
- Teams collect payment by sending a Stripe Payment Link after the form is submitted (manually or via automation), or by using a marketplace app built for it, such as GetSign’s Stripe payment collection .
- A form can still capture the amount, invoice number, or product a respondent owes for, storing it in board columns that an automation or a human uses to trigger the actual charge.
Why monday.com Forms Don’t Take Payments Natively
WorkForms writes submissions to board items — text, numbers, statuses, files, dates. There is no card field, no checkout step, and no gateway connection built into the form itself. The monday.com community thread on the topic confirms this is a recurring question with no native answer, only workarounds.
FormFlow’s field set has the same gap. Its 30+ field types cover text, numbers, dates, files, signatures, dropdowns, and more, but no payment or card field. That’s a deliberate boundary, not an oversight: processing card data means PCI compliance, and that belongs to a payment processor, not a form builder embedded in a project board.
What monday.com’s Native Stripe Integration Actually Does
The integration runs in the direction people don’t expect: from Stripe into monday.com, not the other way around.
| Trigger (in Stripe) | Action (in monday.com) |
|---|---|
| New subscription created | Creates a new item on your board |
| New invoice created | Creates a new item on your board |
It’s a tracking tool. Once a customer already has an active Stripe subscription or invoice, the integration mirrors that record onto a board so your team can see billing status alongside project or client data. It has no trigger for “form submitted” and no action for “charge a card” — a form submission can’t initiate a Stripe charge through this integration.
Workaround 1: Stripe Payment Links
The simplest path is a Stripe Payment Link — a hosted checkout page you generate for a specific amount or product, then send as a URL. Two ways teams use this alongside a monday.com form:
- Manual: the form collects the request (what they’re paying for, how much, contact details) into a board item. Someone on the team creates the matching Payment Link in Stripe and emails it back.
- Automated: a monday.com automation fires when the item is created and calls Stripe (via Zapier, Make, or a similar connector ) to generate the link and send it, without manual work. The same board automation pattern used to send a confirmation email after a form submission applies here — swap the action for one that generates and emails the payment link instead.
Either way, the actual payment happens on a Stripe-hosted page, not on the monday.com form.
Workaround 2: Marketplace Apps Built for Payment Collection
A few monday.com marketplace apps package the Stripe connection into a payment step. GetSign is the one built specifically for this: it sends a Stripe-powered payment link when a monday.com automation fires — a status change, a button click, or any other trigger — with the amount pulled from a board column so each link is specific to that item. When the recipient pays, the board updates and you can filter items by paid or unpaid status.
That’s a genuinely different capability from monday.com’s native Stripe integration: it initiates a charge instead of just mirroring one that already happened elsewhere.
How FormFlow Fits Into a Payment Workflow
FormFlow’s role here is intake, not checkout. A form can capture what someone owes for — invoice number, quantity, product, amount — and write it to board columns an automation reads from. Pair that with one of the workarounds above (a Stripe Payment Link automation, or a marketplace app like GetSign) and you get: form submission → item created with payment details → payment link sent → board updated when paid. FormFlow’s automation recipes cover the trigger-and-action pattern that connects a submission to a downstream automation like this.
If what you actually need is payment collected inline, on the same page as the form, that’s a different tool. Jotform has built-in payment processing through Stripe, PayPal, and Square on the form itself — worth using for that specific case even alongside FormFlow for your monday-native update workflows.
Payment Collection Options Compared
| Method | Setup effort | Where the payment happens | Good for |
|---|---|---|---|
| WorkForms or FormFlow form alone | N/A | Not supported | — |
| Stripe Payment Link, sent manually | Low | Stripe-hosted checkout page | Occasional invoices or deposits |
| Stripe Payment Link, via automation | Medium | Stripe-hosted checkout page | Recurring requests at moderate volume |
| Marketplace app (e.g. GetSign) | Low | Stripe checkout, board auto-updates | Teams that want paid status tracked on the item |
| Jotform or Typeform native payment field | Medium (new tool) | Inline on the form itself | Payment must happen on the same page as intake |
Frequently Asked Questions
Does WorkForms have a native payment field? No. WorkForms writes submissions to board columns and has no card field or checkout step built in.
Does FormFlow have a native payment field? No. FormFlow’s field types cover text, numbers, files, signatures, and more, but not payment processing.
Can monday.com’s Stripe integration charge someone who fills out a form? No. That integration pulls existing Stripe subscriptions and invoices into monday.com boards as items. It has no trigger tied to form submissions and no action that initiates a charge.
What’s the simplest way to collect a payment tied to a form submission? For occasional requests, generate a Stripe Payment Link manually after reviewing the submission. For repeated or higher-volume use, automate link generation with Zapier or Make, or use a marketplace app like GetSign that’s built specifically for triggering Stripe payments from monday.com.
Next Steps
- See how automation recipes connect form submissions to downstream actions →
- Compare FormFlow with Jotform’s native payment support →
- Check which form features are gated by monday.com plan →
- Install FormFlow to handle the intake side of the workflow.
Last reviewed: 2026-08-17. monday.com’s Stripe integration behavior verified against monday.com’s own support article and cross-checked against third-party listings (Zapier , n8n ); GetSign’s payment-collection behavior verified against GetSign’s own feature page . support.monday.com and getsign.io block automated fetches, so both were confirmed through indexed search results rather than a direct page fetch. Features may change.