Fixing the Wallet Top-Up Flow: Modal Now Reopens After Card Setup
Fixing the Wallet Top-Up Flow
If you've tried to add funds to your dealwork.ai wallet for the first time, you may have hit a subtle friction point: after adding your credit card through the Stripe checkout, you landed back on the wallet page — but the "Add Funds" modal had closed. You had to click the button again to finish the top-up.
That extra step is now gone.
What Changed
When you click Add Card inside the Add Funds modal, the platform redirects you to a Stripe-hosted setup page. Once you complete the card setup, Stripe sends you back to /dashboard/wallet?card_added=1. Previously, the page reloaded your data (so the new card appeared) but left the modal closed.
The fix: on return from card setup, the Add Funds modal now reopens automatically with your new card pre-selected. Enter an amount and confirm — one click instead of three.
Why It Matters
This was contributing to drop-off at the most critical step in the buyer funnel. Adding a card and then having no clear "what next" is a classic conversion killer. The intent was always to fund the wallet; the modal should stay out of the way.
What We Investigated
As part of this fix we audited the full Stripe checkout path:
- Card setup (Stripe Checkout in
setupmode) correctly attaches the payment method to the Stripe customer. - Top-up (Stripe PaymentIntents with
off_session: true) correctly charges the saved card and credits the wallet via the webhook handler. - Webhook correctly verifies the Stripe signature and processes both
payment_intent.succeededandcheckout.session.completedevents idempotently.
The code was correct end-to-end. The only issue was the UX gap between the two steps.
Coming Up
We're tracking a few follow-on improvements:
- Surfacing a clearer post-top-up confirmation screen for first-time funders
- Adding per-contract configurable escrow holdback windows for high-value contracts
If you run into any issues with the wallet or top-up flow, use the feedback board at dealwork.ai/feedback or open a support thread.
Comments (0)
0/5000
No comments yet. Be the first to comment!