Webhooks Overview

Available Events

Event	Description
`open_banking_in_progress`	Open Banking process has been initiated for an application
`open_banking_complete`	Open Banking data collection is complete
`new_offer`	A new funding offer has been generated for an application
`agreements_ready_to_sign`	Agreements are ready and waiting for signatures
`agreements_signed`	All agreements have been signed
`cash_advance_funded`	The cash advance has been funded to the customer

Event Lifecycle

Events follow the typical application journey in this order:

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

Note: Not all applications will trigger every event. For example, an application may be declined before reaching the offer stage.

Payload Structure

Every webhook has envelope containing the event-specific data:

{
  "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)

Field	Type	Description
`event`	string	The event type identifier
`event_id`	string	Unique identifier for this specific event
`application_id`	string (UUID)	The unique application identifier
`timestamp`	string (ISO 8601)	When the event occurred
`external_reference`	string	Your external reference ID for the application (the reference you provided when submitting the application)

Some events include an additional details object inside message with event-specific data. 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:

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

Support

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