Filtering P2P Counterparties with Advertisement Requirements
Summary
The document explains how a Bitget P2P merchant can screen counterparties when setting up an advertisement. Requirements determine who may place an order before the merchant accepts it or starts a trade. The listed filters cover completed order counts, a per-user order cap, account registration age, the counterparty’s asset balance, merchant eligibility, recent completion rate, and KYC country.
Examples show how thresholds can admit users with minimum, maximum, or bounded completed-order counts, restrict each user to one order, require a stated asset balance, or set a recent completion-rate threshold. Merchants can also allow other merchants to trade and select one or more countries. These are configurable eligibility rules, not a trading strategy or evidence of improved execution or reduced fraud. The guide is a product walkthrough and gives no data on outcomes; merchants would need to choose thresholds appropriate to their own risk and market conditions.
Key ideas
- Merchants can enable counterparty requirements while creating a P2P advertisement.
- Completed-order counts can be filtered with minimum, maximum, or range conditions.
- Per-user order limits and account age can restrict who places orders.
- Asset balance, recent completion rate, merchant status, and KYC country are additional filters.
- The guide describes configuration options but provides no evidence about their effect on trading outcomes.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.