Payments and profiles

This guide covers Client 0.8.11 and calls out Explorer 1.2.1 differences. Last verified October 26, 2026. For exchange withdrawals, use funding with Mountaintops.

Receive from a compatible wallet

Open Send & Receive in Client and select the receiving Wallet profile. Share its identity key with a sender whose wallet supports identity-key payments. In Explorer, open Receive to view and share the receiving identity. Check the selected profile before copying it.

Review incoming payments in Receive and accept the intended payment. Explorer offers individual Receive actions and Receive All for waiting payments. Some transfers between your own Explorer profiles are received automatically; check the destination balance and incoming list before treating one as missing.

An identity key is public, but sharing it can link activity to you. It does not authorize a sender to spend your funds. Never share a recovery key in its place.

Send a payment

1. Choose the sending profile and check its available balance and network.
2. Enter the recipient in the format the selected payment mode requests. An identity key and a traditional address are different inputs; do not substitute one for the other.
3. Enter the amount and read the displayed unit. 1 BSV = 100,000,000 satoshis. A converted USD display is not a separate USD balance.
4. Review the recipient, source profile, amount and fees before confirming.
5. Check the resulting status and Activity. The recipient may need to accept the payment before it becomes spendable in their wallet.

For app purchases, also check the app's receipt or entitlement. A wallet transaction and the app granting access are separate outcomes. Keep the transaction ID and contact the app if access did not arrive; do not immediately buy again.

Client 0.8.11 can also send directly to a traditional type-1 BSV address. Choose Person or service and paste the address into Recipient. Check the selected Currency, Amount (unit) and network, especially for an exchange deposit. This outbound capability is separate from receiving an exchange withdrawal into Metanet. Explorer users can use Mountaintops' outbound form inside its browser. Follow the exchange-deposit guide.

Move money between your own Client profiles

In Client's Send & Receive, select the sending Wallet profile and use My profiles for the destination. Client preserves the signed payment on that device. Switch to the destination profile, open Receive and use Accept saved payment to credit it.

Selecting a destination profile alone does not accept a saved payment. Keep the original device's app data until it is accepted. A local saved payment is not guaranteed to exist on your other computer or phone.

New-profile funding checks whether the source can cover the payment and transaction fee. Profile/account updates can have a separately disclosed fee; read it before approving. Creating a profile does not move every balance, identity, permission or backup setting from another profile.

Pending, interrupted or returned payments

Client saves signed payments before delivery. If a delivery acknowledgement is missing, use the retained payment and status information rather than creating a second send. A transaction can exist even when the sending app did not receive confirmation.

If the status is unclear, check Activity, the destination's Receive screen and any transaction ID first. Keep the original signed-payment record. Client asks for confirmation before returning a payment; a return is another wallet operation, not simply deleting a message.

See payment troubleshooting and Explorer FAQ for the next checks.