> For the complete documentation index, see [llms.txt](https://doc.tokenpay.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.tokenpay.me/common-problems/white-label-vs.-payment-api-a-deep-dive-into-web3-payment-solutions.md).
# White Label vs. Payment API: A Deep Dive into Web3 Payment Solutions
### Core Concept Analysis
**Payment API**\
As a foundational payment solution, it supports multi-chain (ETH/BNB/TRON/POLYGON etc.) and multi-currency (USDT/USDC/ETH/BNB) payments. Its core advantages include:
* ntegrated payment system (PC/H5 adaptive)
* Multi-chain transaction reports and balance change tracking
* Suitable for general payment scenarios
**White Label** \
An customized upgrade on top of payment API services. Its core value lies in:
* Brand-specific payment interface (logo replaceable)
* No redirection to third-party payment terminals, completing payments entirely within merchant websites
* Suitable for brand-oriented payment scenarios
### Rate Difference
\
**Payment API**\
The lowest handing fee 0.8%,and no additional fees
**White Label** \
The lowest handing fee 1%,and no additional fees
### Selection Recommendations
White Label and Payment API are different concepts, although their APIs are basically related. White Label is a customized, logo-free cash register for branded merchants, which allows the merchant user to complete the entire process from product purchase to payment without a webpage jump, and also allows branded merchants to use their own merchant name and brand logo in the customized cash register.
**Choose Collection API:**
* Need rapid integration
* Project in early stage
* Focus on basic payment functions
**Choose White Label :**
* Require brand payment entrance
* Have customization needs
* Need deep integration with existing system