Payment Form Builder

How to Create a Form with Payment

A form with payment lets you collect information and charge customers in a single step - no separate checkout page, no developer needed. With FormNX, creating a form with payment takes four steps: build the form in the visual builder, drop a Number field for fixed prices or a Calculation field for dynamic totals, connect Stripe or PayPal in the Integrate tab, then publish. Your form with payment is live in minutes, with secure checkout handled by Stripe or PayPal on their own pages so your business stays out of PCI DSS scope.

The same form with payment pattern powers every common use case below - online orders, donations, event registration, course signups, and service bookings - all from the same builder, on every plan.

What Is an Online Payment Form?

An online payment form is a web form that collects information from a respondent and routes them to a payment processor at submission to complete the transaction. Instead of building a custom checkout page, integrating Stripe or PayPal SDKs, or chasing customers with manual invoices, a payment form does it all in one step - the customer picks options, sees a calculated total, hits Submit, and lands on a secure checkout to pay by card, PayPal, or digital wallet.

FormNX is a free no-code payment form builder. There is no JavaScript to write, no PCI scope on your servers, no developer needed. Connect Stripe or PayPal once, point the Price Field at a Number or Calculation field, and any form becomes a secure online payment form.

How to Build a Payment Form (No Code)

Creating a payment form with FormNX takes four steps:

1. Add a price field - drop a Number field for fixed prices, or a Calculation field for dynamic totals that update based on user inputs (quantity, options, tiers, tax, shipping, discount codes).
2. Connect Stripe or PayPal - in the form Integrate tab, paste your Stripe Secret Key or your PayPal Client ID and Secret. FormNX validates the credentials in real time. You can connect both processors and let customers pick at checkout.
3. Pick the Price Field, currency, and customer email field - choose which form field drives the amount, which currency to charge in (USD, EUR, GBP, CAD, AUD, INR, and 100+ more), the product name shown at checkout, and which form field holds the customer email for receipts.
4. Save and share - your payment form is live. Embed it on your site, share the direct link, or trigger it as a popup. Every submission routes the customer through secure checkout.

Why Use a No-Code Payment Form Builder?

A payment form replaces three pieces of software with one: a form builder for collecting data, a developer-built checkout for taking money, and a CRM for storing the customer details. Building that stack manually means weeks of development, PCI compliance scoping, payment gateway SDK work, and ongoing maintenance. A no-code payment form builder collapses all of it into one tool:

• No PCI scope on your servers - Stripe and PayPal handle card data on their secure checkout. Your site never sees a card number, which keeps you out of PCI DSS scope.
• Dynamic pricing without code - quantity multipliers, tiered pricing, member vs non-member rates, location-based tax, shipping by weight - all driven by Calculation fields, no JavaScript.
• One form does the job of three - data collection, payment, and CRM record in one submission. No reconciling spreadsheets with Stripe dashboards.
• Recover abandoned checkouts - for any unpaid submission, regenerate a payment link with one click and resend. The customer completes payment and the submission flips to Paid - no recreating the order.
• Multi-currency support - charge USD, EUR, GBP, CAD, AUD, INR, and 100+ other currencies depending on your Stripe and PayPal account settings.
• Works with conditional logic and multi-step forms - pair payments with skip logic to charge different amounts based on selections, or place the payment step at the end of a multi-page form.

Types of Payment Forms You Can Build

The same FormNX payment form builder powers every common payment use case - the only thing that changes is the form fields and pricing logic:

• Online order forms - product selectors with quantity, options, and a Calculation field that totals the order. Stripe or PayPal handles checkout.
• Donation forms - preset donation amounts ($25 / $50 / $100) or a free-entry amount field, optional recurring donations, and a custom thank-you page.
• Event registration with paid tickets - attendee info plus ticket-type selection that drives the price. Sell early-bird, regular, and VIP tiers from one form.
• Course and membership signups - plan selection, optional add-ons, and conditional fields based on the selected plan.
• Service booking forms - service type and add-ons set the total, plus date and time fields. The customer pays at booking, not after.
• Custom quote acceptance forms - send a unique link with the quote amount pre-filled; the customer reviews and pays in one step.
• Subscription and recurring billing forms - collect subscriber details and start a recurring Stripe subscription on submission.
• Invoice and bill payment forms - reference number plus amount fields let customers pay an invoice without account login.
• Tip and gratuity forms - simple Stripe forms for service businesses to collect tips after a job.

Stripe Payment Forms vs PayPal Payment Forms

FormNX supports Stripe and PayPal as separate integrations - use either, or both on the same form. Customers see both options at checkout and pick the one they prefer:

• Stripe payment forms - accept Visa, Mastercard, Amex, Discover, plus Apple Pay, Google Pay, and local payment methods depending on your Stripe configuration. Best for businesses already running on cards and digital wallets. See the Stripe integration →
• PayPal payment forms - accept PayPal balance, linked bank accounts, and cards through PayPal's checkout. Preferred by donors, international audiences, and customers who would rather not enter card details on a new site. See the PayPal integration →
• Both, on the same form - the highest-converting option for general audiences. Customers see Stripe and PayPal side by side at checkout and pick the method they already trust.

Secure Payment Forms - How FormNX Keeps Card Data Safe

Payment security on a FormNX payment form is built on the gateways themselves. Card details are entered on Stripe's and PayPal's own checkout pages, never on FormNX servers - which means your business stays out of PCI DSS scope and the payment processor handles encryption, tokenization, fraud detection, and 3-D Secure / SCA. Every payment form is served over HTTPS, every Stripe and PayPal credential is encrypted at rest, and FormNX uses the official Stripe and PayPal APIs for all transactions. The result is a secure payment form with bank-grade protection, set up in minutes.

Embed Your Payment Form Anywhere

Every payment form you build with FormNX works on any site. Embed it on WordPress (Gutenberg block, shortcode, or Elementor widget), Webflow, Shopify, Wix, Squarespace, or paste the embed code into a custom HTML site. You can also share the direct link in emails, on social media, or trigger the payment form as a popup overlay. Stripe and PayPal checkout flows behave identically wherever the form lives - no separate mobile checkout, no developer setup.

FormNX vs Other Payment Form Builders

Most popular payment form builders charge a per-submission platform fee on top of Stripe and PayPal processing fees (Jotform charges 3% on its free plan, Wufoo applies processing surcharges, Typeform gates payments behind paid tiers). FormNX charges 0% platform fees on paid plans - the only fees are the standard Stripe/PayPal processing fees that go to the payment processors directly.

You also get features competitors charge extra for: dynamic pricing via Calculation fields, conditional pricing rules, multi-currency support, abandoned-checkout recovery, both Stripe AND PayPal on the same form, and payments that work natively with multi-step forms and conditional logic. The visual builder handles every part of the experience, so you never touch a payment SDK or write a line of code.