v5
latestOpenAPI 3.1.02026-07-262421791.5 MBDispute dynamic flow entry point
Retrieves the JSON for initiating the dispute flow. Use this endpoint with Wise's Dynamic Flow framework.
The JSON response must be passed into the Dynamic Flow framework, which handles the multi-step dispute submission including the generation of subsequent pages and the creation of the dispute.
Setting up the API
You will need to implement a GET API with the following format: GET https://{{yourApiUrl}}/v3/spend/profiles/{{profileId}}/dispute-form/flows/step/{{scheme}}/{{reason}}?transactionId={{transactionId}}
This API should forward the call to: POST https://{{wiseUrl}}/v3/spend/profiles/{{profileId}}/dispute-form/flows/step/{{scheme}}/{{reason}}?transactionId={{transactionId}}
This is required as the dynamic flow returned by Wise will automatically be configured to call your GET API. Use baseUrl or fetcher as part of the dynamic flow setup to redirect the Dynamic Flow JavaScript library to your domain.
For a full integration guide, including example backend implementation and styling, see Disputes via Dynamic Flow.
Path parameters
Your profile ID.
The network of the card that was used to make this transaction.
Dispute reason code supplied by the dispute reasons endpoint.
Query parameters
The ID of the transaction being disputed. Can be a comma-separated list of IDs if the reason code has the supportsMultipleTransactions flag.
Headers
Optional UUID for correlating requests across systems. If provided, Wise echoes it back in the response. Maximum 36 characters. Learn more.
Request body
Example request
{
"email": "support@partner.com"
}Response
Returns information required to populate the form with the correct information. Note how the action field contains the URL and method to the next step.
Dynamic Flow JSON object. Pass this to the Dynamic Flow framework to render the dispute form.