> ## Documentation Index > Fetch the complete documentation index at: https://docs.qint.ch/llms.txt > Use this file to discover all available pages before exploring further. # List currencies > Public, unauthenticated. Every fiat currency Qint knows, with whether it is offered for **new** payments right now. Qint can switch a currency off (and back on) at any time; while it is off, creating an intent, link or invoice in it is refused with `400`. That `400` has no machine-readable `code` — only a `detail` such as `GBP is currently disabled on Qint. currency must be one of: CHF, EUR, USD.` — so call this endpoint before creating an intent rather than parsing the error. Records already created in that currency keep working. The response is cacheable for 30 seconds — cache it on your side rather than calling it on every checkout. ## OpenAPI ````yaml openapi.yaml GET /api/v1/public/currencies openapi: 3.1.0 info: title: Qint Merchant API version: '1.1' description: > The Qint merchant API is a server-to-server API for creating and reading **payment intents**. You create an intent, redirect the buyer to the returned `checkoutUrl` (Qint's hosted checkout at `checkout.qint.ch`), and get notified of status changes via [webhooks](https://docs.qint.ch/webhooks/overview). ### Authentication Every request is authenticated with a Qint-issued API key (`qk_live_` + 32 alphanumeric characters), sent either as `Authorization: Bearer qk_live_…` or as an `X-Api-Key: qk_live_…` header. Keys carry **Read** and/or **Write** scopes: creating intents requires Write, reading them requires Read. The merchant account must be approved before the API accepts requests. ### Errors Errors are returned as RFC 7807 `application/problem+json` documents with `title`, `status` and `detail` fields. ### Rate limits The merchant API is rate limited. When a limit is exceeded the API responds with `429 Too Many Requests` — back off and retry. Intent creation is retry-safe: the required `idempotencyKey` makes a retried request return the original intent instead of creating a duplicate. ### Settlement Every payment is credited to the merchant's balance in its **Account Currency** (CHF, EUR, USD or GBP; CHF by default) at the rate fixed when the buyer is quoted. Since 20 October 2026 a payment intent reports the credit as `creditAmount`, `creditCurrency` and `creditRate`; the former stablecoin fields `creditUsdt` and `creditAsset` are no longer returned, and `creditRate` changed meaning. See [the breaking change note](https://docs.qint.ch/api-reference/introduction#breaking-change-20-october-2026). ### Dashboard endpoints The endpoints tagged **Dashboard** serve the Qint dashboard. They authenticate with the dashboard's signed-in session, not with an API key, and are documented so that the balance, balance conversion and Account Currency rules are described in one place. contact: name: Qint support email: support@qint.ch url: https://qint.ch servers: - url: https://api.qint.ch description: Production security: - bearerAuth: [] - apiKeyHeader: [] tags: - name: Payment intents description: Create standalone payments and read their status. - name: Currencies description: Which fiat currencies Qint currently offers for new payments. - name: Dashboard description: > The merchant balance, conversions of a previous-currency balance and the Account Currency, as used by the Qint dashboard. Signed-in dashboard session only; API keys are not accepted. paths: /api/v1/public/currencies: get: tags: - Currencies summary: List currencies description: > Public, unauthenticated. Every fiat currency Qint knows, with whether it is offered for **new** payments right now. Qint can switch a currency off (and back on) at any time; while it is off, creating an intent, link or invoice in it is refused with `400`. That `400` has no machine-readable `code` — only a `detail` such as `GBP is currently disabled on Qint. currency must be one of: CHF, EUR, USD.` — so call this endpoint before creating an intent rather than parsing the error. Records already created in that currency keep working. The response is cacheable for 30 seconds — cache it on your side rather than calling it on every checkout. operationId: listCurrencies responses: '200': description: The currency list, in display order. content: application/json: schema: $ref: '#/components/schemas/CurrencyList' example: currencies: - code: CHF enabled: true - code: EUR enabled: true - code: USD enabled: true - code: GBP enabled: false security: [] components: schemas: CurrencyList: type: object required: - currencies properties: currencies: type: array items: type: object required: - code - enabled properties: code: type: string description: ISO 4217 currency code. examples: - CHF enabled: type: boolean description: Whether the currency is offered for new payments right now. securitySchemes: bearerAuth: type: http scheme: bearer description: > `Authorization: Bearer qk_live_…` — a Qint API key created in the dashboard under Developers → API keys. apiKeyHeader: type: apiKey in: header name: X-Api-Key description: > Alternative to the Authorization header — send the same `qk_live_…` key as `X-Api-Key`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.