SafePal adds Arc support across its wallets

Arc support reaches the SafePal wallet suite

SafePal announced Arc integration on 16 September 2026 across its software wallet, hardware range and browser extension. Native-asset transfers and USDC/EURC vault access in Earn arrive together. Separate official instructions explain the mobile, S1 and browser workflows, giving users a practical route from the announcement to a transfer.

Add the Arc version of USDC in the mobile wallet

The software-wallet guide starts with an existing or newly created SafePal app wallet. From the homepage, open the three-dot menu and Manage Coins, search for USDC on Arc, then use the plus control to add it to the asset list. Opening that asset and choosing Receive displays the address to share with the sender. For an outgoing payment, choose Send, enter the amount and recipient, review the fee level and transaction details, then authorize with the security password or enabled fingerprint option. The guide finishes by checking the broadcast transaction's status.

This sequence separates adding an asset to the screen from receiving a payment. A new row in a wallet is not evidence that the expected money has arrived. For someone being paid an invoice, the meaningful result is the incoming transaction and balance, rather than the successful completion of the add-coin step.

An S1 uses the paired app and a device check

SafePal's S1 instructions assume the hardware wallet has already been set up and paired with the app. In that paired account, add USDC on Arc through Coin Management, then scan between the app and S1 to synchronize the asset information. The token appears in the device's Asset Management area. Selecting Receive and entering the PIN shows its address QR code. The guide explains that the offline S1 cannot automatically update balances; the paired app provides that view.

These are two distinct checks: the device presents the receiving information, while the connected app reports activity. When investigating an expected payment, a reader should therefore identify which observation is missing. An unchanged device display alone does not establish that the sender's transaction failed.

The browser approval path depends on the connected wallet

The extension guide also uses Manage Coins to add USDC on Arc. Receive exposes the address; Send begins with the recipient and amount. The subsequent approval route depends on the configuration. A standalone extension confirms locally. An app-paired extension hands the request to the app, and a hardware configuration adds the device's QR-signing step. After signing, the transaction is broadcast and its status can be checked.

For example, a person beginning a payment on a laptop may still need the paired phone or signer to finish it. Seeing a browser request is therefore different from completing all approvals. Before repeating a stalled attempt, establish whether the original request is waiting for authorization or has already produced a transaction.

USDC also pays the network fee

Arc fees use USDC, so that balance must cover both the payment and its quoted network cost.

Consider an invented invoice for 100 USDC and a hypothetical fee quote of 0.02 USDC. A balance of exactly 100 would fall short of the assumed total debit of 100.02. A balance of 101 would leave 0.98 after that simplified payment. These figures illustrate budgeting only; they are not an Arc fee estimate. The useful comparison is between the intended amount, the actual confirmation-screen charge and the available balance, all expressed in the same asset.

Earn remains a separate decision after receipt

SafePal names Morpho, Gauntlet and Steakhouse Financial in the Earn integration. Its announcement describes direct vault access without bridging, but provides no fixed yield or complete withdrawal terms.

A recipient who simply needed to collect an invoice has completed a different task from someone choosing an earning position. Moving the received balance into a vault should have its own reason and review. In particular, the amount needed for an upcoming payment should remain visible in that decision. The wallet integration makes more actions accessible, but it does not make depositing into Earn a required part of receiving or sending USDC.