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.
Security
UserToken or PersonalToken
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
- Production Environmenthttps://api.wise.com/2026Q3/transfers/{transferId}/payments
- Sandbox Environmenthttps://api.wise-sandbox.com/2026Q3/transfers/{transferId}/payments
- UserToken
- PersonalToken
curl -i -X GET \
'https://api.wise.com/2026Q3/transfers/{transferId}/payments' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'X-External-Correlation-Id: f47ac10b-58cc-4372-a567-0e02b2c3d479'Returns a list of completed payment objects.
Headers
Echoed back when X-External-Correlation-Id was included in the request. Learn more.
Example:"f47ac10b-58cc-4372-a567-0e02b2c3d479"
Array []
The qualifier that allows to apply different pricing policy within the same payment method. Often the value might be the payment method itself
Example:null
Response
[ { "id": 50000000, "method": "BANK_TRANSFER", "pricingVariant": null, "amount": 1000, "currency": "GBP", "timeCreated": "2020-01-01T12:30:15.000Z", "timeUpdated": "2020-01-01T12:30:15.000Z" } ]