Giving & payments
Take the gift without losing its terms
A contribution arrives carrying instructions: this fund, this restriction, every month, in memory of someone, from this appeal. Most checkout flows keep the amount and drop the rest. Beneora treats those terms as part of the gift.
Gift received
Recurring · Winter Shelter (restricted)
Processor fee
2.9% + $0.30 · card
Net to payout
Payout PO-2261 · settles T+2
Bank deposit
Matched batch of 21 gifts
Fund allocation
Winter Shelter · restriction honoured
Monthly gift
$250
Next Aug 12 · change or pause
Pledge
50%
$3,000 of $6,000 fulfilled
Receipts
2026
Statement ready to view
What your giving did
Winter Emergency Shelter · 1,914 bed-nights recorded this season, with the evidence the organization filed.
- Amount
- $250.00
- Fund
- Winter shelter (restricted)
- Recurrence
- Monthly, 15th
- Attribution
- Appeal WT-24 · email
- Fees covered
- Yes — $8.30
- Checkout
- Gift record
- Receipt
- Payout
The designation, recurrence and attribution are fields on the gift, so the receipt and the deposit read the same terms.
What the system holds
The objects behind the workflow
A workflow is only as reliable as the records underneath it. These are the objects this pillar owns.
Form
A branded, embeddable giving surface with its own fields, suggested amounts, designations, recurrence options and tribute handling — versioned, so you can see what a donor was shown.
Checkout session
The donor's intent before money moves: amount, frequency, designation, restriction, tribute, cover-the-fee choice and attribution source.
Transaction
Gross, fee and net held as values, with the processor reference, method, currency and settlement state.
Attribution
Campaign, appeal, source, medium and UTM parameters captured at checkout and carried onto the gift, so conversion analysis is a query rather than a guess.
How the work runs
Four steps, in order
Read left to right on a wide screen, top to bottom on a phone. The order is the order the record moves in.
- 01 · Step 1
Build the form
Compose fields, amounts, designations and recurrence in a form builder with a live donor-checkout preview beside it. What you see is the component the donor will use, not an approximation.
- 02 · Step 2
Publish and attribute
Publish to a campaign page or embed it. Inbound traffic keeps its source, medium and campaign so first-gift conversion can be measured per appeal.
- 03 · Step 3
Take the payment
Card, wallet and ACH, one-time or recurring, with the fee-coverage choice recorded rather than assumed.
- 04 · Step 4
Create the record
The gift is written with its designation and restriction attached, resolved to a donor and household, and queued for receipting — in one operation, not four.
Safeguards
What stops it going wrong
Each safeguard is server-enforced, not a UI warning.
- Safeguard
Restrictions cannot be dropped
A restricted designation is a property of the gift, not a note. Downstream allocation reads it, and an allocation that contradicts it is an exception.
- Safeguard
Recorded fee coverage
If a donor elects to cover fees, the gross, the fee and the receiptable amount are stored distinctly so the receipt is defensible.
- Safeguard
Versioned forms
Editing a live form creates a new version. A gift always references the version the donor actually saw.
The boundary
Did everything the donor told us survive the payment step?
A contribution arrives carrying instructions: this fund, this restriction, every month, in memory of someone, from this appeal. Most checkout flows keep the amount and drop the rest. Beneora treats those terms as part of the gift.
A contribution arrives carrying instructions: this fund, this restriction, every month, in memory of someone, from this appeal. Most checkout flows keep the amount and drop the rest. Beneora treats those terms as part of the gift.
Scope honesty
What this is not
Naming the boundary is more useful than implying there isn't one.
- We are not a payment processor and do not hold funds.
- We do not build a website CMS — forms embed into the site you already have.
- We do not run a donor marketplace as part of Release 1; that surface is a contained prototype.
Questions
Giving & payments, answered directly
Design-partner program
Shape giving & payments with us
We are working with a small number of US and Canadian nonprofits who feel the reconciliation and donor-data pain most acutely. Partners shape the sequence, see the honest status of every module, and are never charged for a capability that is still a prototype.