How to Design a User Wallet Feature in Bubble

Create a 'Wallet' Data Type with: user (User — one wallet per user), balance (number — current balance in cents to avoid floating point issues), currency (text — e.g. 'USD'). Create a 'WalletTransaction' Data Type with: wallet (Wallet), type (text — credit/debit), amount (number — in cents), description (text), counterparty (User — who the transfer is with), reference_id (text — external payment ref), balance_after (number — balance snapshot after transaction), Created Date. Create the wallet record automatically when a user signs up.

Create a wallet page showing: a large balance display formatted as currency (divide cents by 100), a row of action buttons (Top Up, Send, Receive), and a Repeating Group of WalletTransactions sorted by Created Date descending. Each transaction row shows: icon (green arrow up for credit, red arrow down for debit), description, amount (formatted as +$XX.XX or -$XX.XX), balance after transaction, and date. Add filters above the list: date range picker and type filter (all/credits/debits). Add a summary section showing total credits and debits this month.

When the Top Up button is clicked, show a popup with pre-set amount buttons ($10, $25, $50, $100) and a custom amount input. On confirmation, initiate a Stripe Checkout session for the selected amount. On successful payment (via Stripe webhook), create a WalletTransaction with type = 'credit', the amount, description = 'Top up via card', reference_id = Stripe charge ID, and update the Wallet balance by adding the amount. Set balance_after to the new balance.

When the Send button is clicked, show a popup with: a user search input (to find the recipient), an amount input, and an optional note. Validate that the sender has sufficient balance. In the workflow: create a debit WalletTransaction for the sender (amount subtracted from balance), create a credit WalletTransaction for the recipient (amount added to balance), update both Wallets. Use a backend workflow for this to ensure atomicity — if any step fails, the whole transfer should not partially complete.

Add transaction verification by requiring a PIN or password confirmation before transfers above a threshold amount. Log all wallet operations in a separate AuditLog Data Type for compliance. Add a daily balance reconciliation backend workflow that compares each Wallet's balance against the sum of all its transactions to detect discrepancies. Display a transaction receipt after each operation with a unique reference number. Add low-balance alerts that notify users when their balance drops below a configured threshold.