---
title: "Retrieve a single funding"
method: GET
path: "/fundings/{id}"
tags: ["Endpoints"]
---

# Retrieve a single funding

`GET /fundings/{id}`

Returns a single Funding for the given unique ID

## Path parameters

- `id` string, required — Unique system identifier of the record in our system.

## Response `200`

OK

- Funding — A summary of a funding record which summarises a transfer between acquierer and merchant, for more details see the 'funding detail' object
  - `id` string, required — Unique system identifier of the record in our system.
  - `funded` string, date-time, required — The date and time (in ISO 8601 format `yyyy-MM-ddTHH:mm:ssZ`) the money is ready to be funded into the recipients account.
  - `posted` string, date-time, required — The date and time (in ISO 8601 format `yyyy-MM-ddTHH:mm:ssZ`) the funding order was generated.
  - `status` 'RELEASED' | 'HELD' | 'UNKNOWN', required — Whether the money has actually been released to the merchant account or is still being held
  - `type` object, required — The nature of the funding record / payment, such as whether it is a standard payment to the merchants account, or a collection from their account. Examples: * `250` - Merchant Payment (money being send from us to the merchant) * `270` - Merchant Collection (money being sent from the merchant to use, i.e. for charges / refunds)
    - `code` string, required — A numberic code which represents the type, can be used for programmatic checking
    - `description` string, required — A human readable text description for the type
  - `merchant` object, required — The merchant (business entity) being funded. This is usually identical to the merchant that processed the transactions, but may differ from the funding details records based on merchant group/subgroup hierarchy.
    - `id` string, required — External merchant id provided by client (if merchant ids have been pre allocated) or generated by our systems during merchant boarding.
    - `name` string, required — Trade name of the merchant, often printed on a card receipt.
    - `allianceCode` string, nullable, required — An alliance is typically an organization holding an acquiring licence issued by card schemes (like VISA, MasterCard etc). This code is assigned by us.
    - `partnerCode` string, nullable, required — Partners are typically companies (such as Payment Facilitators, Independent Software Vendors, Independent Sale Organisations) who can contract merchants for card acceptance but they don't hold an acquiring licence so must always be authorized by an Alliance.
  - `account` object, required
    - `id` string, required — Unique ID of the account in our system
    - `reference` string, nullable, required — Internal account reference used by our funding system
    - `iban` string, nullable, required — Masked international bank account number
    - `currencyCode` string, nullable, required — The account currency, may be different from the current funding from the acquirer
    - `type` object, required — The nature of the account being used, as it is common to have accounts for specific purposes.
      - `code` string, nullable, required — A numberic code which represents the type, can be used for programmatic checking
      - `description` string, required — A human readable text description for the type
  - `financial` object, required — Financial details on the funding
    - `netAmount` string, required — Final amount to be funded, in **account** currency, this may be negative in the case where it is a collection *from* the merchant
  - `meta` object, required — Reference metadata used by both the merchant and acquirer to link the funding to other records or systems.
    - `paymentReference` string, nullable, required — Internal reference for the funding record in our funding system, links all funding records to a singe payment together
  - `_links` object — HAL-style links to other related resources within our APIs
    - `transactions` object — A reference to the `/transactions` endpoint for any transactions records related to the current funding, using the following params: - `fundingId` as the `id` field from the current funding record - `postedAfter` the day before the current `posted` date - `postedBefore` the current `posted` date
      - `href` string
    - `funding-details` object — A reference to the `/funding/{id}/details` endpoint for the detail records related to this funding (by ID). For ecommerce this will not be present.
      - `href` string

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `429` — Too Many Requests
- `500` — Internal server error

---

[API](https://skmtc.net/fiserv/apis/acquirer-profile-in-design.md) · [All operations](https://skmtc.net/fiserv/apis/acquirer-profile-in-design/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fiserv/acquirer-profile-in-design/versions/dd7ef6ce81a1/schema)