WePay review

WePay is a cloud-hosted payment-processing service from JPMorgan Chase, designed to embed payments in software applications, SaaS products and online marketplaces. It sits between a platform’s application and payment processing: the platform integrates WePay, while WePay supports merchant onboarding, transaction processing and risk operations.

Its three models map to different platform responsibilities. Link refers merchants to Chase-branded payment services, with WePay handling onboarding, compliance, underwriting and end-user support. Clear keeps onboarding, checkout and reporting under the platform’s brand, while the platform controls merchant fee markup. Core is for registered payment facilitators and connects to Chase wholesale banking rails for custom settlement, reporting and revenue sharing.

The service accepts cards, ACH and digital wallets; mobile point-of-sale SDKs and certified card readers support in-person payments. It is aimed at platform businesses managing payments and sub-merchant onboarding, rather than merchants looking for a standalone checkout account.

The integration surface includes REST APIs, event webhooks and hosted web components for browser-based platforms. WePay also offers native mobile SDKs for iOS and Android, plus mobile point-of-sale SDKs and pre-certified card readers for card-present payments. Client-side tokenization and hosted fields are intended to reduce the platform’s PCI-DSS requirements; they do not remove the need to assess compliance responsibilities.

The Partner Center provides merchant-account review, API logs and financial reporting. WePay describes an API-first integration model rather than an off-the-shelf app marketplace, and does not publish an official count or directory of pre-built integrations. The homepage does not name programming languages. Confirm language-level SDK support and CLI availability in the vendor’s developer docs before choosing an implementation path; the documented integration surfaces are APIs, webhooks and hosted components.

For architecture planning, confirm webhook event behavior, onboarding flow, and how the selected product handles merchant support and settlement.

WePay has no free plan, and its hosted service is not an open-source option. Link is transaction-priced: the listed rate is 2.9% + $0.30 per card transaction and 1% + $0.30 per ACH transaction. The plan includes merchant onboarding and compliance, underwriting, and end-user support. A $15 chargeback fee is listed.

Clear and Core use custom pricing. Clear is for platforms that need branded onboarding, checkout and reporting, with the platform controlling its merchant fee markup. Core targets registered payment facilitators and includes custom settlement, deep reporting and bespoke revenue sharing. Ask WePay for a quote tied to your expected transaction mix, merchant count, settlement needs and support model; seat and usage limits for Clear are not published.

The pricing is transaction-based or quote-based, not a monthly or annual subscription. As processed volume grows, fees scale with transactions, while the published card and ACH rates give Link buyers a basis for estimates. Other add-ons and overages are not published, so confirm chargeback handling and any additional fees before launch.

WePay is a closed-source, cloud-hosted service managed by JPMorgan Chase. There is no open-source or self-hosted version, so teams cannot run the payment-processing infrastructure in their own environment. Public developer access is through client SDKs, documentation and integration libraries.

The vendor does not publish a data-export policy on the vendor's site available to buyers. Ask what merchant, transaction and reporting data can be exported, in what formats, and for how long it remains accessible after termination. Also establish how to move recurring payment credentials: tokenized payment data can create migration work if it cannot be transferred to a replacement processor.

Migration means replacing the API and webhook integration, rebuilding payment and onboarding flows, and arranging a new processor relationship. The effort will depend on which WePay product you use and how deeply the platform relies on its hosted components, reporting and risk workflows.

WePay offers KYC onboarding, risk engines, fraud monitoring and dispute mitigation. The vendor also says Same-Day Deposits are available to Chase business bank accounts without additional expedited transfer fees. Before depending on those flows, verify eligibility, settlement timing, reserves, review triggers and the escalation path for held transactions with WePay. Published rate limits and service-level commitments should be confirmed with the vendor during procurement.

Reddit users report payments held for review, delayed refunds and account deactivations, including complaints about large transactions and requests for business documentation. These are individual accounts, not measured incident rates, but they point to a material production concern: risk decisions can affect merchant cash flow and platform support load. Set expectations with merchants about verification and payout reviews, and define a process for urgent escalations.

Tokenization and hosted fields can reduce PCI-DSS scope, but platforms still need to validate their own compliance obligations. Test onboarding, webhook handling, dispute workflows and payout reconciliation before rolling WePay out across a merchant base.