# List completed payments

Fetch completed payments used to fund the transfer.

In most cases there should only be a single payment associated with the transfer. There are rare occasions that a transfer can be funded with multiple payment methods and when this occurs the first completed payment method would be used to calculate the fees provided on the quote.

Endpoint: GET /v1/transfers/{transferId}/payments
Security: UserToken, PersonalToken

## Path parameters:

  - `transferId` (integer, required)
    The transfer ID

## Header parameters:

  - `X-External-Correlation-Id` (string)
    Optional UUID for correlating requests across systems. If provided, Wise echoes it back in the response. Maximum 36 characters. Learn more.
    Example: "f47ac10b-58cc-4372-a567-0e02b2c3d479"

## Response 200 fields (application/json):

  - `id` (integer)
    Payment ID
    Example: 50000000

  - `method` (string)
    The payment method used to pay for the transfer
    Example: "BANK_TRANSFER"

  - `pricingVariant` (string,null)
    The qualifier that allows to apply different pricing policy within the same payment method. Often the value might be the payment method itself

  - `amount` (number)
    Transfer source amount
    Example: 1000

  - `currency` (string)
    Transfer source currency
    Example: "GBP"

  - `timeCreated` (string)
    Date of when payment was created
    Example: "2020-01-01T12:30:15.000Z"

  - `timeUpdated` (string)
    Date of when payment was updated
    Example: "2020-01-01T12:30:15.000Z"


## Response 404 fields