Skip to content
Sections

Guides

Bank callbacks

Understand the verified Plaid and Salt Edge callback contracts.

Configure access

A finance administrator configures and validates the Plaid or Salt Edge connection in the organization Finance workspace. Provider/environment configuration and certification must be completed separately. These callbacks are generated by the provider; the example builder cannot produce a valid provider signature.

Cabinet route: /organizations/:organizationId/finance → Integrations. Managing a connection requires organization.finance.integrations.manage. Provider callbacks use the configured connection, environment and provider-issued verification material, not the administrator’s account session.

First successful workflow

Follow these steps in order. Open each method for its exact body, required headers and response schema.

  1. Register the correct Hallify callback URL with the configured bank provider.
  2. Plaid sends its verification JWT and exact raw JSON body; Hallify checks ES256, key rotation, body SHA-256, environment and issue time.
  3. Salt Edge v6 signs the exact callback URL and raw body with RSA SHA-256; Hallify also verifies callback version, timestamp and connection identity.
  4. A valid callback records a receipt and queues incremental synchronization. Inspect the connection’s synchronization state in Finance.

State, retries and recovery

Do not reuse Hallify HMAC examples for these providers. A callback receipt is not proof that all transactions have been reconciled. Exact replays are recognized; changed or unverifiable content must not be acknowledged as successful processing.

Hallify uses essential cookies and optional analytics.

Essential cookies keep sign-in, locale, and theme preferences working. Analytics is off until you choose to allow it.