Feature hub

7Grant platform features

7Grant is built from five groups of components: identification channels that need no app, entitlement types and spending controls, merchant tooling on existing hardware, evidence and integration, and security with on-premise deployment. Together they let a programme restrict how aid is used without asking anyone in the chain to adopt new software.

  • No app to install
  • Enforced at checkout
  • Existing POS terminals
  • On-premise option

Last updated

Browse by group

Each group answers one question a programme team asks when it evaluates a delivery platform.

Access without an app

Beneficiaries reach assistance through channels they already carry. Nothing to download or register.

01

Wallet cards

A beneficiary saves a programme card to Apple Wallet or Google Wallet from a single link. No app store, no account creation, no password.

Used in

Instant payment
02

Messenger bots

Balance enquiries, dynamic QR payment, receipt submission and a two-way channel back to the programme, in WhatsApp or Telegram.

Used in

Instant payment
03

Phone and anonymous cards

A phone number spoken at checkout, or an anonymous plastic card with no personal data. Routes for feature phones, no handset and protection contexts.

Used in

Category limits
04

Flash-call authorisation

An unanswered incoming call whose last four digits are the code. Cheaper than SMS at scale, which matters across millions of confirmations.

Used in

Category limits

Entitlements and spending controls

Permitted categories, blocked categories, daily and monthly limits, enforced at checkout rather than audited afterwards.

01

Spending controls

Permitted and blocked categories with daily and monthly limits. The rule is checked at the moment of purchase.

Used in

Category limits
02

Commodity accounts

Accounts denominated in litres, kilograms and kits rather than currency. Goods are issued against the balance, so the entitlement cannot become cash.

Used in

E-vouchers
03

Beneficiary accounts

One person, several accounts, different rules on each. A strict ration and a flexible allowance can coexist on one beneficiary.

Used in

Category limits
04

Deduplication

Beneficiaries exist as single records holding multiple accounts, so one household assisted by three programmes is visible as one household.

Merchant network

Merchants accept 7Grant on hardware they already own. No second device on the counter.

01

POS terminal acceptance

The programme runs on the acquiring terminals merchants already operate. No hardware purchase, no certification.

Used in

E-vouchers
02

Scanner app

A light application on the merchant's own smartphone: check a balance, choose a category, read a voucher. For retailers with no terminal.

Used in

Category limits
03

Merchant whitelist

Only vetted merchants can receive programme funds. An unlisted merchant cannot be paid at all, and removal takes effect immediately.

Used in

Instant payment
04

Web and portal widgets

A payment module embedded in a government service or commercial site, so targeted funds can pay utilities, pharmacy orders and fees online.

Evidence and integration

Donor reports assembled from the transactions themselves, not from field returns.

01

Donor reporting

Every transaction records account, merchant, category, amount and time. Reports are assembled from those records.

02

Receipt capture

The beneficiary photographs the receipt in the chatbot, and the image is filed against the transaction the platform already authorised.

03

API and integrations

An existing registry upstream, financial service providers downstream. Records import and export in full, because portability is a buyer's right.

Security and deployment

Defence in depth for beneficiary data, with the option to run inside your own perimeter.

01

Defence in depth

Isolated storage, separated components, role-based access, encrypted transport and full audit logging.

02

On-premise deployment

Run 7Grant inside your own security perimeter, with the database isolated from external networks and personal data kept in your jurisdiction.

03

Beneficiary data protection

Designed around a second question beyond lawfulness: what happens to this person if the data is compromised, subpoenaed or seized.

Next step

See the platform against your programme

Walk through the features that matter for your caseload, markets and security requirements.