WhyDonate

The identity was developed to work consistently across nineteen languages without redrawing. The symbol and wordmark separate cleanly, so the symbol carries the brand at small sizes — in the app icon, and within the donate button embedded on third-party websites.

The colour system is intentionally restricted. A single green marks the donation action; deep forest supports the trust surfaces — fees, safeguarding, data residency; a neutral base lets fundraiser photography lead. Associations were reviewed across markets before rollout.

A single type scale, with a typographic role assigned to each feature: campaign pages read long and quiet so the fundraiser's words lead; the donation sheet sets the amount larger than everything around it; dashboards run the densest setting in the system.

Typeface selection prioritised matched-weight coverage across Latin, Greek and Cyrillic, and true tabular figures — amounts, fee breakdowns and payout tables are read in columns, and figures that change width undermine confidence in a financial product.

Each component ships with usage guidance, accessibility notes, localisation behaviour and the reasoning behind the decision, so engineering implements directly rather than interprets from a mockup. Design tokens are delivered as code, from a single source.

Design review is carried out per locale rather than per screen — wrapping, truncation and misplaced currency symbols are rarely visible to a team that does not read the affected language, so the language set is reviewed as a whole, longest strings first.

Donating is an emotional act carried out through a financial interface. The donation flow was rebuilt as a single continuous sequence, and fundraiser pages restructured to lead with the person and the story rather than the mechanics.

The organiser journey was mapped end to end — create, share, payout — and rewritten so each stage explains what happens next. Fee breakdowns, verification and payout timing are visible parts of the journey, because transparency is the platform's central promise.

Nineteen interface languages, twenty-seven donation currencies and eighteen payout currencies resolve from a single codebase, with components already tested against the string lengths and scripts each market requires.

Payments were consolidated onto Stripe — one integration, one checkout pattern, with the local method presented first by country: iDEAL in the Netherlands, BLIK in Poland, Swish in Sweden, MB Way in Portugal, among 24 methods.

Plugins and connectors for WordPress, Wix and Zapier were built alongside an embeddable donate button, QR codes and payment requests for collecting in person — components that stay recognisably WhyDonate on host sites we could not see in advance.

Fundraisers were opened up to personalisation: organisers adjust imagery, colour and layout, organisations apply their own branding on custom domains — while the components hold their structure, accessibility and localisation rules regardless of configuration.