Have something to say?

Tell us how we could make the product more useful to you.

Negative Wallet Balances Workflow

Subject: Update on Non-SaaS Workflow and Negative Wallet Balances Hey team, [Solution already Planned] Since I run Auth.net V2 payment version. I cannot send out touch points for failed payments. I wanted to share a quick update regarding our efforts to address the non-SaaS accounts. We've implemented a new workflow to identify these accounts and are actively reaching out “manually” to encourage them to update their payment information. Our ultimate goal is to reduce the number of non-SaaS accounts to zero, as they should all be transitioned to SaaS. [Key Point] Additionally, we've encountered a challenge with several users having negative wallet balances. I'm looking into creating a touchpoint for these accounts to ensure they are addressed promptly. It would be great to explore potential solutions or feature requests that could help us manage this situation more effectively. Thanks for your attention to this matter! https://loom.com/share/64ab6272b1d04b408400d6da20ab9627 Best regards, Troy Hitt

troyhitt 2 months ago

Enhancements

Authorize.net SaaS and Non-SaaS Users activation trigger & export

It was recently brought to my attention that there’s no way to export both SaaS and non-SaaS users from the platform. Having access to this data would make a huge difference in how we manage adoption and activation campaigns. Here’s why this is important: Our users’ sub-accounts are created automatically via API from our core software platform. However, activation requires an additional manual step where the user must enter their credit card information to fund their wallet. Currently, about 40% of our users stop midway—they create a sub-account but never complete the setup by activating their wallet. If we could export a list of these non-SaaS users, we could easily identify and target them through follow-up campaigns to drive full activations. Additionally, I’d love to see this export functionality extended beyond Stripe to include Authorize.net and NMI accounts. Since many of us operate in industries where Stripe isn’t a viable option, having parity for Authorize.net (priority) and NMI would be extremely valuable.

troyhitt 3 months ago

Feature Request

Authorize.net & NMI Payment Failed and Payment Success Workflows

We’re currently on version 2 of the payment platform, which allows sub-accounts to use alternative payment providers like NMI and Authorize.net. Our SaaS subscription is processed through Authorize.net, and we’d love to see a trigger event added for when those subscriptions fail. At present, this functionality only exists for Stripe, but because we operate in a restricted industry, Stripe isn’t an option for us or for any of our sub-accounts. Adding support for Authorize.net and NMI failure triggers would make it possible for agencies like ours to automate customer notifications, retry logic, and account management workflows—exactly as Stripe users can today. This enhancement would bring parity across all supported payment gateways and unlock far more flexibility for those of us in regulated verticals.

troyhitt 3 months ago

Feature Request