What Your Donors See in Your Giving

Every donor who has given through Together can sign in at alltogether.giving/giving with their email alone, see their giving organisation by organisation, open any receipt and have it re-sent, and cancel, pause, re-price, re-card or move a regular gift onto direct debit without contacting you. It is on for every organisation, on every plan, with nothing to configure.

A donor emails your team twice a year: once for a receipt they have lost, once to ask what they gave last financial year. Both are answers Together already holds, and both cost your team a search and a reply.

"Your giving" is the donor's own view of those answers. It lives at alltogether.giving/giving, it is free, and it is on for every organisation.

How a donor gets in

There is no password and no account to create.

1. The donor enters their email address.
2. If Together holds giving under that address, they get a link that lasts 15 minutes and works once.
3. Tapping it opens their giving straight away - there is no second step - and keeps them signed in on that device for a week.

If Together holds no giving under that address, they get a reply saying so. Either way the screen says the same thing, so nobody can use the form to find out whether a stranger gives to you.

How a donor finds it in the first place. Four of the emails Together sends a donor end with a "See all your giving" line, and the /donate and /give success screens carry the same line the moment a payment goes through. The link opens the sign-in form with the donor's own address already in the box - nothing more. It is not a way in: they still have to ask for a link and open it from their inbox, which is the point. A donor who no longer has any of those emails gets there from the Your giving link in the footer of alltogether.giving, under Platform.

Which emails carry it, and which deliberately do not, is in Emails your donors receive. The rule behind the list is one sentence: the line appears only where the gift it sits under is already something the portal can show. A bank debit takes a few business days to clear, so the receipt carries the line and the processing notice before it does not - a donor who followed a link while their gift was still settling would be told no giving was found under their address, minutes after giving.

A link works once, and a week is longer than a link lasts, so a donor who re-opens an old email lands on one of two screens: their giving, if they are still signed in on that device, or "this link has already been used", with a button that sends a new link to the same address. Neither is an error they have to do anything about.

Signing in ends any other session on that address. A donor who signs in on their phone is signed out on their laptop. That is the deliberate trade for the longer week: the donor always has a way to end a session they did not start, without contacting you.

What they see

The portal has three levels, and the first one is an overview.

Organisations is what a donor lands on. At the top is one figure: their lifetime giving, and to how many organisations since when. It counts settled gifts only, each dollar once - and since September 2026 it counts both the gifts Together processed and the gifts you recorded yourself, because a donor does not think of their giving as belonging to one system or another. A second line names the two halves, so the figure is never ambiguous about which is which: "$3,990 processed by Together · $1,220 recorded by organisations". A donor with no settled giving at all sees no figure; one gift is a figure, and it is the gift's own amount.

Below it is one tile per organisation - your logo, your name, what they have given you and since when, the state of any regular gift, and how many gifts sit behind it. Nothing opens in place; the tile is a link.

An organisation is the second level, and it holds everything that donor has with you:

• Regular gifts that are still running: the amount, how often, and when the next payment is due. One that has missed a payment says so. Each opens its own page. A regular gift that has ended is listed too, under its own "Ended" heading below the running ones - "$50.00 monthly · ended Dec 2025 · $1,240.00 over 29 payments" - as long as it collected at least once. It opens a read-only page: when it started, when it ended, what it gave in total, and every payment with its receipt. Nothing on that page can be changed; a gift that never collected a single payment has no page and is not listed. The overview tile and the Regular gifts tab show running gifts only.
• Gifts you recommended, where a donor made one gift through you to the organisations you recommended (see below).
• One list of every gift with you, newest first - regular-gift payments, one-offs, parts of a recommended gift, and the gifts you recorded yourself - each row saying which kind it is. A payment of a regular gift that has since ended says so on its row ("gift ended Dec 2025"). A month a regular gift was not collected is shown as well, in its place in the list, as "Payment declined · not collected" with the amount struck through - the donor sees that their bank declined it, and never the reason Stripe gave you. It opens nothing and counts for nothing: not in the number of gifts, not in any figure. A month that was declined and then recovered shows only the payment that went through. Six show, and "Show all" expands the rest in place, grouped by calendar year; there is no paging and no cap. A refunded gift is shown and labelled as refunded; a gift you refunded part of keeps its receipt and is labelled with the amount that went back, and the figures count only the part you kept. A recipient's part of a RECOMMENDED gift that was partly refunded is different: it is left out of the figures entirely, not counted net, because until your team resolves how that refund divides across the recipients, nobody knows what this recipient's part of it was. The row is still listed and still shows what was sent at the time - it is the recommended gift's own page, under the organisation that took the payment, that says money came back.

Their photo. Beside "Giving as [their name]" at the top of your organisation page is the donor's picture - the photo on your record, else their initials. The donor can click it to add a photo, change it or remove it, and it is the same photo your team sees on the donor's page: PNG, JPEG, GIF or WebP under 4MB, cropped to a square from the centre. Removing it also stops Together copying in a Gravatar picture for that address. The photo is per organisation: a donor who gives to two organisations sets each one separately. Where an address is two donors on your records - a person and their company, or a shared inbox - there is no picture and nothing to click, because the portal cannot tell which of the two is signed in. Your team can still remove any photo from the donor's page.

The third level is the documents: a receipt, a recommended gift, or a gift record. Each row on the list above opens the right one.

Regular gifts is the second tab, and it is the same thing from the other direction: every regular gift this donor has, across every organisation, in one list. Each opens its own page, where the donor can act - see below.

What a donor can do with a regular gift

Opening a regular gift shows the amount, how often it is charged, when the next payment is due, when it started, what it is paid by and what it has given so far - and six things the donor can do without contacting you.

Cancel it. The gift stops immediately: no further charge, and the record of every past payment stays in their giving. Together asks for a reason and says plainly that it is optional and that it is shared with you - "I can't afford it right now", "I'm giving in a different way", "I no longer support this organisation", "Something about the process", "I'd rather not say" - plus a free-text box if they want to add anything. The donor gets the same "your regular gift has ended" email your team's own cancel sends; nobody is emailed twice.

Pause it. A donor who cannot give right now can stop the gift instead of ending it: skip the next charge, or pause for one, two or three months. Nothing is charged while the pause lasts, the amount and the schedule do not change, and the gift restarts on its own - there is nothing for the donor or for your team to remember. The gift reads "Paused" wherever it appears in the portal, with the date it resumes.

Three things to know. The resume date is not a charge date: collection restarts then, and the first charge is the gift's usual charge date after it - so a gift paused until 21 November next charges on its normal December date, not on 21 November. A pause cannot be undone from the portal - there is no "resume early" control, so a donor who changes their mind contacts you, and your team can restart collection from Stripe. And a gift with a failed payment cannot be paused: the unpaid invoice would stay outstanding behind the pause, so the donor is asked to settle it (or to contact you) first.

"Skip the next charge" is about the gift's own cycle, not about a month - a yearly gift eleven months from renewal skips eleven months of waiting, because skipping one charge is what the donor asked for.

The donor is emailed; your team is not. "Your monthly gift to [your name] is paused until 21 November" goes to the gift's own donor, which is what catches a pause somebody else set from a forwarded link. Your team sees it on the audit log, with the resume date, attributed to the donor.

Change the amount. A donor can set a new amount for the gift without contacting you. It carries on otherwise exactly as it is - same schedule, same card or account, same everything else - and the new amount applies from the next payment, never to one already under way. Nothing is charged or refunded at the moment of the change.

Four things to know. Your own form's limits apply: the amount has to sit between the minimum and maximum on the donation form the gift was set up through. The sheet does not read those limits out up front - it refuses an amount outside them and names the limit it crossed ("The smallest amount for this gift is $10.00"). A gift with a failed payment cannot be changed - the unpaid invoice is still being retried at the old amount, so the donor is asked to settle it or to contact you first. A paused gift CAN be changed, and the pause sheet offers it as an alternative to pausing at all: "Or keep it going at a smaller amount". And if a payment is already on its way - Together prepares each payment shortly before it is taken - that one goes through at the old amount, and the portal says so rather than promising the new figure.

The donor is emailed, with both figures. The subject reads Your regular gift to [your name] is now $60.00, and the email itself says what it changed from and when the new figure starts. It goes to the gift's own donor, which is what catches a change somebody else made from a forwarded link. Your team sees it on the audit log, with both amounts, attributed to the donor. There is no webhook event for an amount change; tell us if you need one.

Update the card. The donor enters a new card and the gift carries on at the same amount on the same schedule. Together emails them to say the card changed - to the gift's own donor, which is what catches a change somebody else made. No card number, brand or last four digits is shown anywhere in the portal or in that email.

Change how it is paid. A card gift can be moved onto direct debit, and a gift already on direct debit can change bank account or move back to a card. The amount and the timing do not change: only where the money comes from. The gift's own page says which it is on, as "Card" or "Direct debit".

Direct debit is set up through Stripe's own bank form, which carries the Direct Debit Request and the service agreement the donor has to agree to - that text names your organisation as the merchant, because the authority is to debit on your behalf. Together stores none of it: no BSB, no account number, no last four digits, on the page, in the email or on the audit log. A fresh authority is collected every time; nothing is reused or copied from an old one.

Four things to know. A gift with a failed payment cannot be switched - the unpaid invoice is still being retried on the old method, so the donor is asked to settle it or to contact you first. A paused gift CAN be switched, and the pause is untouched. The first debit comes out on the gift's usual date - a switch does not bring a charge forward, and direct debits take a few days to clear once they are taken. And direct debit is only offered if your Stripe account can actually collect it: if that capability is not active, the donor sees no direct-debit option at all rather than signing an authority that could never be used. A gift already on direct debit can always move back to a card either way.

There is also a short window each cycle - about an hour, while Together is preparing that cycle's payment - where a switch BETWEEN methods is declined with "a payment for this gift is being prepared right now". That payment would otherwise go out on the new kind of method at the fee set for the old one, so the donor is asked to come back in a couple of hours. It only applies when the KIND of payment method changes: replacing a card with another card, or a bank account with another bank account, goes through at any time - which matters most for a donor fixing a dying card just before a renewal.

There is one thing your team should know that the donor does not see: the platform fee moves with the rail, automatically, in the same instruction that changes the payment method. See Pricing.

The donor is emailed. The subject reads Your regular gift to [your name] is now paid by direct debit, and the email says the amount and the timing have not changed. It goes to the gift's own donor, which is what catches a change somebody else made from a forwarded link. Your team sees it on the audit log, with the rail it moved from and the one it moved to, attributed to the donor - and never a bank or card detail. There is no webhook event for a rail change; tell us if you need one.

Pay a missed payment. A gift whose last payment failed says so, explains that it picks up again on its own if the next payment succeeds, and offers to make up the most recent missed payment now. Nothing is ever charged without a second, explicit confirmation naming the amount. If the donor's bank wants to check the payment with them, Together says so and charges nothing - it does not retry, and Stripe's own retry schedule carries on regardless. If the card is simply declined, the donor is told to update the card rather than to try again.

One limit to know about: the control settles the most recent missed payment, not every one. A gift that has been failing across two or more cycles has an older unpaid invoice behind it, and paying here does not clear that one - so a donor can pay and still show as lapsed. Your team settles the rest, or the gift recovers on its own as Stripe retries. Tell us if this comes up and we will build the multi-payment version.

Two limits are worth knowing:

• "Update card" is for card gifts. A gift on direct debit gets "Update bank account" instead, which collects a fresh authority. A gift on PayTo, or one whose payment method Together cannot read at that moment, gets neither and says "To change how this gift is paid, contact [your name]" - it will not guess, and PayTo is not something the portal can set up.
• The schedule cannot be changed yet. A donor who wants to give monthly instead of yearly still contacts you. The amount and the payment method CAN be changed - see above.

Each of these controls names the donor's own email address, your organisation and the amount, immediately above the button that acts - so a donor who opened somebody else's emailed link reads whose gift it is before they change anything.

Gifts you recommended

A donor who made one gift through you to the organisations you recommended sees that as its own page - the recommended gift: the total they were charged, where their gift went and how much each organisation received, the date, and a line saying that each amount also appears as a gift under the organisation that received it. It is reached from your organisation page, under "Gifts they recommended", and each recipient's part also appears under that recipient. The donor reads it as "These gifts were based on a recommendation from [your name]" - a gift the donor made, on your recommendation.

The recommended gift is the only document Together issues in its own name, and it says so: not a receipt, each organisation issued its own.

A recipient's part is headed "Your gift to [the recipient]", not "Your receipt". The donor did not give to that recipient directly; the document is the notice that recipient sent them about their recommended gifts, and it carries that recipient's ABN. The page says as much above it: "This is the notice [the recipient] sent you about your recommended gifts. Your own record of the whole gift is on the organisation you gave through." Calling it the donor's receipt would tell them they gave that amount to an organisation they never chose to pay.

The recommended gift carries the same pair of controls as a receipt does - "Email me the summary" and "Print", side by side above the document. What the email sends is the summary of the whole gift, not a tax receipt: the receipts are the per-recipient ones.

If the money went back - a full refund or a lost chargeback - the recommended gift is labelled refunded and the summary can no longer be emailed, because it would itemise money the donor no longer has; Print stays. A partial refund on a recommended gift is the same: the page says how much came back, and the summary is held until your team has resolved how that refund divides across the recipients. While it is held, each recipient's part drops out of the donor's totals altogether rather than being reduced by a guess - so the rows under those recipients can add up to more than the figure above them, and that is the page being careful rather than wrong.

Gifts you recorded yourself

A gift that came from your CRM, a CSV import or a bank statement is on the donor's record, but Together did not take the money and did not issue a receipt for it. Those gifts are listed on your organisation page alongside the ones Together processed, each row saying "Recorded by [your name] · not processed by Together", and each opening a gift record rather than a receipt.

A gift record is deliberately not a document. It has a dashed border, no logo, no ABN, no message from you and no Print button, and it says in as many words: "Together did not process this payment, so there is no Together receipt for it. This is what [your name] holds on its own records. For a receipt, contact [your name]."

What it shows is a fixed, short list and nothing else: the date, the amount, the currency, and whether you recorded it as a donation or an in-kind gift. Your own reference for the gift, the revenue code you filed it under, any notes, and the raw record your CRM sent are never shown - they are your working record, not the donor's.

Three rules bound which of these gifts count:

• In-kind gifts are listed but carry no dollar figure, on the row or on the record. The value of a non-cash gift is your own assessment of it, not money the donor handed over, so Together will not put a number on it in front of them.
• Only AUD gifts are shown. A gift recorded in another currency is neither summed into your figures nor listed as a row, because converting it would mean picking a rate nobody chose. It is counted, though: your tile and your page carry one line saying "3 gifts recorded in another currency - not included in these figures", so the donor can see that something of theirs is missing from the totals and ask you about it, rather than finding a figure that is quietly short.
• A refunded one counts nothing, the same as a refunded gift Together processed.

Underneath the list, the donor gets your website address and your notification sender address, whichever you have set - so a request for a receipt you do hold lands with you rather than with support.

Both come from your existing settings. The website is the one on your organisation profile; the sender address is the one under Settings → Engage, and it is only shown once that sending domain is verified - an unverified one is an address your donors have never received mail from. If neither is available, the line tells the donor to contact you by name and gives them nothing to click, which is worse for them and for you.

Receipts

Opening a gift shows the receipt Together emailed at the time - the same document, not a reconstruction of it. The donor can print it, or have it emailed again to the address they signed in with.

A re-send spends the same budget as a re-send from your dashboard: five per gift per 24 hours, counted together. A donor working through last year's giving cannot flood their own inbox, and they cannot exhaust a budget your team needs, because five sends of one receipt in one day is already past the point where something else is wrong.

Only a confirmed gift has a receipt. A fully refunded one appears in the list, labelled, with nothing to open; a partly refunded one keeps its receipt, which is the document you issued at the time.

Sending a donor their sign-in link

A donor who phones to ask how to see their giving does not have to find the form themselves. On their record, under the email address on the Contact information card, an EDITOR or ADMIN has a Send sign-in link button. One press sends the same link the donor would get by asking on the portal - to the address on the record, lasting 15 minutes, working once - and the card says "Link sent to [their address]".

Three things to know. The link opens the donor's whole giving, across every organisation that holds that address, exactly as their own request would; sending it from your record does not narrow it to you. It refuses rather than sending a dead link: a donor whose only giving with you was imported from your CRM, or whose gifts never went through and who has no running regular gift, is told "This donor has no giving the portal can show". A donor marked do-not-contact, or with no email address, is refused too. It shares the donor's own limit of five links an hour to one address, so it cannot be used to fill an inbox. Every press is on the audit log under your organisation, attributed to the staff member, whether it sent or not.

What it does not do

• It cannot change a donor record. Not the name, not the address, not the email. The only donor-initiated change Together accepts is the one confirmed from a receipt - see How Together protects your donor record. Their own photo, how a regular gift is paid, and whether and when it charges, are the only things a donor can change here.
• It cannot show giving under a second email. A donor who gave to you at work and to another organisation at home sees two portals, one per address.
• It cannot be turned off per organisation. The donor's own giving history is theirs; an organisation-level switch would be a switch over somebody else's record.

What your team sees

Every re-send is on the audit log, attributed to the donor rather than to a staff member, and under the organisation whose gift it was. A re-sent receipt also appears on that donor's Activity tab, beside the sends your team made.

The same is true of everything a donor does to a regular gift. A cancel, a pause, an amount change, a card update and a made-up payment each land on the audit log under your organisation, attributed to the donor - a donor cancel sits beside a staff cancel under the same words, with the actor saying which it was. A cancel your donor made carries the reason code they picked; the free-text note they typed is kept on the gift itself rather than on the log. A pause carries the date it resumes, and an amount change carries both the old figure and the new one.

A photo the donor adds or removes is on the audit log too, under your organisation and attributed to the donor, and shows on the donor's page and in your donor list straight away.

A paused gift says so on the donor's page, on the Regular gifts card: "Paused", and "Paused until 21 Nov 2026" where a running gift says "Paid through". That matters more than it sounds - while a gift is paused its paid-through date keeps moving even though nothing is being collected, so the card states the pause instead of a date that would be wrong.

There is no webhook event for a pause or for an amount change. If you need to know when a donor does either, the audit log is the place, and tell us - we will add the events rather than guess at them.

If you receive Together's webhooks, the existing subscription.cancelled event now carries two extra fields, donor_cancel_reason_code and donor_cancel_reason. They are filled only when the donor cancelled in the portal, so their presence is how a receiving system tells a donor's own cancel from one your team or a failed payment caused.

What to do next

• Set your contact pathway so the organisation-recorded note has somewhere to point: your website on the organisation profile, your verified sender address under Settings → Engage.
• Read what a donor can and cannot change: How Together protects your donor record.
• Check what else Together emails donors: Donor emails and receipts.