Collect payments
Last updated August 28, 2026
Take deposits, fees, or full payments as part of an application, booking, registration, or request.
This is the Intake-facing use of the Payments system.
Add payment to an intake
An intake template can define whether payment is required.
Examples:
- School application — Registration fee: JMD 5,000
- Swedish Massage — Booking deposit: JMD 2,500
- Workshop registration — Full payment: JMD 3,500
Decide when payment happens
Possible models:
- Before submission — Fill form → Pay → Submit
- After submission — Submit → Review → Payment requested
- After approval — Apply → Accepted → Pay registration fee
This is worth supporting conceptually because different industries will need different timing.
Track payment with the submission
The submission should show states such as:
- payment required
- awaiting payment
- paid
- payment verification required
- refunded
The intake record shouldn't become the accounting system; it simply shows the relevant payment state.
Continue the process after payment
Payment can trigger the next step. For example:
- Deposit paid → booking confirmed
- Registration fee paid → enrollment continues
- Consultation paid → appointment unlocked
This becomes very powerful once workflows exist.