Community eWallet use case

Community eWallet Platform

A community use-case of the Allxs digital wallet platform for member groups and programmes that need shared balances, top-ups and repeat community spend.

Overview

This page is the community use-case of the Allxs digital wallet platform. It is for member organisations and community programmes that issue a shared wallet so members can top up, spend on approved community activity and review that spend. The wallet product parent is the Digital Wallet Platform. The stored-value capability lives on the digital wallets module.

Problem to solve

Community programmes often mix cash, paper vouchers and one-off payments, so members cannot carry value between activities and organisers cannot see what was issued and used.

A use-case of the wallet parent, not a second wallet product

The community eWallet uses the same stored-value model as the Digital Wallet Platform. Stay here when the buyer is choosing a wallet for a member group or programme. Open the parent page when the product itself is the comparison, and open the digital wallets module when the need is the stored-value capability.

Member groups and programme spend

Issue a shared balance to members, take programme top-ups or funded allowances, and limit spend to approved community activity. This page does not own school commerce, event trading or standing venue operations.

When to open the community environment instead

If the need is the wider community operating environment — activations, stall payments and local programmes around a wallet — use the communities solution page. This page stays on the wallet used inside that environment.

School, event and canteen commerce stay on their owners

Parent-funded student wallets belong on Cashless Schools. Attendee event value belongs on Cashless Event Solutions. Workplace dining allowances belong on the canteen pages. Link out to those owners instead of repeating them here.

Buyer fit

Best for

Member organisations and community programmes that need a shared wallet for repeat community spend.

Better choice when

Use this page for a community wallet use-case. Use the Digital Wallet Platform when comparing the wallet product. Use the digital wallets module for the stored-value capability.

Common mistake

Do not treat this page as the wallet product parent, the stored-value module, or the communities operating environment.

Detail

Member and programme wallets

Issue a shared balance to a defined member group or community programme, not a generic guest checkout.

Detail

Approved community spend

Limit value to the activities, stalls or services the programme already intends to fund.

Detail

Repeat transactions in one group

Let the same members top up and spend across recurring community activity without starting a new payment each time.

Detail

Not school, event or venue commerce

Those environments have their own commercial pages. This page only covers the community wallet use-case.

Reporting and control

  • Keep this page as the community wallet use-case, not a second product page for stored value.
  • Send school, event and canteen buyers to those commercial owners instead of repeating their journeys here.
  • Use the communities solution page when the need is the operating environment around the wallet.

How it works

A clear workflow from setup to daily operations.

  1. 01

    Define the member or programme group

    Decide who holds the community wallet and which activities the balance may fund.

  2. 02

    Issue and fund the wallet

    Load member top-ups or programme allowances onto the shared wallet model.

  3. 03

    Spend on approved community activity

    Members use the balance at the community points the programme has already set.

  4. 04

    Review issuance and use

    Organisers see what was loaded, spent and left on the community wallet.

FAQ

Common questions from buyers evaluating this use case.

How is this different from the Digital Wallet Platform?

The Digital Wallet Platform is the commercial wallet product. This page is one use-case of that product: a community eWallet for member groups and programmes.

How is this different from the digital wallets module?

The module explains stored value as a platform capability. This page is the community commercial use-case of the wallet product.

How is this different from the communities solution page?

The communities page is the operating environment: programmes, allowances, activations and stall payments. This page is the wallet used inside that environment.

Who is a community eWallet for?

Member organisations and community programmes that need shared balances, top-ups and repeat community spend. School, event and canteen buyers should use those commercial pages.

Ready to talk

Discuss a community eWallet for a member group or programme.

We can show how a community wallet sits on the Allxs digital wallet platform without treating this page as a second wallet product.