Skip to main content
Waycore turns a commercial bank portal into a programmable surface area using delegated user access, policy-gated execution, and observable state transitions.

System Overview


The Core Loop

Your customer creates a dedicated user inside their bank portal for Waycore. Permissions are scoped explicitly:
  • Read-only access (balances, transactions)
  • Transfer initiation
  • Approval rights (if required)
No shared credentials. No screen scraping under a primary login.
Waycore verifies that:
  • The delegated user is active
  • The required permissions exist
  • The portal flow is operational
Connection health is continuously monitored. If a bank flow changes, a degraded state is emitted.
Your platform calls the Waycore API. Example: POST /transfersBefore execution:
  • Policy rules are evaluated
  • Limits are enforced
  • Approval requirements are checked
If the request violates policy, execution does not begin.
Waycore:
  • Navigates the bank portal
  • Handles MFA prompts
  • Submits transfer details
  • Confirms bank acknowledgement
If MFA is required, the transfer moves into an MFA_REQUIRED state until resolved.
Every transfer moves through defined states:
  • CREATED
  • POLICY_VALIDATED
  • QUEUED
  • EXECUTING
  • MFA_REQUIRED (if applicable)
  • COMPLETED
  • FAILED
Each state transition emits a webhook event. All actions are written to an immutable audit log.

What Happens When MFA Appears?

When a bank requires MFA, Waycore moves the execution into an MFA_REQUIRED state. Depending on your configuration, Waycore can: 1) request an end-user prompt, or 2) escalate to human-in-the-loop operations to complete the step under audit controls.

Guarantees

  • Policy is evaluated before execution.
  • Every state change is observable.
  • Delegated access preserves bank-native permissions.
  • No money movement occurs without explicit API initiation.

Non-Guarantees

  • Banks may change portal flows.
  • MFA requirements vary by institution.
  • Execution latency depends on bank behavior.