Participant proof ledger
Contribution state and proof ledger
Contribution intents stay conditional: identity, threshold, destination-proof, challenge-window, and milestone-release gates must all clear before anything becomes payout-relevant.
Plain-language contribution summary: each accounting channel is labeled separately, so gross captured, fees, net recipient-disbursed dollars, actual contributions, counted dollars, match-eligible dollars, sponsor support, rewards, credits, and certificates are never merged into one unlabeled impact number.
- Maximum this round
- $0
- Current state
- no charge
Plain summary
- Charged from you: $0.
- Sent to project: $0.
- Counts for matching: counted contribution: $0; match-eligible contribution: $0.
- Sponsor added: sponsor base match: $0; sponsor bonus match: $0.
- Contributor benefit: success rewards: $0; coordination credits: 0 credits; impact certificates: 0 certificates.
- Failed or carried forward: failed allocations: $0; carry-forward credit: $0; failure bonus or carry-forward credit: $0.
Summary numbers keep accounting channels separate: sent-to-project dollars exclude fees, rewards, credits, certificates, base match, and bonus match unless separately labeled.
Technical accounting details
- Gross captured
- Fees
- Net recipient-disbursed
- Actual/gross exposure
- Counted contribution
- Match-eligible contribution
- Base-match claim and paid amount
- Bonus-score units and bonus-match paid amount
- Failure-bonus claim state and denial reason, if any
- Success-reward / coordination-credit / impact-certificate state
- Review, threshold, challenge, payment, and authorization reconciliation states
The final receipt uses this same separated technical ledger; the plain summary cannot collapse these fields into one impact number.
- Failure bonus or carry-forward credit
- $0
- Identity status
- Sign in required
- Threshold status
- Sign in required
- Destination-proof status
- Sign in required
- Challenge-window status
- Sign in required
- Payout milestones
- None scheduled
- Gross captured
- $0
- Fees
- $0
- Net recipient-disbursed
- $0
- Actual contribution
- $0
- Counted contribution
- $0
- Match-eligible contribution
- $0
- Sponsor base match
- $0
- Sponsor bonus match
- $0
- Success rewards
- $0
- Coordination credits
- 0 credits
- Impact certificates
- 0 certificates
- Proof state
- no payment proof
Sign in to save MPGF participant state across sessions.
Public goods assurance
Conditional campaign pledges
These pledges are tied to public-goods campaigns and count only after amount, verified-supporter, review, and evidence gates pass.
Sponsor-pool refills
Optional recurring sponsor support
These records refill future challenge budgets. They remain separate from one-time campaign pledges and do not imply custody or tax treatment.
Pledge-only records
Pledge rehearsal records
Pledge rows can be cancelled, converted, or expired. Pause and resume controls live on monthly recurring commitments. These records help test the mechanism before evidence is reviewed.
Monthly recurring commitments
Standing pledge rehearsal instructions
These controls operate on pledge-only recurring commitments. They do not create subscriptions, charges, donations, payment-provider objects, or live budget effects.
Sign in to view and update persisted MPGF participant state.
Stripe-backed contributions
Real-money payment state
These rows come from webhook-backed MPGF contribution records. They are separate from pledge-only rows and depend on Stripe and Supabase production configuration.
Manual external-payment evidence
Open Collective or fiscal-host evidence
Manual evidence rows are participant-submitted records awaiting MPGF review. They do not become verified contribution accounting until review explicitly verifies them.
- Sign in to save MPGF participant state across sessions.