If you’re processing payments through Dodo Payments, you already have a steady stream of moments where customers are satisfied enough to leave a review. The problem is nothing’s capturing that. The payment goes through, the customer moves on, and nobody sends a review request because it fell through the cracks like it always does.
Trophy Jar fixes that by connecting directly to Dodo Payments and automating the ask.
Dodo Payments is a payment and billing platform built for software businesses and digital product creators. It handles payments, subscriptions, tax compliance, checkout, and recurring billing all in one place. A lot of SaaS founders and indie developers use it specifically because it takes the merchant-of-record complexity off their plate.
SaaS startups, indie developers, AI tools, digital product creators or anyone selling software or subscriptions who wants billing handled without building it themselves. If that’s you, every completed payment is a moment Trophy Jar can turn into a review request.
Dodo Payments tells you when a payment completes, a subscription renews, or a plan upgrades. What it doesn’t do is follow up with that customer and ask what they think. That part still falls on someone to remember and action, which means it usually doesn’t happen.
The fix isn’t hiring someone to manage it. It’s connecting Trophy Jar so the request goes out automatically the moment the payment event fires.
Image: A simple before/after timeline. Before: payment completes day one, review request sent (if at all) two weeks later, marked red, “too late, moment gone.” After: payment completes, review request fires same day, marked green, “right timing, higher response rate.”
Go to your Dodo Payments dashboard, navigate to Developer → API, and generate an API key. If you want Trophy Jar to manage webhooks automatically, enable write access. Read-only is fine just to get started.
Paste the key into Trophy Jar. It verifies it against Dodo Payments before saving, so you’ll know straight away if something’s wrong.
Sort out test versus live mode before you do anything else. Use a test key while you’re configuring, then switch to a live key when you’re ready for real customers. It’s an easy thing to mix up and worth being deliberate about.
Once connected, choose which Dodo Payments events should kick off a review request. A completed payment is the obvious starting point. But renewals, plan upgrades, and other billing milestones are all worth considering depending on your business.
Be specific. A vague trigger sends the email at the wrong moment and gets ignored. A request that fires right after a successful payment, like when the customer is already in a good headspace about your product, actually gets responses.
Once it’s set up, nothing changes in how you use Dodo Payments. Payments come in, Trophy Jar picks up the events, emails go out. No manual sends, no reminders, no checking anything.
Head to Trophy Jar’s integration settings and remove the API key. That cuts the connection immediately, no more events, no more automated emails.
Your existing review data stays put. Trophy Jar just stops receiving anything new from Dodo Payments going forward.
Run one test transaction first. Use your test mode key, push a payment through, and confirm the review request email actually arrives correctly. Takes five minutes and saves a lot of cleanup if something’s misconfigured.
Also double-check you’re connecting the right Dodo Payments account. If you manage multiple, there’s no warning if you grab the wrong one.
After that, it runs itself, which is exactly the point.