# Configuration

**Configuration Endpoints** - Retrieve supported payment methods, fiat currencies, countries, crypto currencies, and other configuration data required to build onboarding and transaction flows.

**Key Operations**:
- List supported fiat currencies for on-ramp and off-ramp transactions
- Retrieve available payment methods for a given transaction direction
- Get supported countries and any required states or provinces
- List supported crypto currencies for transaction setup
- Use configuration data to pre-fill forms before pricing or ramp creation

**Use Cases**:
- Populate dropdowns and selectors in your UI
- Filter valid options based on customer choices
- Validate transaction parameters before submission
- Display supported onboarding and payout options

## Payment Methods

 - [GET /eapi/v0/payment-methods/{transactionType}](https://docs.banxa.com/products/native-api/openapi/configuration/listpaymentmethods.md): Retrieve supported payment methods for the specified transaction type as part of the configuration data required to build onboarding and transaction flows.

Use Cases:
- Populate payment method selectors for on-ramp and off-ramp journeys
- Determine which fiat currencies are available for each payment method
- Pre-configure transaction forms before requesting quotes or creating ramps
- Show only valid payment options for the customer's selected transaction direction

Transaction Types:
- onramp - Payment methods available for buying cryptocurrency with fiat
- offramp - Payment methods available for selling cryptocurrency to fiat

Response Structure:
Each payment method includes:
- method: Unique code used in API requests
- name: Human-readable payment method name
- supportedFiats: Fiat currencies supported by that payment method

## Cryptocurrencies

 - [GET /eapi/v0/cryptocurrencies/{transactionType}](https://docs.banxa.com/products/native-api/openapi/configuration/listcryptocurrencies.md): Retrieve supported cryptocurrencies for the specified transaction type as part of the configuration data required to build onboarding and transaction flows.

Use Cases:
- Display available cryptocurrency options to customers
- Show supported blockchains for each cryptocurrency
- Pre-configure asset and network selectors before pricing or ramp creation
- Filter cryptocurrencies by transaction direction

Transaction Types:
- onramp - Cryptocurrencies available for buying (fiat → crypto)
- offramp - Cryptocurrencies available for selling (crypto → fiat)

Response Structure: Each cryptocurrency includes:
- crypto: Unique coin code (e.g., BTC, ETH, USDT)
- name: Human-readable display name
- blockchains: Array of supported blockchain networks, each with contract address, minimum amount, default flag, and restricted countries

## Supported Fiats

 - [GET /eapi/v0/fiats/{transactionType}](https://docs.banxa.com/products/native-api/openapi/configuration/listfiats.md): Retrieve a list of supported fiat currencies for the specified transaction type (onramp or offramp).

Use Cases:
- Display available fiat currencies to customers during onboarding
- Filter payment methods by fiat currency
- Show fiat options in transaction creation UI
- Validate customer-selected fiat before transaction

Transaction Types:
- onramp - Returns fiat currencies supported for buying cryptocurrency
- offramp - Returns fiat currencies supported for selling cryptocurrency

Response Structure: Each fiat currency includes:
- fiat - Three-letter ISO 4217 currency code (e.g., "AUD", "USD")
- name - Human-readable currency name (e.g., "Australian Dollar")
- symbol - Currency symbol (e.g., "$", "€")
- supportedPaymentMethods - Array of payment methods available for this fiat

## Supported Countries

 - [GET /eapi/v0/countries](https://docs.banxa.com/products/native-api/openapi/configuration/listcountries.md): Retrieve supported countries for KYC and transaction flows as part of the configuration data required to build onboarding and transaction flows.

Use Cases:
- Populate country dropdowns during customer onboarding
- Determine which countries are enabled for your merchant configuration
- Retrieve state or province options for countries that require region selection
- Filter valid options based on customer location

Response Structure: Each country includes:
- id: Two-letter ISO country code
- description: Human-readable country name
- states: List of supported states or provinces for that country, if applicable