Skip to main content
A Transfer represents a fund movement the platform executes on your behalf, as opposed to a Transaction, which is an observed bank record after the fact. Once the public Transfer API is released, it will support:
  • Initiating payment instructions across supported rails
  • Batch-oriented submissions for grouped treasury workflows
  • Idempotent creation semantics for safe retries
  • Webhook-driven state changes and reconciliation against downstream transactions

​
Supported rails

RailUse case
internalTransferMove funds between accounts at the same institution.
achUS domestic ACH credit or debit.
wireUS domestic wire.
swiftInternational wire via SWIFT.
fednowUS instant payment via FedNow.
rtpUS instant payment via RTP.
More exotic rails can be enabled on request.

​
Transfer lifecycle

The broader platform models transfers as explicit stateful objects that move through validation, execution, bank acknowledgement, and terminal outcomes. Once the public Transfer API is released, webhooks and audit records will be the main integration primitives around that lifecycle.
Waycore can initiate but not approve external transfers. External transfers have to be approved at the bank’s portal, not Waycore.
Transfer endpoints are actively under development and will be exposed publicly in the near future.