Cash App is ubiquitous because it is easy—not because it exposes coordinator-grade reporting APIs for every vendor. MoneyLayer’s stance is honest: treat Cash App as structured self-report with optional screenshots.
If your market pretends Cash App does not exist, you will still get Cash App screenshots in DMs—so the policy question is whether you want them inside a structured intake with timestamps, or scattered across channels.
Connected where possible. Structured self-report where it isn't. Every number carries freshness, coverage, and provenance.
At-a-glance matrix
| Capability | Connected | Self-report |
|---|---|---|
| API-grade connected totalsDesign policy for personal vs business cashtags up front. | No | Required |
Setup
Organizer-side
- Ban ambiguous “send me whatever” threads; use one structured link.
- Require one attachment when totals look rounded or inconsistent.
- Write a simple rule for personal vs business cashtags if you allow P2P at all—ambiguous identities create Monday rework.
Vendor-side
- Screenshot the Activity view that matches the market’s gross definition.
- If you share a cashtag with a family member, separate flows before the market asks uncomfortable questions.
What data we pull
- Submission fields + attachments + timestamps.
- Optional metadata: booth number, payment method mix, and notes about split booths.
What we cannot do with this POS
- No product can ethically ‘pull’ peer payments without vendor action.
- Cash App risk controls can delay or hide activity—your deadline policy should mention what to do when the app does not show Saturday yet.
FAQ
Why not ban Cash App?
Because vendors will use it anyway—your job is to make reporting legible.