Skip to main content
Funding activity represents operational funding received and tracked through the Partner API lifecycle. Funding activity is associated with:
  • requests
  • balances
  • settlement eligibility
A single funding event may:
  • fund multiple requests
  • be partially allocated
  • remain partially available

Funding Lifecycle States

RECEIVED

Funding was detected successfully. Operational validation may still be pending.

DIRTY

Funding originated from a non-approved source. Dirty funding is operationally segregated and cannot participate in settlement or allocation.

ELIGIBLE

Funding passed operational validation. An internal transfer moves it into the available pool; once that completes the funding becomes AVAILABLE.

TRANSFER_FAILED

The internal transfer of eligible funding failed. Failed transfers are retried operationally, returning the funding to ELIGIBLE.

AVAILABLE

Funding is in the available pool and may be allocated to requests.

PARTIALLY_ALLOCATED

Part of the funding is assigned to requests; the remainder is still available. Allocations may be released, returning the funding toward AVAILABLE.

ALLOCATED

The funding is fully assigned to operational requests. Allocated funding remains linked to the associated requests until settlement completion; releases can return it to PARTIALLY_ALLOCATED or AVAILABLE.

CONSUMED

Funding was fully utilized through completed settlement flows. Consumed funding is no longer available operationally.

Funding Validation

Funding validation verifies:
  • supported asset
  • supported network
  • operational compatibility
  • approved funding source
Funding failing operational validation transitions to:

Approved Funding Sources

Only approved funding sources are eligible for allocation. Funding received from non-approved sources:
  • remains visible operationally
  • is excluded from settlement flows
  • cannot participate in request matching

Partial Funding Support

Requests support partial funding. As a result:
  • multiple funding events may contribute to one request
  • one funding event may contribute to multiple requests

Allocation Rules

Allocation occurs only after funding becomes:
Funding allocation depends on:
  • request lifecycle
  • available balances
  • operational settlement requirements

Balance Visibility

Funding contributes to:
  • available balances
  • allocated balances
  • dirty balances
depending on lifecycle state.

Operational Visibility

Partners may retrieve:
  • funding lifecycle states
  • linked requests
  • balance visibility
  • operational allocation status
through the Partner API.

Precision Rules


Error Scenarios

Funding may fail operational validation for reasons including:
  • unsupported asset
  • unsupported network
  • invalid funding source
  • operational restrictions
  • incompatible request lifecycle