From quiet request to confirmed help

Verification before action. Direct support instead of pooled money. Truthful follow-through after help happens.

Help someone directly Submit a request

The core flow

Private intake. Real review. Direct support.

Each step reduces fraud, protects dignity, and keeps public claims grounded.

1. Private request

A person, family member, or trusted local contact submits the need quietly.

2. Human review

Identity, locality, need, proof, and the safest support route are checked first.

3. Direct support

Help goes directly, then the public ledger moves only as proof and confirmation arrive.

Support modes

The cleanest route comes first

Direct vendor or institution payment should appear before higher-risk routes where possible.

Direct vendor or institution payment

Best for school fees, medical bills, pharmacy support, utilities, and other traceable routes.

Direct beneficiary UPI

Enabled selectively, with higher review and proof expectations.

Non-cash goods support

Useful for ration, blankets, mobility aids, supplies, and other item-specific help.

Volunteer and service support

Transport, tutoring, paperwork help, hospital accompaniment, and similar service needs.

Proof and confirmation

A click is not confirmation

After helping, supporters upload proof. The ledger moves to claimed paid, then to confirmed received only after confirmation.

This separation prevents public numbers from becoming flattering fiction. It also reduces pressure on the platform to imply custody over transactions it does not control.