WePay

WePay is infrastructure for software platforms and independent software vendors that want payments inside their own product. It is best suited to teams building merchant onboarding, checkout and payouts into a platform, rather than companies looking for a standalone merchant account. The trade-off is a developer-oriented, partner-based model with pricing negotiated on request.

Overview

WePay covers the operational path from merchant signup through payment acceptance and withdrawal to a bank account. Its Clear, Link and Core integration models give platforms different ways to structure that flow. The Merchant Center adds administration for onboarding, transactions, reporting, chargebacks and managing user access.

WePay operates as JPMorgan Chase’s integrated-payments business. Merchants generally open accounts through a platform partner, because direct integration for merchants is not supported. That dependency suits software companies controlling the customer relationship, but rules out businesses that need to enrol merchants independently.

Key features

Integrated checkout and APIs

APIs let a platform onboard merchants and process payments for them. Link can present payment fields in an iframe or through a custom interface, and it supplies hosted onboarding and KYC/CIP screens. A custom checkout can retain a platform’s branding while tokenizing card details. JavaScript libraries tokenize cards, bank accounts and digital-wallet payments, reducing the sensitive payment data an application handles.

Developer coverage is broad: SDKs are documented for PHP, Ruby, Python, NodeJS, Java, iOS and Android. WePay says API access follows application registration, with a stage environment recommended before production. Its guidance says API integration can reduce an application’s security and compliance scope, although the application remains responsible for protecting sensitive data.

Merchant operations and payouts

The Merchant Center gives operations teams a single place for reporting, disputes and account access. Flexible payouts and same-day deposits help platforms choose how merchants receive funds; depositing to a Chase bank account carries no additional platform cost. Card acceptance includes most domestic and international Visa, Mastercard, American Express, Discover, JCB and Diners Club cards.

Support is listed Monday through Friday, 9:00 AM to 9:00 PM EST. Merchant availability in the United States and Canada depends on the partner platform, so regional rollout needs confirmation at that level. Link is described as being in closed beta, an important constraint for teams planning a broadly available launch.

Pricing

WePay uses paid, quote-based pricing. The Link Standard plan has no published subscription price and is currently in closed beta. Its stated processing rates are 2.9% + 25¢ for card-not-present transactions and 2.6% + 10¢ for card-present transactions, with a $0 chargeback fee.

Those rates make Link Standard most relevant to platforms that can qualify for the beta and want predictable per-transaction terms without a listed chargeback fee. Custom pricing means larger or more specialised platforms must obtain a quote before comparing total cost. No free plan, trial period, seat allowance or renewal term is provided, so budget planning requires a sales conversation.

Platforms

WePay supports Android, iOS, web and API deployments. Its SDK list also covers server-side languages and mobile development, making it practical for platforms combining backend payment orchestration with native apps. Link’s closed-beta status may limit immediate access despite that technical breadth.

Who it's for

Choose WePay for a software platform or ISV that needs advanced KYC/AML tooling, multi-method payment acceptance, flexible payouts, full account management and broad API/SDK coverage. It is particularly suitable when branded checkout, hosted compliance screens and a central merchant-operations console matter.

Look elsewhere if your model requires direct merchant integration, a public price list, or a generally available Link deployment. Teams serving merchants outside the supported partner-led U.S. and Canadian arrangements should verify eligibility before committing.

Pros and cons

• Pros: End-to-end onboarding, processing and withdrawals; iframe or custom checkout options; tokenization for cards, bank accounts and wallets; same-day and flexible payout choices; no extra platform cost for deposits to Chase accounts; broad SDK coverage; advanced KYC/AML and merchant administration.
• Cons: Merchants cannot integrate directly; Link is in closed beta; pricing is obtained on request; geographic support varies by partner; applications still retain responsibility for sensitive-data protection; support hours are limited to weekdays and EST business hours.

Alternatives

Consider Stripe Connect when you want a mature connected-account model with a free platform plan in which Stripe sets and collects processing fees from users. Checkout.com is worth comparing if free processing for registered charities in its operating countries or tailored commercial terms are relevant.

NMI, DreamPay, PayPal Multiparty Payments, Unipaas, Flute Embedded Payments and Stax Connect are other paid platform-payment options; their commercial models differ, with several requiring approval or a sales quote.

For broader discovery, browse Embedded Payments Platforms and Marketplace Payment Platforms.

Verdict

WePay is a strong choice for software businesses that want integrated merchant onboarding, payment processing, compliant tokenized checkout and flexible payouts under one platform relationship. Its main reasons to look elsewhere are the lack of direct merchant integration, closed-beta Link access and quote-based pricing.