WePay

Overview

WePay found a stronger business by moving payments into other companies’ software. It started with shared expenses, tried tools for small merchants, and then focused on the platforms those merchants already used. GoFundMe, FreshBooks, and Constant Contact became named platform customers; WePay supplied the infrastructure beneath them.

Rich Aberman and Bill Clerico founded WePay in 2008 and joined Y Combinator’s Summer 2009 batch. JPMorgan Chase announced its acquisition in October 2017 and completed it that December. This is an acquisition story, not a documented company shutdown. Chase’s current QuickAccept agreement still names WePay Inc. as a service provider alongside Paymentech and JPMorgan Chase Bank. That continuing legal role does not establish that every historical WePay product remains available to new platforms. ^{[1] [2] [3] [4]}

Image 1 / 1

Founding Story

Aberman, then pursuing law, and Clerico, working in investment banking, were college friends. Their starting problem was collecting money from groups, a task with infrequent usage. ^{[5] [6]}

The company experimented beyond that first job. GoingAsAGroup, launched in 2010, let buyers coordinate group purchases; Mountain Creek ski passes provided an early example. In 2013, mobile invoicing targeted photographers, contractors, and other service businesses. Each experiment moved closer to a merchant’s working routine, although providing every vertical’s software was a substantial product burden. ^{[7] [8]}

WePay also used a memorable distribution stunt. At PayPal’s 2010 developer conference, it placed a large block of ice containing money outside the venue, playing on complaints about frozen accounts. The founder interview documents the event; it does not establish customer acquisition or revenue from it. Attention could introduce the company, but a useful payment workflow had to sustain the relationship. ^[5]

GoFundMe co-founder Brad Damphousse needed payment infrastructure beneath its donation app. WePay could supply it. Aberman’s retrospective says platform partnerships passed half of revenue in 2014; WePay then dropped its direct business. ^[6]

Clerico discusses building and selling WePay in this September 2025 Founders in Arms interview.

Timeline

• 2008–2009: Aberman and Clerico start WePay; the company joins YC’s Summer 2009 batch. ^{[1] [5]}
• 2010: GoingAsAGroup extends the shared-payment idea into coordinated purchases. ^[7]
• 2012: A $10 million growth round backs further merchant expansion. ^[9]
• 2013: Mobile invoicing gives service businesses a way to request online payment from customers. ^[8]
• 2014: WePay demonstrates Veda, its platform risk engine. FreshBooks launches embedded payments, including invoice and dispute bookkeeping. ^{[10] [11]}
• 2015: WePay raises a $40 million Series D led by FTV Capital, with Rakuten participating. Reporting also describes a Google Wallet Instant Buy integration. ^[12]
• 2016: UK support extends the platform service beyond the United States and Canada. ^[21]
• 2017: Chase announces the acquisition on October 17; the deal closes in December. ^{[2] [3]}
• 2024 onward: JPMorgan describes WePay’s integration into its payments offering. Current Chase legal terms retain WePay’s role in QuickAccept. ^{[3] [4]}

What They Built

The mature product combined payment integration, merchant onboarding, and risk operations. A platform could make payments part of its own application while WePay handled infrastructure that required more than a checkout button. Chase’s acquisition announcement emphasized APIs, onboarding, fraud protection, and software partners serving small businesses. ^[2]

FreshBooks shows the practical result. Its 2014 launch used WePay beneath FreshBooks branding. Payment updated the invoice automatically, while refunds and chargebacks also entered the bookkeeping workflow. The value was keeping a merchant’s financial work together. FreshBooks reported that 52 percent of invoices in its beta were paid the same day and more than 70 percent within 48 hours. Those figures concern that beta’s invoice payments, not universal settlement speed or a controlled causal experiment. ^[11]

Veda addressed the platform’s other problem: accepting legitimate merchants without taking uncontrolled fraud risk. Its 2014 presentation described combining transaction relationships and platform-provided information with other signals. The demonstration establishes the proposed mechanism and product identity; it supplies no independent fraud-loss benchmark. ^[10]

Published developer documentation now distinguishes three products:

• WePay Link: Chase-branded payment services with WePay-managed support. The public page labels its APIs a closed beta.
• WePay Clear: A platform-branded experience, including onboarding, verification, and dispute tools; the platform handles end-user support.
• WePay Core: Registration services for a registered payment facilitator, which retains underwriting, compliance, and merchant-experience responsibilities.

Link and Clear documentation directs platform developers toward test credentials and a sales contract. This is different from an individual merchant joining through a platform. JPMorgan’s integration article says it reviewed all software-partner relationships and ended some agreements. The docs therefore establish product descriptions, not unrestricted enrollment or a retirement date for every product. ^{[3] [13] [14] [15]}

Market Position

WePay’s channel gave it access to merchants through software relationships already in place. Its challenge was to make those relationships operationally reliable: verification, payment acceptance, exceptions, and support had to fit the platform’s experience. Chase’s stated acquisition rationale paired that technology with its bank distribution. The announcement’s four million small-business customers described Chase’s 2017 network, not merchants already using WePay. ^[2]

The surviving market is crowded. Stripe Connect supports platform onboarding and payments. Adyen for Platforms combines verification, payments, splits, payouts, and reconciliation. PayPal Complete Payments Platform also offers seller onboarding, payouts, and dispute management.^[22] Chase QuickAccept offers eligible Business Complete Banking customers merchant tools such as payment links and invoicing; that bank-account offering is not interchangeable with developer enrollment in Link, Clear, or Core. ^{[16] [17] [18]}

A rebuild therefore cannot assume an empty embedded-payments market. A narrower opportunity could lie in coordinating cases and consented evidence across providers. That hypothesis requires integration access and paying customers. A portable business profile cannot carry another provider’s underwriting approval with it.

Business Model

WePay monetized payment processing through its platform relationships. Current Clear documentation describes a platform retaining the difference between its merchant price and processing charges. Core assigns a different operating burden to a payment facilitator. These models make responsibility and economics inseparable: branding control does not eliminate risk, support, or compliance work. ^{[14] [15]}

Traction

The 2014 Finovate profile reported 300 platform partners, 250,000 customers, and $500 million in annual transaction volume. Contemporary 2015 reporting described roughly 1,000 API partners, more than 500,000 merchants, and over $1 billion processed. These are company-reported operating figures with different periods and definitions. Transaction volume is not revenue, and cumulative processing is not an annual run rate. ^{[10] [12]}

The $10 million 2012 round and $40 million 2015 round show investor support for expansion. They do not establish profitability or today’s demand for a new payment-operations vendor. Chase’s official acquisition announcement does not disclose consideration, so a headline deal price should not substitute for documented terms. ^{[9] [12] [2]}

Post-Mortem

Infrequent shared expenses limited recurring use. Building specialist merchant apps required competing with focused software companies. Serving those companies instead aligned their customer workflows with WePay’s infrastructure. Aberman’s revenue account supports the channel shift, although distribution alone does not explain the acquisition. ^[6]

Concentrating on platforms also meant giving up direct customers. The trade-off made WePay a clearer partner, while increasing dependence on platforms’ priorities and integration quality. FreshBooks’ embedded bookkeeping illustrates why the partnership could be valuable beyond payment acceptance. ^[11]

Chase’s acquisition addressed capabilities the bank wanted to combine with its customer network. Aberman later described the effort to preserve a small technology team’s culture inside a large bank. That is a founder’s account of integration tensions, not an independent measure of post-acquisition financial performance. The observable sequel is continued Chase integration and WePay’s named legal role. ^{[2] [5] [4]}

Key Lessons

• Match the business to repeated work. Shared expenses and merchant invoicing have different usage patterns, even when both move money.
• Let specialist software own the customer job. FreshBooks could build accounting while WePay supplied payment infrastructure.
• Channel focus has a cost. Choosing platform partners meant abandoning the direct line and accepting partner dependence.
• Keep provider responsibilities explicit. A managed onboarding product and a payment-facilitator service assign different risk and compliance duties.
• Build around the surviving market. Today’s payment platforms already offer much of WePay’s original scope. A new operations layer needs its own evidence of demand.

Sources

[1] Y Combinator: WePay company profile

[2] Chase announces agreement to acquire WePay, October 2017

[3] JPMorgan: WePay integration, May 2024

[4] Chase QuickAccept legal agreement

[5] AppDirect: Rich Aberman founder interview

[6] Startups.com: WePay’s journey to product-market fit

[7] Forbes: GoingAsAGroup launch, November 2010

[8] Wired: Mobile invoicing, February 2013

[9] YC: WePay’s $10 million growth round, May 2012

[10] FinovateSpring 2014: Veda product demonstration

[11] FreshBooks: Embedded payments launch, October 2014

[12] Vator: $40 million Series D, May 2015

[13] WePay Link developer documentation

[14] WePay Clear developer documentation

[15] WePay Core developer documentation

[16] Stripe Connect

[17] Adyen for Platforms documentation

[18] Chase QuickAccept product page

[19] Finovate: Funding coverage and stage-photo caption

[20] Founders in Arms: Bill Clerico interview, September 2025

[21] Finovate: UK launch, July 2016

[22] PayPal Complete Payments Platform overview, updated August 2026