|
| | | |
| |
Get paid three ways. Never leave the form. |
|
| |
Square joins Stripe and PayPal. Plus: dates that check their own logic, an easier way to start building. |
|
| |
|
|
|
|
| |
| |
|
Now three ways to get paid, without leaving the form |
|
| | |
If your clients already pay through Square, that used to mean a gap in the form — collect the details, then send them somewhere else entirely to actually pay. Every extra step is a chance for someone to close the tab and never come back. |
|
| | | |
| | |
| |
⚠️ Square doesn't have a test mode — submissions charge a real card. Stripe and PayPal both offer sandbox testing if you'd rather try the flow first. Square also requires a paid plan. |
|
| | |
|
|
|
|
|
Or skip the reading — here's what turning on Square actually looks like. |
|
| | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
| |
The details that make a document actually usable |
|
| | |
Two updates this month, one theme: dates. Date and Date & Time fields now handle more of this logic themselves: bound a date between two other fields (an inspection date that has to fall between a lease's start and end, say), or restrict the time of day on its own (appointments only between 9am and 6pm), with a clearer error message when either check fails. And the date someone submits a document gets stamped directly into the PDF itself — so the "date signed" on a contract is the date it was actually signed, not the date someone happened to open the file later. |
|
| | | |
| | |
| | |
| |
|
|
|
| |
| |
Three doors in, not one guessing game |
|
| | | |
| | | |
| | |
🛠 FOR DEVELOPERS Testing the API just got clearer Find it under Manage form → Connect → API Playground. A live checklist shows what's missing before you test, and every call now returns a status code and response time — not just raw JSON. Endpoints are grouped by category too. See the updated guide → Still requires a published form with at least one submission, on a free-trial or paid plan. |
|
| |
🔍 AN HONEST MOMENT We ask ourselves this too: when any tool builds a document — or a form — for you automatically, what does it quietly do with your data along the way? We put together a short checklist for anyone using an AI form builder (ours or otherwise) — is it collecting fields you didn't ask for, storing anything it shouldn't, or touching sensitive data like PHI without you realizing it. Worth forwarding to whoever on your team is building forms with AI right now. Read the AI safety checklist → |
|
|
|
|
|
|
Which one do you actually need right now? |
|
|
A faster way to get paid, or a safer way to check the tool that's building your documents. |
|
|
|
|
|
|
|
| |
|
|
|
|
|
| |
|
608 Harris Street Ultimo NSW 2007 |
|
|
©2026 PlatoForms All Rights Reserved |
|
| |
|
|
|
|
|