| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Get Equipment Funders
Returns a list of approved equipment funders available within the authenticated ISO's configuration. Each funder entry contains an ID and a display name. These IDs are used in the fundersIds field when adding POS or non-POS equipment to a merchant application. This endpoint has no query parameters — the funder list is automatically scoped to the ISO associated with the calling credentials.
Endpoint
GET /api/v1/equipment/funders
Authentication
Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:
Authorization: Basic {base64(username:password)}
When to use
Call this endpoint before submitting equipment add requests (POST /api/v1/equipment/equipmentpos or POST /api/v1/equipment/regular) to populate a funder selection UI or to validate funder IDs. The returned list is specific to the ISO account, so different callers may see different funders based on their configuration. Funders represent the financial entity (bank, leasing company, or ISO office) that backs the equipment acquisition.
Response
200 OK
| Field | Type | Description |
|---|---|---|
| data | array | List of funder objects available for equipment financing |
| data[].id | integer | Unique funder ID to use in fundersIds when adding equipment |
| data[].name | string | Human-readable name of the funder |
| status | string | HTTP status string (e.g., OK) |
| error | string | Error message on failure; null on success |
| warning | string | Non-fatal warning message, if any |
| validationResults | array | Validation result objects, if any |
| requestId | integer | Unique request ID for tracking |
{
"data": [
{
"id": 1,
"name": "Unified Payments"
},
{
"id": 2,
"name": "Phoenix Fusion"
},
{
"id": 3,
"name": "RPS"
},
{
"id": 4,
"name": "Super PC Systems"
},
{
"id": 5,
"name": "ISO Office"
}
],
"status": "OK",
"error": null,
"warning": null,
"validationResults": [],
"requestId": 50192
}Error Codes
| Code | When it happens |
|---|---|
| 401 | Invalid or missing Basic Auth credentials |
| 403 | User does not have permission for this operation |
| 404 | No funders configured for this ISO account |
| 500 | Internal server error while retrieving funders |
Common Mistakes
- Hard-coding funder IDs across environments — IDs may differ between staging and production; always fetch this list at runtime before submitting equipment requests
- Expecting the same funder list across different ISO accounts — the list is scoped to the authenticated ISO's configuration
- Using a funder ID from this list for a non-equipment context — funder IDs here are specific to equipment financing and may not be valid in other parts of the API
Related Endpoints
GET /api/v1/equipment/pos— retrieve the POS equipment catalogGET /api/v1/equipment/regular— retrieve the non-POS equipment catalogPOST /api/v1/equipment/equipmentpos— add POS equipment using funder IDs from this endpointPOST /api/v1/equipment/regular— add non-POS equipment using funder IDs from this endpoint
Example
curl -X GET "https://hq.staging.netevia.dev/api/v1/equipment/funders" \
-H "Authorization: Basic $(echo -n 'username:password' | base64)" \
-H "Content-Type: application/json"