Skip to content

Record a phone payment

As a Membership Staff member, I want to take a one-off payment from a member over the phone, so that their dues (or other transaction) are captured and posted without requiring them to visit in person or mail a check.

Screen: Members > (open a member record) > Phone Payment

Phone Payment is a form, not a history grid — it's designed to actually process a live payment through the FluidPay gateway, not just display past activity.

Key fields: Email, Alternate Email, Address1/2, City, State, Zip, Country, Transaction Type* (required), Amount* (required), a "+" button to add another transaction line, Total, Service Fee, Amount to Pay* (required), Payment Method (dropdown: Credit Card, Check).

Actions available: Add Alternate Address; Submit (processes the live payment).

Submit button on the Phone Payment form

This is one of the tabs Business Agent explicitly lacks

Phone Payment is hidden for Business Agent and Management specifically — present for the other six roles, including Super User. If a member calls in with a payment and the person they first reached can't see this tab, that's the hand-off signal to route it to Membership Staff or Accounting. See Know when to hand off to Accounting for the Business Agent side of that same boundary.

Things to watch out for

Always fill Transaction Amount, not just Amount to Pay

The form has two dollar fields that look similar: Transaction Amount is the real money-moving field; Amount to Pay is a calculated display field. A real defect let money get captured by the payment gateway with $0 allocated as dues because only Amount to Pay had been filled in. Fixed in Prizm 2.24 by making Transaction Amount required — but the lesson still matters operationally: fill Transaction Amount directly, every time. (IUOE-2663)

Check (ACH) doesn't work in this environment — use Credit Card

Selecting Payment Method: Check still renders a FluidPay ACH tokenizer iframe and tokenizes fine, but the backend call always fails with "no default processor set" — IUOE's FluidPay merchant account isn't configured for ACH, which is a merchant-account choice, not a PRIZM defect. Credit Card is the channel that actually works end to end. (IUOE-2830)

Deposit routing is by transaction type — and buckets have no defined rule yet

A Phone/FluidPay payment's deposit is chosen by its transaction type: Dues/Misc/Merch route to the "union-Fluid Pay" deposit; FedPac/PEF route to "Fed Pac Fluid Pay" — the deposit auto-creates if none is already open. A straight Dues phone payment routes correctly. Paying a bucket that contains an Initiation component via Phone Payment is a scenario with no defined posting rule today (tracked as a separate Change Order) — don't assume it will land the way a normal Dues payment does. See ../../../../task-management/cases/closed/ACCOUNTING-CLUSTERS.md ("Deposit routing by transaction type") for the full writeup. (IUOE-2741)

Bucket payment math via Phone Payment isn't confirmed reliable

Bucket payment allocation (Amount Paid vs. Amount Applied) has only been confirmed correct for a full walk-in payment against an adjusted bucket. Phone payment, employer payment, and unadjusted-bucket scenarios have shown apparent mismatches in testing — don't generalize a bucket-payment fix to the Phone Payment channel specifically. (IUOE-2705)

A failed receipt print after a phone payment is a known, recurring symptom

"Report not found" when printing a receipt after a credit-card transaction traces back specifically to the Phone Payment feature under Member Details — treat any "can't print receipt after a card payment" report as this same family rather than a new issue. (IUOE-2187)

Reversing a bad payment is a multi-step process, not one click

If a phone payment needs to be undone, "Roll back" offers Void (remove entirely) or Back out (reverse from the original member but leave the check unposted in Bank Deposit for reassignment) — reassigning the check to a new member in Bank Deposit does not automatically post it; it must be separately reposted via New Walk-in. Stopping after the reassignment step will make the money look like it vanished. (IUOE-2206)