Why Destination Wallets Are Locked & Immutable

1. The Immutability Principle

When an operator adds a destination wallet address (Ethereum ERC-20 or TRON TRC-20) to PayCow, the platform assigns a permanent Serial ID (e.g. WAL-1001) and permanently locks the entry. Locked wallet addresses cannot be deleted, updated, or modified via the Operator Dashboard or API endpoints.

2. The Threat Vector: Unauthorized Account Access

In conventional payment gateway platforms, a common attack vector involves unauthorized access to merchant accounts via compromised credentials, phishing, session hijacking, or stolen API tokens. In such breach scenarios, an attacker typically attempts to:

• Edit existing settlement wallet addresses to point to an attacker-controlled external wallet.
• Delete legitimate merchant wallet records and register malicious destination addresses.

If wallet addresses were mutable, all subsequent customer payments generated via payment links or checkout APIs would immediately be diverted to the attacker's wallet, resulting in unrecoverable financial losses.

3. How Wallet Serial IDs Neutralize Wallet-Swapping Attacks

PayCow decouples transaction routing from mutable dashboard state by introducing locked Wallet Serial IDs:

• Static Binding: When an operator configures a destination wallet address, it receives an immutable reference ID (e.g. WAL-1001).
• API Payment Creation: Checkout requests reference the Serial ID (e.g. walletSerialId: "WAL-1001").
• Immutability Guarantee: Because an entry linked to WAL-1001 can never be altered or deleted, even if an attacker gains full administrative access to your PayCow portal, they cannot modify the actual destination wallet address bound to WAL-1001.

As a result, your API integrations and automated checkout systems continue routing 100% of customer deposits directly to your verified cold wallet address, neutralizing the risk of payment redirection.

4. Wallet Modifications & Emergency Support Protocol

While existing wallet records cannot be self-edited or deleted via the dashboard, operators can always add new destination wallet addresses (which receive new unique Serial IDs like WAL-1002, WAL-1003).

If an operator legitimately needs to edit or decommission a locked destination wallet address, the following security protocol is enforced (strictly Zero-KYC):

• Live Support Initiation: The merchant must initiate a ticket via PayCow Live Support.
• Registered Admin Email Verification: Support will send an explicit authorization confirmation to the exact email address registered to the account (e.g. [email protected]).
• Strict Email Matching Requirement: All wallet modification approvals and support inquiries must be conducted exclusively through the registered account email address. Requests from unverified third-party emails (e.g. [email protected]) will be immediately rejected, and no wallet modifications or technical support will be granted.

5. Technical Summary