Building a Membership Subscription with Binance Funds: Unlock Setup and Payment Collection

Binance

15 October 2026

There is no membership subscription feature called "Unlock" in the Binance ecosystem. However, if you are referring to using Binance Pay or Binance funds to set up an automatic debit-style subscription, it is technically possible. The path you take depends on where your users are and what currency you want to receive.

Binance Exchange
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!

First, Distinguish Between Two "Subscription Payment" Scenarios

Scenario 1: Users subscribe on your website or app, and you collect payments through Binance. This is the most common need. Your users already have Binance accounts, and you want them to complete subscription payments using Binance Pay, with the money going into your Binance funding account.

Scenario 2: Users subscribe on your website or app, but they use self-custody wallets. This requires an on-chain payment path and has nothing to do with the Binance account system.

The "Unlock setup" in the title is closer to Scenario 1 — users use the funds in their Binance accounts to "unlock" your membership content.

What You Need to Accept Binance Pay

Personal accounts cannot be used for automated payment collection. You must apply for a Binance Merchant Account at merchant.binance.com. Binance has stopped supporting individual merchant accounts and now strictly requires a registered business entity (KYB) to create a merchant account.

When applying, you need to submit proof of your business entity and complete the KYB review. Once approved, you will receive an API Key and Secret Key to integrate with your subscription system.

The Actual User Payment Flow

Users select a subscription plan on your website and click Binance Pay to pay. Your system generates a unique QR code with the amount corresponding to that order. The user scans the code with the Binance App and confirms the payment.

Funds immediately enter your Binance merchant wallet (which actually belongs to your funding account). After Binance Pay receives the payment, it will show up in your Funding Account, not your spot account.

The Most Common Integration Pitfalls

There is no sandbox environment. Binance Pay does not provide a testing environment. To verify that your integration is correct, you can only use real small transactions (such as 0.1 USDT) for testing. This means your tests will generate real on-chain or account-to-account transfers.

Minimum amount limits. Each currency has a minimum transfer amount. If your subscription price is very low (for example, $1 per month), it may not reach the minimum value for certain currencies. Before integrating, confirm whether the currency you plan to accept supports your pricing.

Webhooks must be configured. If your system does not correctly receive Binance Pay payment confirmation notifications, users will have paid but your order status will not update automatically. In the merchant portal's "Webhook Settings," confirm that the callback address is configured and can receive notifications properly.

On-chain payments from self-custody wallets are a different system. If your users do not use Binance accounts but pay from wallets like MetaMask, you need an on-chain payment solution, not Binance Pay. Binance's x402 protocol is designed for this type of scenario — it combines the HTTP 402 standard, self-custody wallet authorization, and stablecoin settlement on BNB Chain, supporting pay-per-call and usage-based billing. But this is a different technical path from "subscribing with Binance funds."

How to Reconcile After Receiving Payments

Binance Pay transaction records are in your Funding Account. Here is how to view them:

In the Binance App, go to the Pay page, and at the bottom there is History. You can filter by 24 hours, 1 week, 1 month, 3 months, 6 months, or a custom date range, then choose PDF/Excel/CSV format to export.

A more complete export path is through the Data Center: select the funding account, set the date range, choose a format, generate it, and download. Download links expire after 7 days, so save the file as soon as possible after generation. There is a monthly export limit, and the specific quota is shown on the export interface.

If you integrate via API, the /sapi/v1/pay/transactions endpoint can programmatically pull Binance Pay transaction history. Note that this endpoint requires a signature. The returned amount field shows positive numbers for income and negative numbers for expenses, and walletType value 1 represents the funding account.

Deciding Which Path to Take

If your users are mainly Binance users and you have a registered business entity: Apply for a Binance merchant account and integrate using the Binance Pay API. This is the most direct path, with fast settlement and low fees.

If you do not have a business entity, or your user base is not limited to Binance users: The Binance Pay merchant route will not work. Consider an on-chain payment solution (direct transfers from self-custody wallets), or use a third-party payment gateway (such as Clearqo, a service that confirms payments by reading your Binance transaction history through a read-only API).

If you only want to accept one-time payments, not subscriptions: Binance Pay's Payment Link is enough. You do not need a merchant account or API integration. Generate a link, send it to the user, and they click it to confirm payment.

The core of a "membership subscription" is recurring automatic debits. Binance Pay itself does not provide an automatic debit function — it is a series of one-by-one active payments. If your users need to manually scan a QR code to pay every month, that experience is different from a true "subscription." A real automatic subscription requires you to use your own system to manage billing cycles and payment reminders. Binance Pay is only the payment channel.