Webhooks Overview

365 Finance provides real-time webhook notifications to keep partners informed about key events in the application lifecycle. When a significant event occurs, we send an HTTP POST request to your configured webhook URL with event details.

Available Events

EventDescription
open_banking_in_progressOpen Banking process has been initiated for an application
open_banking_completeOpen Banking data collection is complete
new_offerA new funding offer has been generated for an application
agreements_ready_to_signAgreements are ready and waiting for signatures
agreements_signedAll agreements have been signed
split_check365 Finance is requesting a split eligibility check
cash_advance_fundedThe cash advance has been funded to the customer
activate_splitSplit payments should begin for the merchant
update_splitThe holdback percentage for an active split has changed
cancel_splitThe advance is repaid — deactivate the split

Event Lifecycle

Standard application events follow this order:

Open Banking in Progress → Open Banking Complete → New Offer → Agreements Ready to Sign → Agreements Signed → Cash Advance Funded

For applications with split payments, additional events follow funding:

Split Check → Cash Advance Funded → Activate Split → (Update Split) → Cancel Split

Note: Not all applications will trigger every event. For example, an application may be declined before reaching the offer stage. Split events are only sent to partners with split payment integration enabled.

Payload Structure

Every webhook delivers a JSON object to your endpoint with the following fields:

{
  "event": "{event_name}",
  "event_id": "{event_id}",
  "application_id": "{application_uuid}",
  "timestamp": "{ISO_8601_timestamp}",
  "external_reference": "{your_reference_id}"
}

Message Fields (common to all events)

FieldTypeDescription
eventstringThe event type identifier
event_idstringUnique identifier for this specific event. Use for idempotency.
application_idstring (UUID)The unique application identifier
timestampstring (ISO 8601)When the event occurred
external_referencestringYour external reference ID for the application (the reference you provided when submitting the application)

Some events include an additional details object with event-specific data. See individual event pages for full payload examples.

Split Payment Events

The split_check event is sent before funding to determine whether a merchant is eligible for split payments. Your system should respond with:

ResponseMeaning
200Merchant is eligible — 365 Finance will proceed with split activation
500Merchant already has an active split with another provider — not eligible

The activate_split, update_split, and cancel_split events manage the split lifecycle after funding. Each includes a details object with merchant_uuid, holdback percentage, and mids (Merchant IDs). See individual event pages for full payload examples.

Authentication

Webhook requests are sent as HTTP POST requests to your configured endpoint. Details on webhook authentication and security will be provided during onboarding.

Retry Policy

If your endpoint does not return a 2xx response, we will retry the webhook delivery. Details on retry intervals and maximum attempts will be provided during onboarding.

Getting Started

To start receiving webhooks:

  1. Provide your webhook endpoint URL to your account manager
  2. Ensure your endpoint accepts HTTP POST requests with JSON payloads
  3. Return a 2xx status code to acknowledge receipt
  4. Process events asynchronously — respond quickly and handle business logic separately

Support

For technical support or questions about webhooks, contact us at [email protected]