List connector compliance requirements
Returns the required and optional sender/beneficiary compliance fields
for a specific connector. Different connectors on the same corridor can
require different fields. The corridor is derived from the connector, so
only connectorId is needed.
Authorizations
Access token issued by POST /v1/auth/token.
Application secret (the apiKey issued at registration), validated at the Kong edge.
Query Parameters
Connector to resolve requirements for.
Transaction type the quote was created with (e.g. B2C). Defaults to C2C upstream.
Response
Connector compliance requirements.
Required and optional sender/beneficiary compliance fields for a connector, passed through from the payment engine. Treat the exact shape as connector-defined.