Payment Fields
TinyForms supports inline payment collection. Respondents enter payment details and pay as part of the form submission.
Available payment fields
| Field | Provider | Use case |
|---|---|---|
| Payment | Generic | Basic payment collection (manual processing) |
| Stripe Payment | Stripe | Credit card payments via Stripe Checkout |
| Razorpay Payment | Razorpay | UPI, cards, netbanking via Razorpay |
Stripe Payment
Setup
- Add a Stripe Payment field to your form
- Connect your Stripe account (via App Authorizations)
- Configure:
| Setting | Description |
|---|---|
| Amount | Fixed amount or calculated from other fields |
| Currency | USD, EUR, GBP, INR, etc. |
| Description | What the payment is for (shown on receipt) |
| Success message | Confirmation after payment |
How it works
- Respondent fills the form
- Reaches the payment field; Stripe's secure payment form appears
- Enters card details (handled entirely by Stripe, PCI compliant)
- Payment processes
- Form submits with payment confirmation
Connecting to workflows
Form Submission (with payment) → If-Else (payment succeeded?) →
Yes: Create Record (log order) + Send Email (receipt)
No: Send Email (payment failed notification)
Razorpay Payment
Same concept as Stripe, using Razorpay's payment gateway. Supports:
- Credit/debit cards
- UPI
- Net banking
- Wallets
Setup
- Add a Razorpay Payment field
- Connect your Razorpay account
- Configure amount, currency (INR), description
Common uses
- Event registration with payment
- Product orders
- Donation collection
- Subscription signup with first payment
- Service booking with deposit
Warning
Payment fields handle sensitive financial data. TinyCommand does NOT store card numbers. All payment processing happens through Stripe/Razorpay's PCI-compliant infrastructure. TinyCommand only receives a payment confirmation token.
Note
Test payments using Stripe's test mode or Razorpay's test keys before going live. Switch to production keys only after verifying the full flow.