Skip to content
Homeward Documentation

Payout integrations

Payout integrations is where the organization connects its own Wise account, so that payouts Homeward has approved can be sent out from the organization’s own business profile. It is per-organization on purpose: the page says it directly — “ owns these connections… Each organization’s tokens and Wise profiles are isolated from every other organization.” Owners and organization admins can add or rotate credentials.

Currently one provider is available: Wise, for outbound bank payouts. The card shows a runtime badge — Production runtime or Sandbox runtime — for the environment this deployment is actually using, and a status badge of Ready or Needs configuration.

Credentials

Section titled “Credentials”

There are two credential sections side by side, Production (“Used when this deployment sends real payouts”) and Sandbox testing (“Kept separate so connection and payout flows can be tested safely”). Each shows a Connected or Not connected badge, and either may carry a Deployment fallback badge when its credentials come from deployment configuration instead of this page. The section that is not the runtime environment is captioned Not used by this deployment.

  • Profile ID — the Wise business profile that owns the payout balance. It must be a positive whole number; anything else is rejected with “Enter a positive whole-number Wise business profile ID.”
  • API token — a Wise personal API token, pasted into a password field. It must be at least 20 characters. Once stored it is accepted once and never shown again: the field then reads “Stored securely — enter only to replace”, and you can change the profile ID on its own by leaving the token blank.

Save production credentials or Save sandbox credentials saves them, and the feedback tells you to “Verify the connection before relying on it for payouts.” Press Verify to check that the profile ID and token work together; the result reads Verified or Couldn’t be verified.

Disconnect

Section titled “Disconnect”

Disconnect appears once a token is stored. Its dialog is explicit: “Flo will erase the stored token and profile selection for this organization. Historical payout records remain auditable, but unfinished payouts using this connection may need manual resolution.” Confirm with Disconnect, or press Keep connection to back out.

Webhook destination

Section titled “Webhook destination”

The Webhook destination block shows the webhook URL and a badge: Signature verification ready, or Platform setup needed when Homeward still has to configure its side. Copy URL puts it on your clipboard.

Before Wise is ready

Section titled “Before Wise is ready”

While the status reads Needs configuration, the page lists exactly what is missing under Before Wise is ready — the production or sandbox connection, the credential vault, the recipient bank-detail vault, or webhook signature verification. If the credential vault is unavailable, the message is for Homeward rather than you: an operator has to configure the server-side encryption key before any token can be saved.

Section titled “Related”