How the Transaction Portal Works

The Transaction Portal is the self-serve page at pinecone.humanitru.com/portal where a donor can look up their own giving history and manage an active recurring gift — no account or password required.

There's no username or password. A donor authenticates with a signed link, delivered one of two ways:

1. Donor requests access. They enter their email on the portal's landing page, or a staff member generates a link for them directly from Alpine (pinned to that donor's organization).
2. A signed link goes out. The portal emails a link carrying a cryptographically signed token — no shared secret, so it can't be guessed or reused across donors.
3. The link is good for 60 minutes. Unused past an hour, it expires and the donor has to request a fresh one. Once inside, every page and download reissues a new token automatically, so an active session doesn't time out mid-browse.

The portal is available in English and Spanish.

The list a donor sees is pulled live from Alpine at the moment they open the portal — it isn't a copy that lives only in Pinecone. The rule for what's included has nothing to do with where a transaction came from: any Donation, Membership, or Ticket action tied to that donor's email shows up, regardless of which system created it.

Good to know: There's no toggle to hide a particular integration from a donor's view — sourcing isn't a filter option today, by design or otherwise.

Heads up: Alpine's "verified" flag — the one that gates most reports and Stewardship Automation segments — is not checked here. An unverified action still shows up in a donor's own transaction history.

The list treats every source equally, but managing a gift is different — that only works for donations that originated in Pinecone, because only those have a local payment record behind them. For a Pinecone-native recurring donation, a donor can:

• Change the payment method on file (card or ACH, if you accept this)
• Push the next charge date out (must be a future date)
• Cancel the recurring gift outright

A ticket purchased through ACME, or a membership synced in from Ticketure, still appears in the list — the donor just can't act on it from here. There's nothing to manage: no local record, no controls.

The on-page list paginates at nine transactions per page and can be narrowed to a date range. The same date range applies if the donor downloads a CSV instead. The CSV includes:

• Action ID — internal record id
• Donation ID — Humanitru id
• Transaction Date — M/D/YYYY, local time
• Transaction Type — Donation / Membership / Ticket
• Amount — dollars paid
• Fair Market Value — dollar value of goods/services received
• Tax-Deductible Amount — Amount minus Fair Market Value

Humanitru hosts many separate nonprofits, and a donor's email isn't unique to one of them. If the same address has given to more than one client organization, the self-requested flow shows an org picker so the donor can switch between giving histories. A link a staff member generates from Alpine skips that step — it's pinned to that one organization from the start.

• "I don't see my ticket purchase" is rarely a portal bug — check that the action exists in Alpine under that donor's email as kind Donation, Membership, or Ticket. If it's there, it will show, unverified or not.
• "I can't change my card" on a gift that wasn't made through Pinecone is expected, not broken — see Recurring Gifts above.
• If Alpine can't be reached for a donor's email at all, the portal silently falls back to Pinecone's own local records for that donor as a last resort — donors relying on this path only ever see Pinecone-native transactions.
• A stale "link expired" complaint almost always means more than 60 minutes passed between the email landing and the click — resending is the fix, not troubleshooting.

Reference for the Transaction Portal (pinecone-rails / alpine-rails). Reflects the code as of September 2026 — behavior can change with future releases.