dApps

Connect external dApps to your B2BINPAY DeFi account via WalletConnect and process dApp-initiated transactions through the queue

The dApps feature lets you connect external decentralized applications to your B2BINPAY DeFi account through the WalletConnect protocol. Connected dApps can request transactions and message signatures, which are routed to the account queue for multisig approval.

The dApp connection control is only visible when both conditions are met:

The current account is on an EVM-compatible network (the feature is not available for TVM networks such as Tron).
The account's smart contract version is 1.1.0 or later. For earlier contract versions, upgrade the account to use dApps.

Access the dApp panel

The dApp connection control is located in the header, next to the wallet selector.

The button indicates the current state:

No badge, no dot: No active sessions and no pending messages.
Green dot: At least one active dApp session.
Red badge: Pending messages or transactions from connected dApps await approval in the queue. The badge shows the number of pending items.

Click the button to open the dApp side panel, which contains the URI input field and the list of active sessions.

Common use cases

Connect a dApp

Connect a new dApp to the current account using a WalletConnect URI.

In the external dApp, choose WalletConnect as the connection method and copy the connection URI (for example, wc:...).

In the B2BINPAY DeFi app, click the dApp connection button in the header.

Paste the URI into the WalletConnect URI input and click Connect.

In the Session approval popup, review:

The dApp name, icon, and URL.
The verification status — VERIFIED, UNKNOWN, or a warning if the dApp is flagged as malicious.
The list of networks the dApp requests access to.
The connected account address.

Then click Approve to establish the session or Reject to cancel the request.

The Approve button is disabled if the dApp requests unsupported WalletConnect methods or is flagged as malicious. In those cases, only Reject is available.

Approve a dApp transaction request

When a connected dApp requests a transaction, a modal appears for your review.

In the Transaction approval popup, review:

The dApp name and icon.
The From and To addresses.
The transaction Value.
The raw Data (hex calldata) — use the Copy icon to copy it.
The Decoded data section, when available — shows the function signature and parameter values.

Click Approve to send the request to the queue as a dApp transaction, or Reject to decline.

Open the Queue page to collect required signatures and execute the operation. See Queue for details.

Approve a dApp message signature request

When a dApp requests a personal or typed-data signature, a separate modal appears.

In the Message signature popup, review:

The dApp name and icon.
The Message contents.
The Required signatures count for the current account.
The Address and raw Hex under the collapsible details section.

Click Sign to add the message to the queue for multisig signing, or Reject to decline.

View and disconnect active sessions

Click the dApp connection button in the header to open the side panel.

Under the URI input, review the list of active sessions with dApp names, icons, and session details.

Click the Disconnect action next to a session to terminate it and confirm the action in the popup.

Disconnecting does not cancel pending dApp transactions already in the queue — handle them on the Queue page.

dApp-initiated transactions in the queue

Transactions created from a dApp request appear in the Queue list with the following characteristics:

The Operation column shows the dApp name and icon instead of a generic type label.
Clicking the dApp name link opens the dApp's URL in a new tab.
Canceling or deleting the operation from the queue sends a cancellation event back to the dApp.

For the full queue workflow, see Queue.