List compliance vocabularies
Returns the global compliance vocabularies (purpose of remittance, source of funds, ID types) used to populate the off-ramp compliance fields. These are the baseline lists; which fields a specific payment actually needs is connector-specific — submitting an off-ramp payment validates them and returns a 422 listing anything missing or invalid.
Authorizations
Access token issued by POST /v1/auth/token.
Application secret (the apiKey issued at registration), required on every request.
Response
Compliance vocabularies.
Compliance vocabularies (for example purposeOfRemittance, sourceOfFunds, idTypes). Treat the exact shape as connector-defined and read values dynamically.