Skip to main content
Waycore turns a commercial bank portal into a programmable surface area using entity-aware ownership, delegated user access, and observable state transitions. We act as an end-user’s authorised representative, operating under a delegated user, at the portal level, to automate treasury workflows under human supervision.

​
System Overview

​
The Core Loop

Your platform starts by selecting or creating the business that owns the bank connection.This entity becomes the ownership boundary for:
  • Connections
  • Accounts
  • Transactions
  • Your own internal customer mapping
Your platform either looks up the target institution in the public catalog or provides a raw bank portal URL, then creates or returns a connection.If onboarding is still required, the setup-stage connection returns:
  • Structured setup details
  • The next required action
  • Which party needs to take it
Your customer creates a dedicated user inside their bank portal for Waycore. Permissions are scoped explicitly by the bank.Then the integrator:
  • Submits the temporary credentials
  • Marks bank-side setup complete
  • Polls the connection until it is activated
Once activation is complete, the connection becomes active.From there, your platform can:
  • Read accounts
  • Backfill transactions
  • Trigger a sync when freshness matters
The public API exposes webhook notifications for operational changes such as:
  • Connection status changes
  • Fresh transaction sync availability
All of this sits on top of the same audit and operational control model that powers the broader Waycore platform.

​
What Happens When MFA Appears?

When a bank requires MFA or a reauthentication step during onboarding or ongoing sync, Waycore escalates to human-in-the-loop operations where needed.

​
Guarantees

  • Ownership is explicit through entities and connections.
  • Every major state change is observable.
  • Delegated access preserves bank-native permissions.

​
Non-Guarantees

  • Banks may change portal flows.
  • MFA requirements vary by institution.
  • Activation and sync latency depend on bank behavior.
  • Bank portal uptime is not guaranteed.