Moheeb Zara
8edc9da611
Finalizes the docs section after an adversarial audit (code review + per-page fact-check + coherence critic) and two content requests. - Accuracy: fixed 10 invented cross-link slugs, the admin-vs-board gating claims the verifiers caught (permissions matrix, /settings, invites, onboarding, connect-payments, proposal withdraw, Stripe reconciliation, member fields, door.operate), and 2 issues in the new pages (project area-at-creation, forum thread-delete role). - Coverage: added 5 how-to pages so every module is documented (recurring Stripe dues, tasks & chores, projects, comms & forum, ops knowledge base + secrets vault). 34 pages total. - Screenshots: 12 captioned app screenshots under public/docs-media/, embedded as figures. Each tutorial now has 2-3 step screenshots. - Style: removed all em-dashes/en-dashes/ellipses from the docs (natural ASCII punctuation). - Handoff (docs/HANDOFF-audit-cleanup.md) updated with the current state. typecheck 0 · lint 0 errors · build ok (all 34 /docs pages prerendered)
79 lines
4.5 KiB
Markdown
79 lines
4.5 KiB
Markdown
In this tutorial you will set up an external pay-here link, watch a member pay through it, then record that payment and reconcile it to the member so their dues advance. By the end you will have taken one dues payment all the way from "add a link" to a member marked `current`.
|
|
|
|
You will use three screens: [/settings](/settings) to add the link, [/import](/import) to record the payment, and [/payments](/payments) to reconcile it.
|
|
|
|
## Before you start
|
|
|
|
You need the right role for each part:
|
|
|
|
| Task | Required role |
|
|
| --- | --- |
|
|
| Add or edit a pay-here link | admin (the Settings screen is admin-only) |
|
|
| Import and reconcile payments | admin, board, or treasurer |
|
|
|
|
This example uses Venmo, but PayPal and Zeffy work exactly the same way.
|
|
|
|
## Step 1: Add a pay-here link
|
|
|
|
|
|
|
|
1. Go to [/settings](/settings) and open the **Dues** tab.
|
|
2. Under **Other ways to pay dues** you will see a card for each platform: PayPal, Zeffy, and Venmo. Find the **Venmo** card.
|
|
3. Paste your payment link into the **URL** field. It must be an absolute `https://` URL, anything else is rejected.
|
|
4. Optionally add an instruction, for example `Put your member name in the note`. This is a hint that helps you match the payment later.
|
|
5. Leave the toggle set to **shown** so members can see it.
|
|
6. Click **Save**.
|
|
|
|
The link is now live for your space. You can add all three platforms, and hide any one later by flipping its toggle to **hidden**.
|
|
|
|
## Step 2: The member pays externally
|
|
|
|
There is nothing for you to do here, this is what the member sees.
|
|
|
|
1. The member opens their [/me](/me) page and looks at the **Dues** section.
|
|
2. While they still owe dues, the card shows your active links under **Other ways to pay** (or **Pay your dues** if your space has no card billing set up).
|
|
3. They click **Pay with Venmo**, which opens your external payment page in a new tab, and they pay you there, adding their name in the note if you asked them to.
|
|
|
|
The platform does not record this payment automatically. That is the next step.
|
|
|
|
## Step 3: Record the payment
|
|
|
|
|
|
|
|
When your Venmo activity is available, export it as a CSV and import it.
|
|
|
|
1. Go to [/import](/import) and switch the **Import type** to **Payments**.
|
|
2. Upload your CSV file by dropping it on the upload area or clicking to browse.
|
|
3. On **Map Columns**, confirm the required fields are mapped: **Amount**, **Sender / From Name**, and **Date**. Set the **Platform** column to `venmo` so the payment is tagged correctly, and map the note column if you have one.
|
|
4. Click **Preview Import**, review the first few rows, then click **Import**.
|
|
|
|
Every imported row lands as an `unlinked` payment. Rows with a bad amount, platform, or date are skipped and counted, so nothing invalid is silently added.
|
|
|
|
> Recording a single hand-received payment instead? Use the **Log Cash** button on [/payments](/payments), but note it always records the platform as `cash`.
|
|
|
|
## Step 4: Reconcile the payment to the member
|
|
|
|
|
|
|
|
1. Go to [/payments](/payments). The header shows a count like **1 unlinked** whenever payments still need a member.
|
|
2. Find your Venmo row. You can narrow the list with the **All Platforms** and **All Status** filters at the top of the transactions table.
|
|
3. Click **+ Link member** on that row.
|
|
4. In the **Link to Member** dialog, pick the member who paid.
|
|
|
|
The row flips to `linked` and shows the member's name with a check mark.
|
|
|
|
## Step 5: Confirm the dues advanced
|
|
|
|
Linking a payment does two things automatically:
|
|
|
|
- It advances the member's **last paid** date to the payment's date.
|
|
- It sets the member's status to `current`, as long as this payment is the most recent one on file for them.
|
|
|
|
This is **advance-only**: recording an older or backdated payment never moves a member's dues backward. If the member already has a newer payment recorded, linking an older one leaves their status untouched.
|
|
|
|
To verify, open the member on [/members](/members) and check their status, or have the member reload [/me](/me), where the payment now appears under **My payments**.
|
|
|
|
## What you did
|
|
|
|
You added an external pay-here link, a member paid through it, you imported the payment as an `unlinked` row, and you reconciled it to the member, advancing their dues to `current`. Repeat Step 3 and Step 4 whenever new external payments come in.
|