Connect the intended purchase to the cause you mean to support
For a One Lottery purchase motivated by a particular good cause, keep the named cause, purchase route and allocation statement together. The total you commit and the amount described as supporting a cause are different fields. A payment record alone does not prove that the intended organisation received funds.
This review reads a player FAQ and a fundraiser-facing explanation. Neither reading is a customer transaction test or a verified remittance to a cause. The governing player terms and a particular cause's page were not reviewed.
What the two audiences are told
Choose a good cause; at least 50p per £1 ticket supports causes. Player FAQ
Fundraisers receive 50% of ticket sales from supporters signing up via their page. Fundraising
These are selected operator declarations. Keep their audiences and wording separate. Do not turn a fundraiser-facing statement into proof of your purchase, a player contract or a remittance already made to your intended beneficiary.
Record the cause beside the intended order
Our worksheet connects each question to its evidence rather than treating a general allocation headline as the answer to every purchase route.
| Field | Evidence to keep | Question before purchase |
|---|---|---|
| Intended beneficiary | Exact cause name and selected page | Is this the organisation you mean to support? |
| Purchase route | The page or route used for the intended order | Which allocation statement applies to this route? |
| Purchase scope | Selected entries, events, period and total | What does the whole payment buy? |
| Allocation description | Its amount or basis, audience and relevant condition | Which part is described as supporting the named cause? |
| Accepted order | The actual reference and recorded selection, if available | Does it connect the intended order with the intended cause? |
| Beneficiary receipt | Separate evidence of a remittance, if one exists | What establishes receipt rather than a published promise? |
Do not replace an unknown field with an answer about another cause, another purchase route or another period. An allocation declaration does not make the entire ticket payment a donation. It also does not reduce the total money committed to the order. Use the service-cost worksheet to keep that total visible.
An invented cause-selection enquiry
Imagine that Mara intends to support a fictional Harbour Community Group. She keeps that cause's selected page and the planned order in one file. A later confirmation identifies an order but does not identify the cause in the record she has. Her first question is whether the accepted selection matches the intended cause and which allocation statement applies to that route. If the reply identifies those fields, the separate question of whether funds reached the group still needs its own evidence.
This example is invented. It supplies no actual confirmation layout, tested purchase, tax treatment, beneficiary eligibility or guaranteed charitable payment. Keep later replies attached to the specific question they answer.
Compare the purpose as well as the total
If supporting a named organisation is essential to the decision, retain that criterion beside the entry and prize questions. A service offering another participation model is not an equivalent charitable purchase solely because it offers lottery-related products. The charity and postcode lottery guide explains why the model belongs in the comparison.
If the planned purchase continues over time, identify its future commitments with the subscription checklist. A statement about one intended order does not settle every later period.
Questions still open
We have not established the complete current order cost, draw coverage, accepted player terms, personal admission, independently verified licence status, tested claim performance or actual beneficiary receipts. The source edition is unknown. Use the operator-and-licence checklist for the separate authority question rather than treating this document review as that finding.
Ask through the verified private channel with the named cause, intended route and missing field. Keep account credentials and full ticket or payment records private; a public review does not need them to express the unresolved question.