Skip to main content

Cryptofuse API Documentation

Welcome to the Cryptofuse API documentation. This guide is designed for developers who want to integrate cryptocurrency payment processing into their applications using the Cryptofuse platform.

Postman Collection

For easy API testing, check out our Postman Collection with pre-configured requests and examples using USDTERC20 and EVM addresses.

API Version

Current API version: 1.0. This documentation reflects the latest stable release.

What is Cryptofuse?​

Cryptofuse is a multi-tenant cryptocurrency payment processing platform that enables businesses to accept and manage cryptocurrency payments. The platform provides a secure, scalable infrastructure for handling cryptocurrency transactions across multiple blockchain networks with a focus on ERC20 tokens and EVM-compatible chains.

Key Features​

  • Multi-Chain Support: Process payments on Ethereum and other EVM-compatible networks (Polygon, BSC, Arbitrum)
  • ERC20 Token Focus: Optimized for stablecoins like USDT, USDC, and DAI
  • Multi-Tenant Architecture: Isolated environments for each merchant with dedicated schemas
  • Real-time Webhooks: Instant notifications for payment status updates
  • Automatic Balance Management: Track balances across multiple currencies and wallets
  • Fee Management: Flexible fee structures with merchant or user payment options

Supported Blockchains & Tokens​

Cryptofuse specializes in EVM-compatible chains and ERC20 tokens:

Primary Tokens​

  • USDTERC20: Tether USD on Ethereum
  • USDCERC20: USD Coin on Ethereum
  • DAIERC20: DAI Stablecoin on Ethereum

Supported Networks​

  • Ethereum (ETH)
  • Polygon (MATIC)
  • Binance Smart Chain (BSC)
  • Arbitrum (ARB)
  • Base
  • Optimism

How to Use This Documentation​

This documentation is organized into several sections:

Getting Started — Create an Account​

To start using Cryptofuse, you need to create a merchant account:

  1. Sign up at cryptofuse.io or fill out the registration form
  2. After registration, you will receive your custom API base URL and OAuth2 credentials (client_id and client_secret)
  3. Each merchant gets a dedicated, isolated environment with its own unique base URL
Custom Base URL

Every merchant receives their own unique API base URL upon registration. There is no shared public endpoint — all examples in this documentation use {{BASE_URL}} as a placeholder. Replace it with the URL provided to you during onboarding.

Sandbox Environment

Sandbox/testing environments are available on request. Contact [email protected] to get access to a sandbox instance for development and testing.

API Structure​

The Cryptofuse API follows RESTful design principles and uses JSON for request and response payloads. All endpoint paths are relative to your custom base URL (e.g. {{BASE_URL}}/payments/).

Authentication​

All API calls require authentication using OAuth 2.0 bearer tokens. Access tokens are obtained through the client credentials flow:

POST /o/token/
Authorization: Basic base64(client_id:client_secret)
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials

Request Format​

All requests must include:

  • Content-Type: application/json header for POST/PUT/PATCH requests
  • Authorization: Bearer {access_token} header
  • JSON body for data payloads

Response Format​

Successful responses return JSON data:

{
  "transaction_id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "waiting",
  "blockchain_address": "0x742d35Cc6634C0532925a3b844Bc9e7595f8b8E0",
  "pay_amount": "100.000000",
  "pay_currency": "USDTERC20"
}

Error Responses​

Errors follow a consistent structure:

{
  "error": {
    "code": "invalid_request",
    "message": "The amount field is required",
    "details": {
      "field": "amount",
      "reason": "missing"
    }
  }
}

Rate Limits​

API rate limits vary by endpoint:

  • General endpoints: 1000 requests/hour
  • Payment creation: 100 requests/hour
  • Webhook notifications: No limit

Rate limit headers are included in all responses:

  • X-RateLimit-Limit: Maximum requests allowed
  • X-RateLimit-Remaining: Requests remaining
  • X-RateLimit-Reset: Unix timestamp when limit resets

Support​

For integration assistance or technical questions, our support team is available to help you implement Cryptofuse in your application.