> ## 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.

# How pricing works

Waycore pricing is simple: a base **platform fee**, a **per-connection fee** for each maintained delegated user, and **usage-based** pricing for execution workflows.

<CardGroup cols={3}>
  <Card title="Platform Access" icon="server">
    API access, sandbox environment, monitoring, support, and integration tooling.
  </Card>

  <Card title="Delegated Users" icon="user-check">
    A per-connection fee for each maintained bank portal session, priced as standard or complex.
  </Card>

  <Card title="Execution Events" icon="bolt">
    Usage-based pricing for write-side workflows such as transfers, uploads, and scheduled actions.
  </Card>
</CardGroup>

The main variable is the **delegated user**. Each delegated user represents one maintained bank portal connection for one entity at one institution. That portal may expose one account or many accounts; the pricing unit is the maintained portal access, not the number of accounts behind it.

These connections are priced as either **standard** or **complex**, depending on the operational effort required to keep the portal reliable.

<Tip>
  Larger partners can access enhanced support, committed-volume pricing, and custom commercial terms. Get in touch with us via [hello@waycore.com](mailto:hello@waycore.com).
</Tip>

***

## What is a Standard vs. Complex Portal?

Delegated users are priced in two bands: **standard portals** and **complex portals**. The band depends on the operational effort required to keep the connection reliable, including authentication, MFA, session recovery, permission structure, and bank-specific behavior.

<CardGroup cols={2}>
  <Card title="Standard portal" icon="spline">
    Common authentication and recovery patterns, such as email OTP, SMS codes, phone-call verification, or app-based two-factor authentication.
  </Card>

  <Card title="Complex portal" icon="route">
    Higher operational load caused by tighter session constraints, device-bound approvals, hardware tokens, mobile soft tokens, or non-standard auth.
  </Card>
</CardGroup>

<Note>
  Portal complexity is based on the operational effort required to maintain reliable delegated access. If a portal’s classification is unclear, Waycore assesses it during onboarding as part of implementation.
</Note>

***

## Want to learn more?

Whether you are exploring coverage for a specific bank, evaluating a partner rollout, or trying to estimate production pricing, we can help map the right setup.

<CardGroup cols={2}>
  <Card title="Book a call" icon="calendar" href="https://calendly.com/eliasimos">
    Schedule a short conversation to discuss your use case, coverage requirements, and implementation path.
  </Card>

  <Card title="Get in touch" icon="mail" href="mailto:hello@waycore.com">
    Email us for pricing questions, custom quotes, partner terms, or anything else we can help clarify.
  </Card>
</CardGroup>