Jaris helps payment and software companies become financial partners so they can better serve small and medium-sized businesses (aka merchants). Partners can onboard new merchants, manage funding flows, and launch embedded lending, banking, and instant payouts. Jaris is B2B2B with partner-facing experiences in the Jaris Dashboard and merchant-facing experiences in the Merchant Dashboard (hosted, but also available as an embedded experience).
⭐ Managed SettlementsHighlighted Work (1 of 2)
When a merchant accepts a loan product from Jaris, they are issued a settlement account. Payment processors will send funds to this settlement account and Jaris will automatically collect the loan repayment amount before sending the remaining funds to the merchant’s business bank account.
Managed Settlements allow partners to add funding instructions to collect fees and reserves from a merchant’s settlement deposit alongside the loan repayment. To support this new feature, merchants would be issued a new type of settlement account and be given visibility into all of the money movement for each settlement deposit.
This project required a systems-thinking approach to ensure the interconnected experiences across partners and merchants were cohesive and not fragmented. I'm not showing everything that was done as part of this project, but am only showing a piece of it.
0.5 to 1: The partner's experience in Jaris Dashboard
The first version was co-designed by a contract designer and engineers, and had limited functionality.
Before:The lack of intentional organization and language made the experience hard to understand, use, and scale. It wasn't designed with the partner in mind as the main user, and felt more like an internal tool using BE language. I couldn't just add new functionality to the existing experience without cluttering it and making it more confusing.
After:Improved both Jaris Dashboard and Managed Settlements IA to create intuitive and scalable experiences. Updated the language and crafted additional copy to make the experience more user-friendly and ensured there was parity with the new merchant experience.
0 to 1: the merchant's experience in Merchant Dashboard
With the new Managed Settlements feature, merchants require a new type of settlement account with multiple balances to support the different fees a partner could collect or withhold. Since accounts typically have a single balance, the challenge here was to simplify the complexity of this acccount structure to [1] provides transparency into all money movement, [2] craft language to help the user make sense of all of this, and [3] provide bank statements (not shown).
In addition to this, I needed to create a hosted white-labeled experience that was mobile-responsive to give to partners an out-of-the-box solution for their merchants.
Before:In the embedded experience, there was a basic Settlement Account experience; settlement deposits flow through, amounts are deducted for loan repayment, and the remaining funds are swept to the merchant's business bank account. This basic experience would not be able to support the new type of settlement account.
After:Designed a scalable MVP with a consumer-grade experience to make it feel like a familiar banking experience. Came up with user-friendly labels for each balance type (avoiding the use of BE enums which was a common practice). Provided helper text to make sense of the different balances and overall experience. Provided transparency into the money movement for each settlement deposit.
⭐ Instant Payouts RedesignHighlighted Work (2 of 2)
Instant Payouts (IP) gives merchants same-day access to a portion of their pending card sales for a small fee.
Updated IP experience
Before:Before I joined the team, the MVP experience for IP already existed but there was no adoption. After I launched a new hosted Merchant Dashboard experience, IP was in the middle of re-launching and the existing experience was added to the dashboard as is.
After:I redesigned the experience to improve the layout, navigation, and organization of information for a more intuitive experience (I was able to reuse components and layout patterns I previously established for the settlement account work shared above too). I also rewrote and added new copy to provide additional context to users. Lastly, I ensured the overall experience was responsive to support mobile users.