List Intent external providers

GET

/v3.0/:ClientId/payins/intents/external-providers

Retrieve the list of third-party PSP names supported by Echo for:

The ExternalData.ExternalProviderName property of the Intent object
The ExternalProviderName property of Mangopay’s settlement file format

Note – Check values to use for your integration

This endpoint returns the descriptive name for each provider. The rendering of the value you need to use as the ExternalProviderName in your integration is listed in the supported providers page.

Retrieve the list of third-party PSP names supported by Echo for: - The `ExternalData.ExternalProviderName` property of the [Intent object](/api-reference/intents/create-intent) - The `ExternalProviderName` property of Mangopay's [settlement file format](/api-reference/settlements/settlement-file) <Note icon="fa-regular fa-circle-info"> **Note – Check values to use for your integration** This endpoint returns the descriptive name for each provider. The rendering of the value you need to use as the `ExternalProviderName` in your integration is listed in the [supported providers](/api-reference/echo/supported-providers) page. </Note>

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.

Bearer authentication of the form `Bearer <token>`, where token is your auth token. If your platform is using a [proxy](/guides/sca/proxy-management) to take SCA-triggering action on behalf of users, you also need to integrate [mTLS authentication](/guides/sca/platform) and use the `api-mtls` base URL.

Path parameters

ClientIdstringRequired

Platform's API account identifier, associated with the API key.

Response

Success