> ## Documentation Index
> Fetch the complete documentation index at: https://docs.waycore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Commercial & Billing

This section explains how Waycore is priced and how that pricing maps to real-world usage. The goal is not just to describe mechanics, but to clarify the economic model behind the service; what drives cost, how it scales, and how to reason about it as a long-term production system.

## Pricing model

<AccordionGroup>
  <Accordion title="How do you define a 'delegated user'?">
    A delegated user is a single, persistent authenticated session to one bank portal on behalf of one entity.

    If your company has accounts at Chase and Bank of America, that is two delegated users. If you have accounts at two separate Chase entities (e.g., two different legal entities), that is also two delegated users.
  </Accordion>

  <Accordion title="Is a bank account the same as a delegated user? ">
    No. A delegated user refers to a portal login with access permissions, not to each individual bank account. If a single delegated user can access 50 accounts within one portal, that is billed as one delegated user.

    You are not charged separately for each of the 50 accounts.
  </Accordion>

  <Accordion title="Why is Waycore not priced per bank account?">
    Because the operational unit is the **authenticated bank user session**, not each account. One delegated user can cover dozens of accounts, but still requires a single maintained connection, permission model, and MFA handling.
  </Accordion>

  <Accordion title="What drives the price of a delegated user?">
    Bank complexity, authentication type, and ongoing operational load. A simple email-MFA bank is not equivalent to an app-token or multi-step approval environment.
  </Accordion>

  <Accordion title="Why is Waycore more expensive than a data aggregator?">
    Data aggregators provide best-effort, read-only access to retail and simple SMB accounts. They are limited to a fixed catalog of supported institutions, and do not specialize in commercial banking.

    They lack near real-time data, which is a structural requirement for any execution workflow, and they lack support for critical treasury features and transaction types.

    When connections break, developer support is often a ticket-based system that can take months to resolve.

    Waycore provides a single integration that works across **any bank**, **anywhere in the world**, so long as the institution supports delegated user access. New banks are onboarded on demand, typically within hours, without requiring a new integration.

    On top of that, Waycore delivers near real-time data, deterministic execution across complex commercial bank portals, native support for those treasury features, and a human-in-the-loop service layer that proactively maintains continuity when bank portals change.

    The relevant comparison is not against an aggregator's per-call pricing. It is against the fully-loaded cost of manual portal work, broken workflows, and the implementation drag that occurs when standard APIs fail to cover the commercial accounts your platform actually needs.

    See [What the alternative really costs](/pricing/cost-of-the-alternative).
  </Accordion>

  <Accordion title="What is a simple delegated user portal?">
    Standard portals use common authentication methods that are relatively straightforward to support and recover in operations, such as email OTP, SMS codes, phone-call verification, and app-based 2FA like Duo or Google Authenticator.
  </Accordion>

  <Accordion title="What is a complex delegated user portal?">
    Complex portals rely on authentication methods that create more operational overhead or tighter session constraints, such as RSA SecurID, mobile app soft tokens, device-bound approval flows, or other non-standard authentication and session controls.
  </Accordion>
</AccordionGroup>

## Volume discounts

<AccordionGroup>
  <Accordion title="Do prices decrease with volume?">
    Yes. Pricing is designed to decline at scale, reflecting shared infrastructure and operational efficiencies across large deployments.
  </Accordion>

  <Accordion title="How do volume discounts work?">
    Typically through tiered or marginal discounts as the number of active delegated users increases. Exact breakpoints depend on the partner and use case.
  </Accordion>

  <Accordion title="Why not flat pricing regardless of volume?">
    Because usage drives real operational cost. At the same time, larger partners create efficiencies, so pricing should reward scale without breaking unit economics.
  </Accordion>

  <Accordion title="Are there partner-specific pricing structures?">
    Yes. Platform partners (e.g., ERPs, accounting firms) may have custom commercial structures, including volume tiers or bundled pricing.
  </Accordion>
</AccordionGroup>

## Commercial terms

<AccordionGroup>
  <Accordion title="What is the platform fee vs usage fee?">
    The platform fee covers access, tooling, and base support. Usage fees scale with active delegated users, which is the core unit of work.
  </Accordion>

  <Accordion title="Does the sandbox replace production costs?">
    No. The sandbox is for testing. Production pricing reflects live-bank reliability and operations.
  </Accordion>

  <Accordion title="What happens if we stop using a delegated user?">
    Billing tracks active delegated users. If a user is deactivated, it is no longer billed.
  </Accordion>

  <Accordion title="Are there minimum commitments?">
    Typically yes for platform partners, to justify onboarding and support investment. Terms vary by agreement.
  </Accordion>
</AccordionGroup>

***

## Ready to get started?

<Columns cols={2}>
  <Card title="Talk to us" icon="message-circle" href="mailto:hello@waycore.com">
    Discuss your specific bank coverage requirements, get a custom quote, or learn more about the Pioneer Program.
  </Card>

  <Card title="Explore the API" icon="code" href="/api-reference/introduction">
    Read the full API reference, explore the sandbox, and start building your integration today.
  </Card>
</Columns>