CW Backend Guide
Overview of core CW management functions and modules
CW is the most commonly used tool in daily work. Here is a brief description of the common functions of CW. Proficiency in using CW is a basic requirement for every customer service representative.
Collect Wallet
User score record query, users can query the order information generated when they increase their scores on the game platform here
Flowchart of the process of order generation
CW-Collect Wallet-The picture shows
Important order information explanation:
Creditor ID:The upstream ID represents the order information generated by the upstream. You can query all the points records of the user through the ID.
Order No:The order number of the transaction. Sometimes the upstream company will ask us to help check the order arrival status, and we need to use Order No to query
MC Order No:The upstream order number, also called the MC order number, is required when querying in the MC management background。
Status:The current transaction status of this order
Paying:The order is still being paidTimeout:Payment timeoutPre-Generated: Prepaid order, which means the order has just been generatedSuccess:Payment successful, Indicates that the transaction has been completed
Payer Ct:The payment method used by the payer is only Balance
Payee name:The name of the wallet of the receiving merchant
Order(Collect)
Upstream purchase record query, the order generated when the upstream purchases the user's INR, that is, in the transaction, when the buyer is the upstream and the seller is the user, the order information generated can be queried here
Flowchart of the process of order generation
CW-Order(Collect)-The picture shows
-a719d7d8fbef6c3f3075f39796104b1b.png)
Important order information explanation:
Creditor ID:The ID of the upstream, indicating the order information generated by that upstream
MC Order No:The upstream order number, also called the MC order number, is required when querying in the MC management background。
Order No:The order number of this transaction. Sometimes the upstream will ask us to help check the order arrival status, and we need to use Order No to query.
Amount:The amount of order transaction
Status:The current status of this transaction.
Paying:The order is still being paidTimeout:Payment timeoutSuccess:The order has been completed
Allo review:Payee's tool information review
OK:Everything is fineneed Ct ldle:Unable to connect to the payee's tool, typically occurs when retrieving the bill after a successful payment, at which point the payee is offline
Payee UPI:During the transaction, the payee uses a UPI to receive INR
Payee Ct:Payee's UPI type and ID for receiving INR
Order(Upstream Collect)
Upstream sales record query,Upstream sales INR Order information generated when the user purchases,That is Trading,The buyer is the user,When the seller is upstream,The generated order information can be queried here
Flowchart of the process of order generation
CW-Order(Upstream Collect)-The picture shows
Important order information explanation:
Order No:The order number of the transaction，The order number can be found at CW，MC The platform queries the transaction information
Upstream Order No:This is the upstream order number. When a manual query is required in the upstream group, you need to copy this order number to the upstream group for inquiry.
Amount:The amount of order transaction
Status
Paying:The order is still being paidTimeout:Payment timeoutSuccess:Order transaction completedFail:Order transaction failed
Payer:The payment status of the payer
Paying:The payer is making paymentPending:When it happens pending This means that there is a dispute in this order Sometimes the user fills in the wrong UTR，Sometimes users deliberately forge UTR Sometimes it is upstream delays that lead to not receiving moneySuccess:Payer payment completed，Order transaction completed
Payer CW:Payee of ID。Often through IDTo query the user's order information details
UTR:After the payer completes the payment，The only transaction certificate filled in，Often through Utr To check whether the transaction is completed
Pay Bank
Bank purchase record query, when the user purchases INR through the Bank method, the generated order information can be queried here
When the user uses the Bank method to purchase INR, it is necessary to bind UPI, which will help us query his payment information. When everything goes well, the transaction will be automatically completed。
Flowchart of the process of order generation
CW-Pay Bank-The picture shows
Important order information explanation:
Order No:Order Number，Displayed in the user Purchase record，By querying the order number，Helps to quickly locate problem orders
Mc Order No:Upstream order number，When needed MC When verifying order status ，use MC Order No exist MC Make an inquiry
Payer:The payment status of the payer，Appear pending hour，Need to check whether the transaction is real and valid
Utr:After the payer completes the payment，The only transaction certificate filled in，Often through Utr To check whether the transaction is completed
Bank Purchase due to the specificity of the purchase，So it is automatically reviewed by the system
Pay Market
Trading market trading records When both the buyer and the seller are The user is The generated order information can be queried here
Flowchart of the process of order generation
CW-Pay Market-The picture shows
Important order information explanation:
Payer Cw:Buy INR User's ID，Received when the transaction is completed INR Users
Payee Cw:sell INR User's ID，The user who gets the money when the transaction is completed
Payee Ct:
Payee's UPI type and ID for receiving INR
When the transaction is completed The money will be transferred to this UPI
Sometimes we need to go through this ID To check the status of the recipient's tool
Status:Status of the transaction
Paying:Transaction in progressPending:Transaction FailureSuccess:Transaction completed
Payer:The payment status of the payer
Paying:The payer is making a paymentPending:When the payer's payment is false UTR，null UTR. Or the system is unable to obtain the transaction bill.Success:Payment Completed，Usually also represents the completion of the transaction
Payee:The recipient's payment status
Pre-Generated:Prepaid Status，Order just placed，Wait until the transaction continuesPending:when payee When the bill is not available or payer The status triggered when payment is abnormalSuccess:Transaction completed
Utr: After the payer completes the payment，The only transaction certificate filled in，UtrIs important transaction verification information
Pay Wallet
User's Points Record Query， The order information generated when users win money and place points on the game platform can be queried in this line
Flowchart of the process of order generation
CW-Pay Wallet-The picture shows
Important order information explanation:
Order No:Transaction order number, you can quickly query order information through order No
Mc OrderNo:Upstream order number, order number in MC, can be used to query order information in MC management background through MC Order No
Amount:The number of issued
Creditor ID:Merchant ID. Through Creditor ID, we can know which merchant issued the points.
Payee CW:The payee's ID in the CW backend
Wallet Adress:The wallet address to receive INR.
Status
Pre-Generated:Prepaid order, indicating that the order has just been applied for by the userSuccess:The order transaction is complete.
UTR:Pay Wallet The Utr in the table is automatically filled in by the system, with a very low probability of duplication or error.
Utr Remark:System record of the transfer from a merchant wallet to a user wallet
Record-Balance
User balance records, records of user balance changes can be queried here. Note: User balance changes are transfer records of user balances, including user purchase records, sales records, and points and deposits records on the game platform
CW-Record-Balance-The picture shows
Important order information explanation:
Collection Worker:User's ID，pass ID You can query a user's balance change record
Type:Common status explanations for balance changes
Transfer Out:Balance transfer record，Transferring out does not mean INR Already sold，Maybe it's on consignment.Transfer In:Balance income records, including transfer records from stop selling and transfer records from game platformsBuy:Transfer record of users purchasing INRPayment:The balance transfer record for users using balance to top up on gaming platforms.record of users adding pointsReward:User's record of obtaining system rewards
Amount:The amount of INR used for each operation message
Order No:The source order number when the balance changes，transfer In、payment、buy There will be order number information in these three states，Can be Order No Combination Type，Go to the corresponding place to inquire，Details of orders where the user's balance has changed
Remark:Transfer-in and transfer-out instructions
Admin Remark:Transfer-in and transfer-out instructions automatically filled in by the system
Record-Buy
The record of users purchasing INR. The transaction records generated when users purchase INR can be queried here
CW-Record-Buy-The picture shows
Important order information explanation:
Status:Common status explanations
-
Success:Purchase Success -
Fail:Purchase failed -
Review:Re-examine the order and check the transaction information
Amount:The amount of INR used for each operation message
Paymentslip OrderNo:Payment order number, the order source of this purchase record.
Record-Quota
The user's balance change records from selling INR. Note that not all selling records indicate a successful sale; it is important to carefully distinguish between successful and failed sale records
CW-Record-Quota-The picture shows
Important order information explanation:
Type:Common status explanations
Transfer Out:Transfer record:the user stops selling and transfers the amount to the balanceTransfer In:Transfer record:The user starts selling and transfers the balance to the credit limitDeductedThe record of the system deducting the balance when a sale is successfulRetrun:The record of the system refunding the user's balance when an order requires a refund
Amount: INR Number of transactions
After Amount: After the transaction，What the user has left INR quantity
OrderNo: The order number of the transaction information
UTR: After the payer completes the payment，The only transaction certificate filled in，UtrIs important transaction verification information
Admin remark: The system's description of this transaction information
SellInfo
Sales information, a collection of related process queries when users sell INR. Including the user's current status, user tool check, user tool bill check, and user transaction records.
When you are proficient in CW management, you can use SellInfo to quickly query all the user's sales information
CW-SellInfo-The picture shows
User
A collection of user information, used to query user-related information.
CW-User-The picture shows
User Important Information:
Collection Worder ID:UserID. Through the user ID, we can query the user's historical transaction records in each different functional module.
In Sell:Is the selling function enabled?
Bill Pending:Are there any disputed bills that need to be dealt with?，bill Pending There is a special document describing the processing
Wallet Adress:User's wallet address，You can use the wallet address User Query the user's ID，Conversely, you can also use Collection Worder ID Query the user's wallet address
User Assets – User's asset information
Records all the user's asset information
Balance: User's balance，Show in Home
Quota:The amount of INR that the user is selling is displayed in the Sell interface. Note that Quota represents what is being sold.
USDT、Trx：Not enabled yet
User Ct
The user's UPI tool information. Check whether the user has tools, how many tools there are, and the status of each tool
In daily operations, the majority of order processing requires regular verification of the Payee Ct status. This can be queried through this section using the Ct IDExample:phonepe(25650), User ID, or UPI.
CW-User Ct-The picture shows
User Ct Important Information Explanation:
CollectionWorker:The user's ID in the CW backend, which is also referred to as Payee CW or Collection ID in some forms
Ct Info:The ID of the user's tool. In some forms, it is referred to as Payer Ct or Payee Ct, where the text outside the parentheses indicates the Ct type, and the number inside the parentheses represents the specific Ct ID.
| Field Name | Example | Description |
|---|---|---|
| Payer Ct | Payer Ct (12345678) | Ct type is Payer, with the specific Ct ID inside parentheses. |
| Payee Ct | Payee Ct (87654321) | Ct type is Payee, with the specific Ct ID inside parentheses. |
Different forms may display different Ct types. Always refer to the actual field labels provided in each form.
Pn Name:The name entered by the user when binding their UPI. It does not necessarily represent the user's real name.
UPI:The UPI account that the user has linked to their wallet.
Quota:The amount currently available for selling.
All Quota:The total amount that has already been involved in transactions. In some cases, this amount may be negative, indicating that the transaction has been paid but the system has not yet retrieved the bill for verification.
Is Collect:Click to view the tool's status. This feature is commonly used during tool inspections.
Below is a description of frequently used fields related to tool status
| Field | Value Example | Description |
|---|---|---|
| Status | Available | The tool is active and in use. |
| Pause | The user has temporarily paused the tool. | |
| State | Disabled | The tool is offline; user must ensure it stays online. |
| Idle | The tool is currently online. | |
| Lock | 0 | Indicates whether the tool is locked. 0 means it is not locked. |
| In Risk | OK | Normal condition, no risk. |
| Risk | The tool is under risk control and requires manual clearance. | |
| Bill Pending | OK | No pending bills; everything is normal. |
| Exist Pending | Pending bills exist for this tool. | |
| Ct Sell | — | Indicates whether the tool is eligible to sell INR. |
| Auto Sell | — | Indicates whether automatic selling is enabled for the tool. |
User Ct Bill
User's UPI tool bill:
Used to query the user's UPI transaction records. You can check whether a specific bill exists by using the UTR, or retrieve all bills by using the user’s ID.
In transaction processing, the user's Ct bill is one of the most important pieces of information. In many cases, determining whether a transaction is completed relies on analyzing the bill details.
CW-User Ct Bill-The picture shows
Important order information explanation:
CollectionWorker: The user's ID in the CW backend. In some forms, it is displayed as Payee CW.
collectionTool: Information about the tool used for receiving payments. In some forms, it is displayed as Payee Ct.
OrderNo: The order associated with this bill. This may not always be accurate, as in some private transactions, the system retrieves the OrderNo merely as the UPI transfer ID.
UPI: The UPI used for this bill.
Amount: The transaction amount of this bill.
UTR: The UTR (Unique Transaction Reference) associated with this bill.
Admin Remark: System log describing what happened to the bill, such as manual creation, pending cancellation, or system auto-deduction.
Pick Up: The bill's trigger status,Currently undocumented; we are not focusing on this for now.
Bill Type: The type of this bill.
-
Receive: Indicates that the user received money. -
Send: Indicates that the user transferred money to someone else.
Deducted: The deduction status of the bill.
-
Deducted: The user's balance has been deducted. -
No need: No deduction is needed, usually meaning this bill is unrelated to . -
Pending: The system cannot automatically determine whether this bill should result in a deduction. This is commonly referred to asCt Bill Pending.
A user's bill list simply represents all UPI transactions retrieved by the system. It does not mean that every bill is related to .
It's common to encounter bills without corresponding orders, or orders without corresponding bills.
Accurately matching a bill with its corresponding order is one of the most challenging tasks in daily operations.
Field Classification
🧑💻 User Information Fields
| Field Name | Meaning | Notes |
|---|---|---|
| CollectionWorker | The user's ID in the CW backend | Sometimes referred to as Payee CW / Collection ID |
| Pn Name | The name bound to the user's UPI | Not necessarily the real name |
| UPI | The user's UPI account | — |
| Quota | Current selling quota | — |
| All Quota | Total quota currently involved in transactions | Can be negative |
| Wallet Address | Wallet address linked to user's account | Used in Pay Wallet module |
| Balance | User's INR balance in | — |
| USDT / TRX | Reserved fields for future use | Not enabled yet |
🧾 Order Information Fields
| Field Name | Meaning | Notes |
|---|---|---|
| Order No | The main transaction order number | Used for cross-checking orders |
| MC Order No | Upstream platform's order number | Used for MC backend checks |
| Upstream Order No | Specific order number for upstream manual query | Shown in Upstream Collect module |
| Amount | Transaction amount | — |
| Status | Transaction status | Paying / Timeout / Success / Fail etc. |
| UTR | Unique Transaction Reference ID | Critical for verifying transaction validity |
| Paymentslip OrderNo | Payment voucher order number | Shown in buy records |
| Admin Remark | System description of an order or bill | — |
🔧 Tool (Ct) Information Fields
| Field Name | Meaning | Notes |
|---|---|---|
| collectionTool | Tool used to collect payments (UPI tool) | Also called Payee Ct |
| Payee Ct | Payee's tool type and ID | e.g., phonepe(12345) |
| Payer Ct | Payer's tool type and ID | — |
| Is Collect | Whether tool is in use | Available / Paused |
| In Risk | Risk control status of the tool | OK / Risk |
| Bill Pending | Whether there are pending disputed bills | Important for manual intervention |
| Ct Sell | Whether the tool can sell INR | — |
| Auto Sell | Whether the tool is set to auto-sell | — |
💳 Bill (Transaction Record) Fields
| Field Name | Meaning | Notes |
|---|---|---|
| Bill Type | Bill type: Receive or Send | Indicates incoming or outgoing funds |
| Deducted | Deduction status of the bill | Deducted / No need / Pending |
| Pick Up | Trigger status of the bill | Currently no detailed documentation |
| Utr Remark | Record for wallet-to-wallet transfer | Only in Pay Wallet |
🔄 Balance/Quota Change Fields
| Field Name | Meaning | Notes |
|---|---|---|
| Type | Type of balance/quota change | Transfer In / Transfer Out / Buy / Payment etc. |
| Amount | Amount involved in balance or quota change | — |
| After Amount | Balance or quota left after the operation | — |
| Order No (Balance/Quota) | Source order for balance/quota change | — |
| Remark | Manual note on transfer | — |
| Admin Remark | System-automated remark | — |
Relationship between CollectionWorker, Payer CW, and Payee CW
-
CollectionWorker:
Refers to the user's unique ID in the CW backend system. It is the base ID used internally across different modules to identify a user. -
Payer CW:
When the user acts as a buyer, their CollectionWorker ID is referred to as Payer CW.
Example: In Upstream Collect, the user purchasing INR from upstream is the Payer CW. -
Payee CW:
When the user acts as a seller, their CollectionWorker ID is referred to as Payee CW.
Example: In Pay Market, the user selling INR to another user is identified by Payee CW.
In simple terms:
- CollectionWorker = general user ID in CW
- Payer CW = CollectionWorker when the user is the payer
- Payee CW = CollectionWorker when the user is the payee