Cryptopay API
  • Welcome
  • Guides
    • Introduction
    • Environments
    • Creating a Test Account
    • API Credentials
    • API Basics
      • Responses
      • Date formats
      • Authentication
        • How it works
        • Signature
        • Creating a signature. Code samples
      • Callbacks
    • API Client Libraries
    • API Reference
    • Cryptocurrency Payments
    • Currencies
      • Supported Currencies
      • Currency Icons
    • Confirmations
    • Tools for accepting payments
    • Prebuilt integrations
      • E-commerce payment plugins
      • Payment and software providers
    • Channels
      • Channel payment
      • Payment statuses
      • Channel payment sequence
      • Create a Channel
      • Visual representation at Cashier
      • Channel hosted page
      • Channel payment callbacks
    • Invoices
      • Invoice statuses
      • Invoice payment sequence
      • How to handle unresolved invoices
        • Underpaid
        • Overpaid
        • Paid late
        • Illicit resource
        • Invoice refunds sequence
      • Create an invoice
      • Visual presentation at Cashier
      • Invoice hosted page
      • Online checkout
        • How-to
      • Payment links
      • Invoice callbacks
    • Payouts
      • Payout statuses
      • Payout sequence
      • Payout fees consideration
        • Network fees
      • Create a Coin Withdrawal
        • Possible errors
        • Withdrawals from fiat accounts
        • Withdrawals from cryptocurrency accounts
        • high_risk_address error message
      • Visual representation at Cashier
      • Minimum transaction amount
      • Coin Withdrawal callbacks
      • Travel Rule Compliance
    • Email Billing
      • Create an email billing
      • Email billing callbacks
    • Testing
      • Channels
      • Invoices
      • Payouts
    • Risks
    • Customers
    • Transactions types and Statuses
Powered by GitBook
On this page
  1. Guides

Currencies

PreviousCryptocurrency PaymentsNextSupported Currencies

Last updated 8 months ago

To keep the list of coins in your systems up to date use the endpoint.

The endpoint provides the following information:

  • Array of available coins and all supported networks

  • Currency - currency ticker

  • Name - name of currency, network or destination tag

  • Precision - number of decimal places supported by coin

  • Destination tag - the presence of an additional destination_tag field for the coin. If destination_tag is not null, then there is an additional field for the coin and it must be shown to the user when the user is paying, as well as give an opportunity to the user to specify it, on par with the wallet address, when withdrawing funds. Additional parameter required specifies the obligation to send destination_tag when requesting a coin withdrawal:

    • required: true - you cannot create a withdrawal without specifying destination_tag. If the user doesn't specify it, add dt=0 to the request.

    • required: false - you can create a withdrawal without destination_tag. If the user didn't specify it - don't add dt to the request.

Destination tag is similar to a reference number for bank transfers. It helps to identify transactions when a single address is used by multiple users.

  • Logo url - link to logo of the coin

  • Invoices, channels, coin withdrawals - availability for use in invoices, channels and coin withdrawals. Switches to false during maintenance on our side.

GET /api/coins