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.
Waycore is a universal API adapter for commercial banking. A business provisions a dedicated delegated user inside its existing bank portal, often through an onboarding interface hosted by its software provider; Waycore turns that bank-authorized workspace into one developer interface for balances, transactions, statements, payment preparation, approval support, audit trails, and recovery workflows across any commercial bank.
Through that API, Waycore delivers treasury operations with the speed and flexibility of software, without removing the permissions, approvals, and audit trails banks and finance teams rely on.
The Problem
Commercial banking access is not solved by connection lists or bank APIs. Aggregators often break down where commercial banking is most complex: incomplete coverage, stale data, limited write support, uneven scopes, and developer experiences built around what the connection can expose rather than what the workflow requires. Bank API projects have the opposite problem: every bank exposes a different interface, approval process, permission model, file format, and operational surface area. Even when those bank APIs are wrapped by another provider, coverage is often limited, onboarding can take weeks, and access may still depend on relationship-manager approval or bank-side implementation work.
A positioning chart comparing commercial banking access options by universal access and visibility/control. Existing approaches such as open banking aggregators, support matrices, ERP transaction feeds, manual portals, RPA scripts, custom integrations, and bank APIs are shown as partial or bank-by-bank solutions. Waycore is positioned in the high-access, high-control quadrant as remote control for any commercial bank account, exposing universal read/write access through one developer API while preserving bank-native permissions, approvals, and audit trails.Waycore is best understood as a remote control for any commercial bank account. It is not limited to banks with open banking APIs, aggregator support, file rails, or bespoke bank integrations. Compared with alternatives, Waycore combines universal access with reliable visibility and control through a single developer API.
Waycore takes a different path. It adapts the bank-authorized workspace the business can already provision, then exposes the underlying treasury workflow through one developer API.
| Category | Universal access | Reliable visibility and control | Limitation |
|---|---|---|---|
| Open banking and aggregators | Medium | Medium-low | Often read-only, institution-catalog dependent, and unreliable for commercial banking workflows. |
| ERP or accounting transaction feeds | Medium-low | Medium-low | Usually limited to transaction visibility and cannot reproduce full commercial banking workflows. |
| Reports, exports, spreadsheets, and manual portals | Low | Low | Bank-by-bank manual work with poor programmability and weak operational leverage. |
| RPA or internal scripts | Low-medium | Low | Fragile, bank-by-bank automation maintained internally. |
| Bank APIs and file rails | Low-medium | Medium-high | Reliable where available, but gated, partial, bank-specific, and not universal. |
| H2H, EBICS, SFTP, and custom integrations | Medium-low | Medium-high | Strong for selected banks and workflows, but expensive and bank-by-bank. |
| Selective connectivity vendors | Medium | Medium | Useful for selected banks or regions, but not universal commercial-bank coverage. |
| Waycore | High | High | Universal read/write access exposed through one developer API, governed by bank-native permissions, approvals, and audit trails. |
For banks Waycore already supports, we aim to go-live in under 8 hours after the delegated user is created. For newly requested banks, Waycore aims to add support in under 48 hours from the point the required bank-side sub-user or authorized portal profile is available.
Waycore supports any bank that supports sub-users.
Waycore supports any bank that supports sub-users.
- A treasury platform
- An ERP
- An AP automation tool
- A lending or capital product
You can’t reliably see, let alone move money across commercial banks.
The Waycore Model
Waycore makes a company’s delegated bank workspace programmable through dedicated delegated-user access. Instead of scraping with shared credentials, your customer:- Creates a delegated user inside their bank
- Assigns permissions (read, transfer, approval)
- Connects that user to Waycore
- Onboards delegated-user bank connections
- Reads balances and account data
- Normalizes accounts and transactions
- Creates and tracks transfers where transfer access is enabled
- Emits real-time webhooks
- Maintains a complete audit trail
What Waycore Is Not
- Not a consumer bank aggregator
- Not a neobank
- Not a regulated Payment Service Provider (PSP) or Third Party Provider (TPP) under PSD2
- Not a UI-first treasury tool
- Not dependent on bank APIs
Who It’s For
ERP & accounting products
When bank connectivity gaps create manual work, broken workflows, or bank-by-bank integration overhead.
Treasury & finance platforms
When customers need balances, transactions, statements, or payment actions at commercial banks that are hard to support.
Accounting firms & fund administrators
When teams are already logging into bank portals on behalf of clients and need to reduce manual effort, errors, and servicing cost.
Internal finance operations
When critical bank workflows still depend on portal hopping, downloads, and error-prone manual intervention.
Design Principles
- Deterministic > probabilistic
- Execution > aggregation
- Delegated access > credential sharing
- Policy before action
- Observable by default