Skip to main content
Version: Current guides

Configure and verify merchant wallets

Availability and wallet purpose​

Public availability of dashboard wallet creation, verification, activation, multiple-wallet allocation and defaults remains unconfirmed. Configure them only when enabled for the account. Settlement execution requires separate confirmation. Confirm wallet allocation, contract-wallet support and default-switching rules individually.

The merchant controls its wallet. Account access, API credentials and wallet signing rights are separate. Resetting a login password does not recover a wallet. Never give the platform or a customer private keys, seed phrases or complete recovery materials.

Check before adding a wallet​

Prepare the target network, full address, internal purpose label and responsible signer. Read the address from the wallet itself and independently compare the full string. Valid formatting does not prove business ownership or that the same address on another network accepts the same asset.

Confirm the complete network and asset combination is supported for the account and that the wallet type is supported. Do not substitute an exchange deposit address or a wallet unable to complete the required signing process.

When wallet configuration is enabled​

  1. Open wallet settings with authorized access, choose a supported network and enter the full address and purpose label.
  2. Connect the corresponding wallet and verify control as instructed. Check the signing site, message and selected account. Proof of control is different from a funds transfer.
  3. Have another responsible person compare the network and address before submission. After saving, check whether the wallet is verified, pending or disabled rather than relying on a save message.
  4. Set defaults or activate wallets only where offered, ensuring you do not disable the only available payment route.
  5. Verify the related workflow in an authorized test environment. Agree any production validation transfer and its fees with your contact and business owner; do not blindly send test assets.
  6. Record the operator, time, previous and new settings, then inspect the new payment entry.

Replace or remove a wallet​

List unresolved Checkouts, refunds and settlements first, and ensure the old wallet can complete bound operations. A created settlement's recipient is fixed; changing the dashboard default does not redirect it. Do not delete old signing materials or assume disabling a wallet cancels tasks.

After reviewing pending tasks, change supported settings with the proper permission and verify new orders. Retain the old address for historical reconciliation. If the wallet is lost, its address appears altered or control is uncertain, stop new affected operations and use account security.

Resolve problems​

ProblemNext action
Duplicate or rejected addressCheck the network and existing records; do not alter a character to bypass validation
Rejected signature or wrong networkCheck the original task, account and network, then resume
Settings saved but collection failsCheck verification, activation, permissions and methods, not just address formatting
Settlement sent but not receivedInspect the original task and transaction using settlements, without resending
Wallet management is missingConfirm the supported configuration route with your contact; do not use unpublished management interfaces