Answers to the questions we hear most often about Furmbase — what it is, how payments work, what's automated, and how your data is handled.
Everything on this page is about what Furmbase actually does today. Where something is planned but not yet available, this page says so rather than guessing.
Furmbase is an AI-native form builder that combines form building, payment collection, custom branding, and analytics in one place. Instead of dragging and dropping fields one at a time, you can describe the form you want in plain text — "a registration form for a baking workshop with a ₦5,000 entry fee" — and the AI Form Agent builds it, then keeps refining it as you chat with it. It's built to be a smarter, more complete alternative to a generic form tool, acting as both a form and a checkout page at once.
The biggest difference is payments: Google Forms can collect answers, but it can't collect money. Furmbase can take a payment inline, as part of the form itself — tickets, orders, deposits, donations — with nothing extra to connect. Furmbase also doesn't require respondents to sign in with a Google account to upload a file, and question-level show/hide logic works without the section-jump branching Google Forms requires.
Yes, two ways. Describe what you need to the AI Form Agent and it generates the whole form — fields, sections, and basic branding — which you then refine by chatting with it. Or build it yourself with the drag-and-drop Form Builder. No coding is required either way.
Businesses use it for lead generation, onboarding, and surveys. Creators use it to sell and collect payments directly through a form. Organizations use it for memberships, applications, and structured data collection with file uploads. Schools use it for admissions, course registration, and exams. Event organizers use it for ticketing, RSVPs, and attendee management.
Yes — this is one of the most common uses. A single form can register an attendee and sell their ticket in the same flow, with the payment amount adjusting automatically to the respondent's currency. Attendee answers can be tracked and exported from the Responses tab, and the form can carry your event's branding (banner, logo, colors).
Yes. Free workspaces are limited to a capped number of forms and monthly responses. Paid plans raise or remove those limits and unlock features like payment collection fee reductions.
Your forms keep collecting responses without interruption. Once you're above your plan's monthly limit, you'll be prompted to upgrade — existing responses are never deleted or hidden.
Yes — every form can use a custom link, like furmbase.com/f/your-company, instead of a random ID. What Furmbase doesn't support is pointing your own domain (such as forms.yourcompany.com) at your forms — every form is served from furmbase.com, with your own branding applied on top. See Custom Link for how to set yours.
Yes. Add a Payment question from the Form Builder like any other question and it works immediately — nothing to connect or configure first. It can charge a fixed amount, or a calculated amount worked out from the respondent's own answers (a per-ticket price, an add-on fee, a different price per option).
Payments go through Flutterwave. Depending on the respondent's country, they can pay by card, bank transfer, USSD, mobile money, M-Pesa, or QR — Furmbase shows whichever methods apply to them automatically. Card details are entered directly into Flutterwave's own secure checkout and never touch Furmbase's servers.
The respondent sees a confirmation screen that keeps your form's branding, with a real payment reference they can quote if they need support. You, the form owner, get a "Payment Received" email for every payment. The money is added to your Furmbase wallet balance — Furmbase is the merchant of record, so it's never sent directly to an outside account — and you withdraw it to a connected bank account whenever you choose; a withdrawal is confirmed with a one-time emailed code and reviewed before payout. Furmbase doesn't currently process refunds automatically; contact support if you need to refund someone.
Yes. Every response to a form with a Payment question shows whether it was paid, along with the payment reference, right in the response detail view — so paid and unpaid responses are easy to tell apart without extra setup.
You automatically get a "Payment Received" notification for every payment you collect. There isn't yet a built-in way to automatically send the person who paid their own receipt — only the form owner receives one by default.
Every form includes Analytics at no extra cost: views, starts, completions, completion rate, average time to complete, question-by-question drop-off, and traffic sources when you share a link with UTM parameters. See Analytics for the full breakdown.
Advanced Analytics is a paid-plan upgrade that goes beyond response counts into real statistics on your answers — crosstabs, correlation, regression, trend analysis, and outlier detection. It's aimed at understanding what your answers mean, not just how many you got.
Yes, with Advanced Analytics. It can cross-tabulate two questions against each other and run correlation and regression between them, to show how answers to one question relate to answers on another.
Yes, with Advanced Analytics — correlation, regression, trend analysis, and outlier detection are all built in, so you're not limited to counts and averages.
In a secure, managed database. Form data is encrypted in transit and at rest.
Only you. Responses aren't reachable by any public or general sign-in access — every read and write goes through Furmbase's own servers, which check that you own the form before returning any of its data.
Card details are entered directly into Flutterwave's own hosted checkout — they're never seen or stored by Furmbase. Furmbase only receives a transaction reference afterward, and independently re-verifies the payment against Flutterwave's own API before crediting anyone's balance, rather than trusting what the browser reports.
Yes. Every form's responses can be exported as CSV or Excel at any time from the Responses tab, or synced straight to a Google Sheets spreadsheet in your Drive — see Export Responses. There's no lock-in on your own data.
Yes. Connect a spreadsheet once from a form's Integrations tab and every new response is added as a row in real time, with no manual export needed — see Google Sheets.
Yes, with a webhook — it sends each response's data as JSON to any URL you control the moment it's submitted, which covers connecting your own server or a tool like Zapier. See Integrations.
Yes. Deleting a form moves it to Trash, where it can be restored, or permanently deleted from there when you're sure. Deleting a form doesn't require deleting your whole account.
Account deletion is a 30-day request, not an instant action, since it needs to account for any live forms still collecting payments and any balance you haven't withdrawn yet. See Account Deletion for the full process, including how to cancel a request.
