Skip to content
Blog

Why a multisig cannot write a memo on Arc, and how it can still pay an invoice

2026-09-24

Arc’s Memo contract only accepts calls from an ordinary wallet sending for itself. Safes and smart accounts are refused. Here is why, and the two ways a multisig can still pay a Memoline payment request.

Arc’s Memo contract lets a payer attach a reference, such as an invoice number, to a payment. The contract records who sent the memo, and it has to be sure that sender really is the wallet paying. So it only accepts a call made by an ordinary wallet (an externally owned account) for itself. A smart-contract wallet, such as a Safe or an ERC-4337 smart account, is refused. A wallet using an EIP-7702 delegation works when it sends the transaction itself.

What this means for a team that pays from a Safe

A Safe cannot send a payout with an invoice number on every payment. It can still send the money as a plain transfer. Memoline gives it two ways to count that transfer against a request:

  1. The payer claims it. On the pay page, the payer pastes the transaction and signs one message with the Safe. Memoline checks the signature the way a contract wallet signs (ERC-1271) and counts the transfer for the request. Signing moves no money.
  2. The payee counts it. On their own link page, the person who asked for the money pastes the transaction. It is their books, so no signature is needed.

In both cases the transfer must go to the payee, in the request’s token, after the request was made, and it can count for one request only.

Paying from an exchange

An exchange withdrawal is also a plain transfer, but nobody can sign for the exchange’s wallet. Send the transaction to the person who asked for the money; they can count it for the request.

See the help page on getting paid for the steps.