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

# What is Waycore?

Waycore helps finance teams manage commercial bank accounts at scale: balances, transactions, statements, and payment workflows across banks that are difficult to integrate directly.

<Note>
  This page is intended for finance and operations teams evaluating Waycore. It covers the model, the access structure, and the key constraints. No prior knowledge of treasury software is assumed.
</Note>

<AccordionGroup>
  <Accordion title="1. What Waycore is" defaultOpen>
    Waycore is a software company that provides a **software-enabled outsourced treasury model.** We combine software automation with a controlled human service layer, using software where possible and human operations where needed.

    This is the same model that has existed in corporate banking for decades: a company appointing an external bookkeeper, treasury bureau, or accounting firm to operate its bank accounts under a limited mandate. Waycore delivers this as programmable infrastructure rather than strictly manual labour.
  </Accordion>

  <Accordion title="2. What Waycore is not">
    Waycore is not a bank, a money transmitter, or a money services business. We are not an Account Information Service Provider (AISP) or a Payment Initiation Service Provider (PISP). We are not a custodian of funds and are not a bank replacement.

    At no point in the transaction lifecycle does Waycore receive, hold, control, or redirect customer funds. **Funds never pass through any Waycore account or intermediary.** The bank remains the sole custodian of funds, the sole processor of payment instructions, and the sole enforcer of transaction controls.
  </Accordion>

  <Accordion title="3. Why this model exists">
    Commercial bank workflows are fragmented and difficult to manage at scale because the banking landscape has no single universal API surface. Aggregators, bank APIs, file rails, and manual portals each solve parts of the problem, but none provide one programmable, permissioned, observable interface over the full commercial-bank workspace.

    Waycore exists to provide that canonical interface by operating on top of the bank-authorized workspace itself, with delegated access, human-in-the-loop continuity, and bank-native controls.
  </Accordion>

  <Accordion title="4. How access works">
    Waycore is designed around the **permissioning model that banks already use**. The customer instructs their bank to create a dedicated delegated user. The customer defines the permissions. The bank enforces them. The customer can revoke access at any time.

    This means Waycore:

    * Does **not** log in as the primary user
    * Does **not** have unrestricted access to the account
    * Uses dedicated credentials issued to a delegated user (not shared passwords)

    <Check>
      Banks including Bank of America, Wells Fargo, Chase, and HSBC already support formal third-party and delegated access for business accounts in exactly this structure.
    </Check>
  </Accordion>

  <Accordion title="5. What this means in practice">
    Waycore operates strictly within the permissions granted by the customer and enforced by the bank. The service supports data access and payment-maker workflows under that model.

    Waycore operates through the customer’s authorized  access path, using bank-native delegated permissions and standard MFA. We do not bypass authentication, impersonate unknown users, or modify bank systems. Where the bank requires human interaction, a supervised operator completes the workflow. Automation is used downstream to normalize, structure, validate, and deliver the customer’s own banking data into their approved business software.

    When payment workflows are in scope, Waycore handles maker-side orchestration only. **Approval of payments remains entirely with the customer** or their designated approver inside the bank's own system. Waycore does not autonomously control funds.

    <Note>
      Human oversight is maintained for edge cases: non-standard authentication, portal changes, or anything outside normal operating conditions.
    </Note>
  </Accordion>
</AccordionGroup>

***

## Want to go deeper?

Waycore touches sensitive financial infrastructure, so we expect legal, security, and operational diligence. These pages are designed to make that review easier.

<CardGroup cols={2}>
  <Card title="Security & compliance" icon="shield-check" href="https://waycore.com/security">
    SOC 2 progress, fintech insurance, data protection, and Vanta trust access.
  </Card>

  <Card title="Legal model" icon="scale" href="https://waycore.com/tearsheet">
    A terms-aware model for delegated access and bank-enforced controls.
  </Card>
</CardGroup>

<Card title="Delegated access & controls" icon="key" href="https://docs.waycore.com/security/data-privacy">
  Learn how delegated users, permissions, approvals, audit trails, and human-in-the-loop escalation work in practice.
</Card>