Tap, scan, or choose a trusted person.
The first action is human and local. The user does not begin inside a dense wallet dashboard.

BUMP is a ritual-first payment surface: tap the fist, reveal payment intent, route through Bitcoin-native rails, and keep the person in control of custody, privacy, and settlement context.
Balance, rails, and counterparty state stay quiet until the user acts.
BUMP lets people understand Bitcoin through a simple action: connect with a person, choose intent, and settle through the appropriate rail.
For SASCOSM, BUMP is a practical entry point into adoption readiness: a visible experience that makes self-custody, Lightning, BTCPay, QR, and trusted contact flows easier to explain.
The first action is human and local. The user does not begin inside a dense wallet dashboard.
BUMP reveals only the action needed for the moment, then keeps the rest of the wallet quiet.
The infrastructure is Bitcoin-native, but the user story stays simple enough for real adoption.
The user needs settlement context and counterparty clarity, not unnecessary platform-owned identity exposure.
Many payment systems push people into accounts, permissions, fees, custody risks, and platform dependency. BUMP makes the payment moment human again, then lets Bitcoin rails do the settlement work behind the gesture.
No public balance exposure. No unnecessary disclosure. The product should feel private before it feels financial.
BUMP should help people move away from custodial dependence without making the first interaction feel technical.
Most users do not care about payment infrastructure until it solves a moment they already understand.
BUMP is the experience people can touch. BAF reviews custody, commerce, treasury, privacy, energy, and education around deployment.
Pay, request, repay, support, or receive through a human interaction that does not start with a legacy form.
Use QR, Lightning, BTCPay, or contact workflows where they fit, without forcing one context onto every transaction.
Limits, custody boundaries, support pathways, treasury treatment, and risk controls belong in a deployment review.
BUMP gives people a reason to engage before they understand the full stack. The deeper conversation moves into BAF, SovereignID, and deployment review when the context is serious.