Changelog
What changed in Memoline, newest first. Each release is tested on Arc testnet before it ships.
2026-10-23
Screening against the UK and EU sanctions lists too
Every payee, sending address, payer and split-link wallet is screened against the UK Sanctions List and the EU’s financial sanctions list as well as the US Treasury’s sanctions list (OFAC).
- Three lists, each read daily. Memoline reads the US Treasury’s sanctions list (OFAC), the UK Sanctions List and the EU’s financial sanctions list once a day, each from its official source and each in a run of its own.
- Named where it matters. A payee set aside, a sending address stopped, a payer flagged on a link and a wallet refused in a split each name the list or lists that name the address.
- Never a false "clear". A payee is clear only when all three lists were read in the last 7 days and none names it. When one is older, the check names that list and says a payee added to it since then is not caught. An old list still sets aside the addresses it names.
- On the status page. Each list is shown with the date it was published and the day it was read.
- Not the UN list. The UN Security Council’s consolidated list names no wallet address, so it is not read.
- See paying people and getting paid.
2026-10-13
Clearer Coming up, receipts and invoices
Seventeen small fixes found in our reviews: Coming up reads as one sentence a wallet, a quoted payment’s receipt says its value in the invoice’s currency, and every invoice amount is grouped by thousands.
Seventeen small things our reviews found are fixed.
Coming up, on the Overview: each wallet reads as one sentence after its badge, with USDC named first in both of its sentences. A shortfall names its payout once, as a link. A wallet that also pays for another of your workspaces is shown amber rather than green, and only when that workspace has a payment due in the next 31 days or a payout still to send; a schedule that has ended or is paused no longer counts. A read you have no permission for no longer offers to try again.
Invoices in a local currency: the payer’s receipt says what the payment came to at its quote, such as "12.232091 USDC (1,180.00 INR at the quote)", and what is still to be paid in the invoice’s currency. Search shows such an invoice’s price, never "any amount". The day’s estimate refuses a price of zero in words, and x402 names the token the pay page quotes.
Everywhere else: every invoice amount is grouped by thousands, on your pages and the payer’s; the aging buckets read the same on Invoices and the Overview; the ledger’s totals list USDC, EURC, then the other stablecoins in a fixed order; a statement’s count of transactions missing from the ledger is grouped; a short reference moves to the next line whole on a phone; and attaching a transfer paid under another link’s memo no longer promises it counts there. See your books.
2026-10-13
A page for each job, and two honest comparisons
Pages for paying contractors, closing the month and invoices in a client’s currency; Memoline compared with Request Finance and with paying by hand; a developer landing.
Three new pages answer the jobs people come to Memoline for: paying contractors, closing the month and invoices in your client’s currency. Each says plainly when Memoline is not the right tool. Two comparisons set Memoline beside Request Finance and beside paying by hand from a wallet or a Safe, with when to choose them instead, each fact taken from their own pages with the day it was read. The developer page now starts with three steps: one call with no key, a key for your books, and an agent through the MCP server. The footer lists them all.
2026-10-13
Pages that say what changes for your business
The landing page leads with what Memoline does for a business, the pricing page works a month out for you, and the header gives visitors how it works, pricing, the API, help and both free tools.
The landing page now opens with what changes for a business: pay everyone in one signature, and close the month to the cent. Under it, four facts a careful buyer checks first, each linked to the help that proves it, then a real payout read back from Arc. The pricing page tells one cost story, your plan plus Memoline’s fee for each payment, works a month out as you type, and answers what counts as a payment. Visitors get a header of their own, with both free tools: check a payout file and look up an address.
2026-10-13
Every stablecoin on Arc in your books
Memoline now reads 22 stablecoins on Arc mainnet and 11 on testnet into your books, each in its own currency and counted once.
Your books now hold every stablecoin Memoline reads on Arc, not only USDC and EURC: 22 on mainnet and 11 on testnet, from Circle’s StableFX list and their issuers. Import an address and each payment in MXNB, BRLA, JPYC or any other listed stablecoin becomes a line in its own amount, in the ledger, statements, the Overview, exports and your accounting software, each in its own currency. Two stablecoins of one currency stay apart. A token that copies a real one’s name is never read. A month read before today is read once more when you close it, so any other stablecoin’s movements in it are found. Getting paid and paying out in them come next; today Memoline pays and collects in USDC and EURC. See the stablecoins Memoline reads and the counting rule, now version 1.2.0.
2026-10-08
Invoices in your client’s currency
An invoice can be priced in one of 54 currencies and paid in USDC or EURC, at an amount its pay page quotes and holds for 30 minutes.
An invoice can now be priced in your client’s own currency, one of 54, and paid in USDC or EURC. When your client opens the pay page, Memoline quotes the token amount at the day’s published rate and holds it for 30 minutes; the page shows the price, the rate, its source and its day before the wallet is asked. Your books keep the token amount, with the quote beside it. Memoline exchanges nothing. See invoices. Rates By Exchange Rate API.
2026-10-07
Split pay links
A payment link can now split its payment between your business wallet and up to 9 others, paid by the payer in one signature.
The workspace’s owner can now make a payment link that splits its payment between the business wallet and up to 9 other wallets, by amounts or by shares. The payer sees who gets what and signs once; each person is paid straight from the payer’s wallet, each part with its own memo on Arc, and the payment counts only when every part arrives together. Refunds send back your own part; split links carry no fee from Memoline. See getting paid.
2026-10-06
Coming up on the Overview
See what your payouts will take from each wallet in the next 31 days, and whether each wallet covers it today.
The Overview now opens with Coming up: every payout waiting to be sent and every schedule day not made yet in the next 31 days, each paying wallet’s balance read from Arc, and whether it covers what is due: the first payout it cannot cover, by how much, and what all 31 days need more. Both currencies are shown whatever the Overview’s currency switch says. It is a forecast; the check before you sign is the one that counts. The API has it at
GET /api/v1/upcoming. See your books.2026-10-05
Recurring payouts
Save a payout as a schedule and Memoline makes it again on each due day for a person to check and sign.
Choose Repeat this payout on the new payout form, set how often it repeats and until when, and press Save this schedule. On each due day, in your workspace’s time zone, Memoline makes that payout for a person to check and sign in their wallet, exactly like a payout made by hand; each payment’s reference carries the day, so SALARY becomes SALARY-2026-11-01 and each payout is a payment of its own in your books. A schedule pauses itself and says why if 3 of its payouts wait to be approved or signed, if the person who prepares it can no longer prepare, or if a payout could not be made; Make it now, Skip next, Edit, Resume and Delete manage it, and each payout carries Memoline’s fee like any payout. See recurring payouts.
2026-10-04
Payouts and app pages that say what is happening
Payouts with names, a list that says what each waits for, times in your time zone, the activity log in words, the terms accepted at sign-in, and what stops when someone leaves.
- Payouts have names. A payout takes its file’s name, or a one-payment payout its reference, and an operator, an admin or the owner can rename it. The name is never part of what approvals cover, and each rename is in the activity log.
- The payouts list says what each payout waits for: Waiting for approval, Checked, not signed yet, or Sending. It shows a hundred at a time, with older payouts a click away.
- Approvals and rejections are heard. When a payout’s approvals become enough, or it is rejected with a reason, the workspace hears it in the bell, on its notification channels and through its webhooks. The API reference describes
run.approvedandrun.rejected. - A rejected or discarded payout’s payments start a new payout from its page.
- The one case where a payment may go out twice says so. When another tab took a transaction over while your wallet’s prompt was still open, and both were sent, the page names both transactions and asks you to look them up on Arc before doing anything else.
- The sanctions screening is in the activity log. For each transaction screened before signing, it keeps the date of the US Treasury’s sanctions list (OFAC) it was screened against, when that list was read and what it found.
- Times in your time zone. Every app event (a payout made, a key used, a link opened, an approval) is shown in the workspace’s time zone, with the zone named. Book dates (ledger lines, statements, months) stay in UTC and say so.
- The activity log in words. Amounts, fields and times read as a person reads them, and its CSV gains an
in_wordscolumn; the stored entries never change. - Signing in accepts the terms, by version. The message your wallet signs names the version of the terms. Memoline keeps which version each address accepted and when, and asks again at the next sign-in after the terms change.
- What stops when someone leaves. Removing a person, their leaving, or making an admin anything less stops the API keys and auditor links they made and the webhooks and notification channels they added, unless whoever removes them keeps these working. The dialog names each one first.
- How control of an account was shown. An auditor link and a monthly statement say, for each account, whether the workspace signed in with the address or sent payouts from it through Memoline; otherwise, that it was imported by address only.
- Reminders wait for Arc. No reminder or overdue notice goes out before Arc is read for payments to the invoice’s pay link, so a customer who paid is never asked again.
- Invoices carry the seller’s address and tax number from Settings, copied when each invoice is issued and printed on it and on its pay page. Each invoice says why no reminder went out, or when the last went and when the next goes. An invoice’s pay link no longer names the customer in its public description, old links included.
- Close the books leads to the lines left to book. The ledger can show only the lines that need booking, and booking a line offers to make a rule for that address.
- The header has an account menu with the workspace switcher, Settings and Sign out. It says when the connected wallet is not the one signed in.
- Members by name, from the address book, on Members and in the activity log.
- Signed out, an app page says what it is and offers to sign in, instead of sending you away.
- Keyboard and screen readers. Errors are announced as alerts and progress in one polite region; a box holding a new key, link or recovery code takes the focus; choosing a workspace or a role only chooses, and a button then acts.
2026-10-04
Clearer public pages, and two new webhook events
Who Memoline is for, what a month of Memoline’s fee comes to, one way to reach a person, one name for the network fee, and webhooks for a payout’s approval and rejection.
- Two new webhook events.
run.approvedis sent once, when a payout’s approvals become enough, andrun.rejectedwhen a payout is rejected, with the reason. Every webhook endpoint receives them. See the API reference. - The home page says who Memoline is for, answers the questions a buyer asks in the help’s own words, and ends with a way to check a payout file or see pricing. Its headline no longer waits for Arc.
- Pricing says what Pro, Team and API add to Free, why there is both a plan and a fee, and, where the fee is charged, what a month of it comes to. Each card now says a workspace’s free payments are free once.
- One way to reach a person. The foot of every page, the help and the terms offer one contact: a private address where this site has one, otherwise a public question on GitHub that says it is public. Deletion requests and security reports are never sent to a public question: they go to the private address, which
/.well-known/security.txtnames, once this site has one. - The network fee. What a transaction costs on Arc is called the network fee on these pages and in the help, apart from the USDC counting rule, which is written for developers; the developer page and the API keep the word gas too.
- Getting started points to checking a payout file without signing in, and to Circle’s faucet at faucet.circle.com for test USDC.
- The terms name what the wallet code contacts when a page opens, every cookie and browser storage key, where Memoline’s servers run, and that an invoice’s pay page shows the customer’s billing address and tax id to anyone with its link.
- An auditor link says the name it shows is the one the workspace typed, which Memoline has not checked.
- Keyboard and screen. A Skip to content link comes first on every page, the footer stays at the foot of a short page, the wallet window takes Memoline’s colour, and a paid or closed payment request is no longer faded.
- Two new webhook events.
2026-10-04
One-time addresses
Pay each person at a fresh address made from their keys, so the chain shows a payment to a new address, not to their wallet.
A payer can tick Pay to one-time addresses on the new payout form, or send
oneTime: truewith a budgeted API key: each payment goes to a fresh address made from the payee’s registered keys, not to the payee’s wallet, and its reference stays in the payer’s books. A payee opens /receive with an ordinary wallet and presses Make my one-time keys (and, the first time, Register these keys), then Find my payments and Move this payment to collect each payment. One-time addresses take USDC payouts only and work on Arc testnet only today; see one-time addresses.2026-10-03
Auditor links
Share chosen accounts and dates with an auditor through a link to a read-only view, with no sign-in, that you can end at any time.
- A read-only view. In Settings, Auditor links, an admin or the owner makes a link to the ledger lines of chosen accounts, in one currency or both, between two dates. It needs a recent two-step code.
- Shown once. The link is shown once and kept only as a fingerprint. The view shows the newest 2,000 lines in the range, each linked to its Arc transaction, with a CSV to download.
- Your names go with it. The view and its CSV show your address book’s names for the counterparties and the workspace’s legal name.
- It ends. A link lasts 30 days by default, 90 at most, and you can end it at any time; ending one never waits for a second person. It opens at most 30 times an hour.
- Every opening logged. Each opening, a CSV download included, is logged with its time and a one-way fingerprint of where it came from, and admins see them. Anyone holding the link can read what it shows until it ends, so share it only with the auditor.
- A second person. While "A second person confirms changes" is on, a new link opens nothing until a second admin or the owner confirms it; the waiting change shows the accounts, the currency and the dates, and until when.
- See auditor links.
2026-10-03
The Memoline MCP client, as open source
The MCP server an AI agent uses to read Arc through Memoline is now MIT-licensed in the public repository, and coming to npm.
- Open source.
@memoline/mcp, the MCP server that reads Arc as ledger lines through Memoline’s public API, is MIT-licensed. Its source is in the public repository, in themcp/folder. - Read-only. It holds no funds and no wallet key, and never signs or sends. It offers four tools:
arc_transaction,arc_address,arc_link, andarc_statement(which needs a read API key). - Run it. It needs Node 20 or later. It is not on npm yet: build it from the source (
npm install,npm run build, thennode dist/main.js);npx -y @memoline/mcpruns it once it is published to npm. It reads Arc testnet unlessMEMOLINE_API_URLsays otherwise. - See the API, the MCP server and agents.
- Open source.
2026-10-03
Memoline’s fee
Where a site charges it, a payout pays 0.25 USDC for each payment in the same transaction, with a workspace’s first 10 payments free, once.
- The fee. Memoline’s fee: 0.25 USDC for each payment in a payout, paid in USDC in the same transaction as the payments (an EURC payout pays its fee in USDC too). Each row of a payout is one payment. It is never a percentage, and never charged on money you receive through links or invoices. The pricing page and the new payout form say whether this site charges the fee; where they show no fee, none is charged.
- First ten free. A workspace’s first 10 payments are free, once. A payment set aside at the check, or one in a payout that is never sent, still uses a free one. Discarding a payout, or its rejection before any of it is sent, gives its free payments back.
- All or nothing. The transaction stays atomic: every payment in it and the fee move together, or nothing moves.
- Shown before you sign. The new payout form shows the fee and the free payments left before you upload a file; the payout’s page, each transaction’s card, the approval request and the review before signing show it too. Settings, Plan and usage, shows the free payments left.
- In your books. The fee is a line "Memoline’s fee for a payout", booked to Expenses, and sent to Xero and QuickBooks as an expense.
- The monthly payout-row limit is gone from every plan: the fee replaces it. See plans and Memoline’s fee.
2026-10-03
Private payroll
Pay each person in their own transaction, so a payee sees only their own payment on the explorer.
- One payee per transaction. Tick "Private payroll: one payee per transaction" on the new payout form, or send
private: truewith a budgeted API key. A payee who opens their transaction sees only their own payment. - What stays visible. Anyone who looks up the paying address still sees every payment, the amounts and the payees.
- Signing. You sign one transaction per payee, and each pays its own network fee and, where this site charges it, Memoline’s fee for that payment. Each is sent on its own: a payee already paid stays paid if a later one is not sent.
- See paying people.
- One payee per transaction. Tick "Private payroll: one payee per transaction" on the new payout form, or send
2026-10-03
Screening against the US Treasury’s sanctions list (OFAC)
Every payout is screened against the US Treasury’s sanctions list (OFAC), read daily, before anyone signs.
- Read daily. Memoline reads the US Treasury’s sanctions list (OFAC) once a day from the official source.
- At every check. A payee the list names is set aside with words naming the US Treasury’s sanctions list (OFAC); a sending address it names stops the check. This happens for a signed-in payout and on the public check a file page alike.
- Never a false "clear". When the list has not been read in the last 7 days, the check says so, and so do the payout’s page, where it is approved and signed, and the review before signing; none of them calls the payees clear. An old list still sets aside the addresses it names, but a payee added to the list since then is not caught.
- Only this list. No other country’s sanctions list is checked. Circle’s own blocklist is still read from the token contract as well.
- See paying people.
2026-10-02
Agents named from Arc’s identity registry
Counterparties that are ERC-8004 agents show the name they gave themselves, checked on the chain, kept out of every file until you take it as yours.
- Agent names: an address registered as an agent in Arc’s ERC-8004 identity registry shows "Agent: its name (ERC-8004 #id)" in the ledger and on statements, set quieter than your own names and after them, and after a published contract’s name.
- Only names the chain stands behind: an address is named by an identity it registered itself and still owns, or whose agent wallet it is (set with that wallet’s own signature), confirmed on the chain before the name is kept. A token given to someone else names nobody, and several identities pointing at one address name nobody. An owner is named when the chain says it owns exactly one identity; a signed agent wallet once Memoline has read the registry’s whole history, which on testnet takes many daily reads. The name is cleaned (no control characters or direction marks, at most 60 characters).
- Kept out of your files: the agent’s own words never go into a Xero, QuickBooks or Memoline file, or into the keyed API’s line names; "Use this name" takes the name into your address book after you check it, and from then on it is yours.
- Read safely, once a day: a metadata file is read only over https from a public address, at most 64 KiB in 5 seconds with no redirects, or from a data address written on the chain. The keyed statement API gives agent names apart from your own, with their source; the MCP leaves them out, since an assistant reads everything it is handed.
2026-10-02
Agents prepare, people approve and sign
An agent member role and budgeted API keys prepare payouts that always wait for a person; the transaction API reads from any participant’s point of view.
- The agent role: add an AI agent or a script with its own wallet as a member in the agent role. It sees what a viewer sees and prepares payouts (makes them, pre-flights, acknowledges warnings and discards its own); it never sends, approves, downloads or changes settings. Every payout an agent prepares needs at least one person’s approval, even in a workspace that asks for none, and an operator, an admin or the owner signs it.
- Keys that prepare payouts: an API key with
payouts:preparesends rows and an idempotency key toPOST /api/v1/payouts. It carries a budget per currency (the most one payout may total, the most in any 24 hours) and may carry a payee list; a payout beyond them is refused with the numbers and nothing is written, a payout with any row error is refused whole, and a retry with the same idempotency key answers the same payout.GET /api/v1/payouts/{id},DELETE /api/v1/payouts/{id}andGET /api/v1/payouts/budgetread, discard and report. The approvers are told who prepared it, and the activity log names the key. - Honest words on budgets: a budget limits what a key may prepare, not what is sent; a person approves and signs every payout, and the agent’s own wallet policy is the hard limit on what it can spend.
2026-10-02
What the signer sees before signing
Every payee by name and whole address, warnings in words beside them, Circle’s blocklist read from the token contract, and a look before signing.
- Who is paid, whole: a payout’s page shows each payee’s name from your address book and its whole address, never the first and last characters alone, the shape address poisoning copies.
- Worth a second look: beside each payee, in words: the first payment to the address; an address that looks like one you have paid or named; a name set in the last 7 days or shared with another address; a contract instead of a personal wallet. Approvers see them too, from the moment the payout is made.
- A look before signing: a person who can send clicks "I have looked at these payees" before the first transaction is prepared for signing (a first payment alone does not ask). It is in the activity log, and a check that finds something new asks again. An agent never gives this look.
- Circle’s blocklist, read: the check reads Circle’s blocklist from the USDC or EURC contract for the sender and every payee before simulating. A blocked payee is set aside with those words; a blocked sender stops the check. A payment that fails with no reason is no longer called "blocklisted" when the list says otherwise.
- A payout prepared by an API key with a warning can now be looked at and checked from its own page, and the check answers with what to do instead of an error.
- What Arc shows: the payout form and pages say what one transaction and one sending address show to anyone who looks.
2026-10-02
Circle Gateway as money held at Circle
Deposits into Circle Gateway and money coming back from it are booked as the workspace’s own money held there, read from Circle’s own events.
- Held at Circle Gateway: a deposit into Circle Gateway (the wallet behind gas-free nanopayments) is still your money. Its line now reads "Deposited at Circle Gateway" and is booked to a new asset account of the default chart, Held at Circle Gateway; money coming back from a Gateway balance reads "Withdrawn from Circle Gateway" and is booked there too. The Overview leaves both out of money in and out, as it does bridges, and so does a line you book to Held at Circle Gateway yourself. Charts made earlier get the account the first time a line is booked (unless an account already uses its code, 1910; then give the role to an account yourself), and Gateway lines booked before it existed move there through Rules, Book past lines, which shows what would change before you confirm.
- Read from Circle’s own events, on the registered Gateway Wallet and Minter only, and matched to the one movement each describes, as the bridge words are. Older lines are named by the daily backfill. A nanopayment batch moves nothing on Arc and labels nothing.
- Honest words: the statement and the ledger say that Memoline shows what went to and came back from Gateway on Arc, and does not read the balance held there or the payments made from it.
- The Xero and QuickBooks files give these lines the payee Circle Gateway.
2026-10-02
Payments inside Circle Gateway, from your own file
Upload Gateway’s transfer history to see the month’s nanopayments under your statement, summed exactly and checked on Arc.
- Your Gateway history: payments made inside Circle Gateway settle in batches and never show on Arc one by one. Save the answer of Gateway’s
searchTransferswith your own key and upload it in Settings, Circle Gateway; the statement then lists the month’s payments received and sent, summed exactly per payer and payee, with how many batches they settled in. - All or nothing, and checked: one bad transfer refuses the whole file, naming it; only transfers to or from your accounts are kept; uploading again updates statuses only; each settled batch is checked on Arc against Circle’s Gateway Wallet, and the statement says how many were not seen.
- Kept apart from your books: these payments are never ledger lines and never go into your Xero or QuickBooks files, and Memoline holds no Circle key.
- Your Gateway history: payments made inside Circle Gateway settle in batches and never show on Arc one by one. Save the answer of Gateway’s
2026-10-02
The ledger and the statement show your newest choice
A slow answer to an earlier choice can no longer replace the page you asked for last.
- Only the newest answer is shown: opening a statement and ticking "Roll up by counterparty" at once, or switching between accounts in the ledger quickly, sends two requests whose answers can come back in either order. The page used to show whichever came last, so the rolled view could vanish, or one account’s lines could show under another’s name for a moment. Now an answer to an earlier choice is dropped when a newer one has been asked for.
2026-10-02
A transfer sent by someone else, read from the right side
The transaction API and the MCP name the payer and the payee of a relayed transfer, and read a transaction from any participant’s point of view.
- Who paid whom, whoever sent it: an x402 settlement, or any transfer relayed by a third wallet, is sent by an address that moved no money and only paid the gas.
GET /api/v1/tx/{hash}now listsnormalization.movements, the counting rule’s own list of who paid whom, and the MCP’sarc_transactiontells the payment from those movements and names the sender as the gas payer, instead of saying it "sent 0.00 USDC to itself". - Any participant’s point of view:
?account=0x…on the transaction API, andaccountonarc_transaction, answer the lines as that address’s books would hold them: the payee sees one payment in with no gas, the payer one payment out. An address that took no part gets no lines and a sentence saying so. The chain is read once; every point of view comes from memory. - The proof page says when the sender only paid the gas for a transfer between other addresses, and points to the participants below.
- Who paid whom, whoever sent it: an x402 settlement, or any transfer relayed by a third wallet, is sent by an address that moved no money and only paid the gas.
2026-10-02
A month of many small payments, rolled up
The monthly statement rolls up by counterparty, exact and never netted, with Xero and QuickBooks files that round once.
- Roll up by counterparty: on the monthly statement, one line per counterparty and direction, money in before money out, the largest first, with how many payments and when. Amounts are exact in the statement’s units (18 decimals for USDC, 6 for EURC) and are never netted; the sums are the statement’s totals, and the gas of lines to itself or lines that moved nothing is shown apart. It is computed in the database, so a month of a million payments is one query, not a million rows read. Each line opens the ledger filtered to its counterparty.
- Rolled files for Xero and QuickBooks: each rolled line’s cents come from the running total over the exact amounts, so the lines add up to the exact total rounded once; a thousand payments of 0.000999 USDC become 1.00, not 0.00.
2026-10-02
A second person confirms changes
Names, API keys, webhooks, channels, members, invites and approval settings can wait for a second admin before they take effect.
- One switch in Settings: "A second person confirms changes". It needs two people who can confirm (the owner and an admin, or two admins).
- What waits: a name in the address book (set, changed, removed, or a whole file), an API key, a webhook endpoint, a notification channel, a member, a role change, an invite, and the approval and two-step settings. An admin or the owner other than the person who asked confirms each one, with the two-step code.
- The whole change, shown: every name in an address book file, a key’s budget and the payees it may pay, and where an endpoint or a channel sends, before anyone confirms it.
- Nothing happens meanwhile: a waiting key is refused, a waiting endpoint or channel is sent nothing, a waiting invite link does not work, a waiting name is not used.
- Never applied on stale ground: a change applies only if what it changes is still as it was when asked, and only while the person who asked could still make it, so removing someone also stops what they asked for. A change waits up to 7 days, then ends unapplied, and what waited with it is revoked or turned off.
- Taking power away never waits: removing an endpoint, a channel or a member, withdrawing an invite and revoking a key apply at once. Turning the switch off waits for a second admin, unless the owner does it. Every request is in the activity log with its old and new values, and every decision with who made it.
- Two people, really: confirming asks for the two-step code from anyone who has turned it on, so each admin should turn it on (on the Team plan, an admin can require it).
2026-10-02
A statement for agents, in one call
The keyed API answers an account’s period rolled up by counterparty as one metered call, and the MCP reads it.
- The statement in one call (
GET /api/v1/statement): one of the workspace’s accounts over a period, rolled up by counterparty: the totals, the balances Arc reports at the period’s edges and whether it closes, and one line per counterparty and direction with the count of payments, exact and never netted. Computed in the database and counted as one call however many payments the period holds; 10,000 rolled lines an answer, with a cursor for the rest. - In the MCP server (
arc_statement): the same, in words an assistant reads, withMEMOLINE_API_KEYset to a read key. Names in the words and the data are the workspace’s own; a name from the ERC-8004 registry is left out of both.
- The statement in one call (
2026-10-01
Close the books
Lock a month once every account ties to Arc to the unit, with a report whose SHA-256 anyone can check.
- Close the books: lock a month once it has ended, in order, starting with the first month that has a line. Every account must tie to the balance Arc reports, every block must have been read, every transaction an account sent must have a line, and every line must be booked. A refusal lists every reason with what fixes it.
- Reading a month happens on the page while it is open, about half an hour for each account’s month, with each account’s progress shown; you can stop and carry on later.
- Transactions that moved no money (an approval, a failed transaction) are found and their gas recorded, so the statement can tie.
- The report of a locked month is a JSON file whose SHA-256 is shown and kept in the action log; the help says how to check it. A CSV made from it is offered too.
- A locked month cannot change: no line of it is booked again, changed or deleted, whatever writes. A line that arrives later is kept at its true date and listed in the next month’s report.
- Unlocking is for the owner, for the last locked month, with a reason. The old report and its hash are kept, and locking again makes a new version.
- Imports reach back at most 30 days, as they always should have; closing a month reads older blocks when it needs them, on the Close page.
2026-10-01
The Overview, alone or across workspaces
Money in and out by month, balances read from Arc, runway, and several workspaces viewed together with what moved between them.
- The Overview: money in and out by month for USDC and EURC apart, with moves between your own accounts and across bridges left out and shown on their own lines; network fees; payouts; balances at each month’s end read from Arc with the block they are of; whether each ended month ties to Arc; runway from how fast the balance fell; who paid you and who you paid most; totals by account of the chart; invoices owed. Every chart has its figures as a table.
- Several workspaces together: if you belong to more than one workspace, add others to the Overview, up to 10. A line two of them hold counts once, booked as the first in the list books it; each account and balance counts once; a payment between two of them is shown as a move between them, both sides, and left out of money in and out. You only ever see workspaces you are a member of.
- Network fees without an account: when the chart of accounts has no Network fees account yet, the Overview totals gas on a Network fees row of its own.
2026-09-30
Books say what each line was
USDC moved between blockchains by Circle’s bridge names the other blockchain, new and destroyed money says so, and known contracts say what they are, the same on statements, in the ledger and in every export.
- Bridge transfers name the blockchain. A line that came in or went out through Circle’s bridge (CCTP) reads "Received from Ethereum through Circle’s bridge" or "Sent to Base through Circle’s bridge", read from Circle’s own events in the transaction. An arrival says what fee the bridge took, and a departure through a router you named says which one.
- New and destroyed money says so: "Newly created (minted)" and "Destroyed (burned)", never the zero address.
- Known contracts say what they are, for example "Circle CCTP TokenMinter (bridge)" or "Circle USYC Teller (money market fund)".
- Xero and QuickBooks payees changed for these lines. Each kind has one payee: "Circle bridge (CCTP)", "Newly created (minted)" or "Destroyed (burned)". If a bank rule matches a payee exactly, check it after your next import.
- The Memoline CSV gains four columns at the end: what each line was, in the statement’s words, and what the bridge said (kind, CCTP domain, fee).
- Lines imported earlier are named from their transactions within a day.
- What it is: a name in the address book can say whether the address is a customer, a vendor, an employee, your own wallet, an exchange or other. It shows in the address book, and the address book file carries it.
- Two addresses cannot be named: the zero address and Arc’s own address for recording movements. Their lines already say what they are.
2026-09-30
Chart of accounts and rules
Every line is booked to an account of your chart, by rules you write, with the reason shown next to it and a person’s choice that sticks.
- Chart of accounts: a default chart to start from, your own codes, accounts retired never deleted, and the chart as a file to import or export.
- Every line is booked as it arrives, by one fixed order, and the ledger says why: a person’s choice, a move between your own accounts, a bridge, an own wallet not imported, a payment link or invoice, your rules, what the address book says, else Uncategorised.
- Rules: every condition together (money in or out, token, counterparty, what the address book says it is, an amount range, a reference exactly or by its start), first match from the top, each change a new version.
- Past lines change only after you see what would change and confirm it; a line that changed since you looked is left as it is.
- A person’s choice sticks through every re-import until they go back to the rules, and every change is kept with who and why.
- The statement and the Memoline CSV say which account each line is booked to.
2026-09-24
API keys for your own tools
Admins can make scoped API keys that read the workspace’s books and make payment links and invoices, counted and limited per plan.
- API keys in Settings, made by admins, shown once and kept only as a fingerprint. Each key has scopes: read, make and cancel payment links, make and issue invoices. See API keys.
- Test and live. Keys for Arc testnet start with
ml_test_and work only there; mainnet keys start withml_live_and come with the Team and API plans. - New calls: the workspace’s ledger lines, a page at a time; payment links (list, make, cancel); invoices (list, make and issue); this month’s usage. See the API reference.
- Counted, and never on someone’s behalf. Every call is counted before it runs, and a refused one is not. Keyed calls never use a browser’s sign-in. What a key does is in the activity log under its name.
2026-09-24
Invoices
Numbered invoices with exact line items and tax, paid wallet to wallet, with an aging report, reminders, recurring invoices and QR codes.
- Invoices. Customers, line items, tax, due dates; issuing numbers the invoice and makes its pay link. See invoices.
- Paid when Arc says so. An invoice is part paid, paid or overdue from the payments Arc shows; a payment after void is flagged and counted once.
- Still owed. An aging report by currency and days late, checked against the payments in the books.
- Reminders. Before, on and after the due date, each sent once. They go by email, where the site has it set up.
- Recurring invoices. A new invoice and link every cycle.
- QR codes. On invoices and pay pages, drawn by Memoline; no outside service sees the link.
- Print or save as PDF, for the invoice and for the customer’s copy on the pay page.
2026-09-24
Plans, limits and discarding a payout
Each workspace now has the limits of its plan, counted once and checked only when a payout is made, and a payout nothing of which was sent can be discarded.
- Plan and usage in Settings: your plan, this month’s payout rows and your members against the plan’s limits. See plans and limits.
- Counted once. A payout row counts once toward the month it was made in, however often a part is sent again, retried or adopted.
- Never stopped halfway. A limit is checked only when a payout is made; a payout already made is always finished.
- Discard a payout that has not been sent; its rows go back to the month.
- The pricing page now says what each plan allows today and what is still being built.
2026-09-24
Referrals
A link per workspace; a referred business gets 30 days free, and the referrer a month of Pro when it first pays.
- Refer a business in Settings: your workspace’s link. See referring a business.
- Earned once, at a real payment. The month of Pro comes when the referred business first pays after its free 30 days, once per business, never at sign-up. Never money.
2026-09-24
Settings, notifications and accessibility
A settings page, notifications in Slack, Discord, email and an in-app bell, a first-run checklist, and every page checked against WCAG 2.1 AA.
- Settings. Name the workspace, add a legal name, pick a default currency for new payouts and links, a usual paying address, a reporting currency and a time zone. A payout warns when you connect a different wallet from the usual one.
- Notifications. Hear about payments, fully paid links, refunds, finished payouts and finished imports in Slack or Discord (incoming webhooks), by email once the address is confirmed, where the site has email sending set up, and in the bell at the top of every page. Each channel chooses what it hears about. Deliveries are retried for twelve tries and are never sent twice by two workers.
- Webhooks now also send
run.completedandimport.completed. - Getting started. A checklist that ticks itself as you name the workspace, bring an address into your books, make a link or a payout, and connect notifications.
- Accessibility. Every page passes the WCAG 2.1 A and AA checks (axe-core) on desktop and phone.
2026-09-24
Teams, approvals and an activity log
Members with roles, invite links, approvals before a payout is sent, an activity log, search, address-book files and one-off payments.
- Members and roles. Add people by wallet address or with a one-time invite link, as admin, operator, approver or viewer. Every request checks the role. See teams, roles and approvals.
- Approvals. Ask for 1 or 2 approvals before a payout is sent, optionally above an amount. The person who prepared a payout cannot approve it, and a changed payout must be approved again.
- Activity log. Who did what, append-only, with a check that nothing was changed afterwards, and a CSV download.
- Search. One box for a transaction hash, address, exact amount, reference or name.
- Address book files. Import and export names as CSV, with checksum checks on import and formula-safe cells on export.
- Pay one person. A one-off payment through the same checks and approvals as a payout file.
- Your data. Download everything Memoline keeps for a workspace, and delete it.
- Payment links pay the business. A link now always pays the owner’s wallet, whoever in the team made it.
2026-09-24
Two-step sign-in
An authenticator code after the wallet sign-in, again before sensitive changes, and a Team rule that admins must use it.
- Two-step sign-in with any authenticator app, turned on in Settings, with 10 recovery codes shown once. See two-step sign-in.
- Asked again before sensitive changes when the last code is more than 15 minutes old: API keys, roles, removing members, the approval rule, the two-step rule and deleting the workspace.
- No code twice. A code that was used is refused, even within its 30 seconds, and tries are limited to five a minute.
- Team rule: admins and the owner must use it; without it they can only read.
2026-09-23
Books: statements, Xero and QuickBooks files, names and a public API
Monthly statements that tie to the balances Arc reports, files for Xero and QuickBooks, names for the addresses you pay, and a JSON API for any transaction or address.
- Monthly statements per address and currency: opening balance, every movement, gas, and a closing balance checked against Arc. When part of a month is not read yet, the statement says so instead of calling the books wrong.
- Xero and QuickBooks bank-statement files, with amounts rounded once so the file totals match to the cent.
- Names for the addresses you pay and get paid by, kept off-chain.
- A public JSON API for a transaction (
/api/v1/tx/{hash}) and an address’s recent movements, with exact integer amounts.
2026-09-23
Get paid: payment links, refunds, webhooks and agent payments
Payment links with your reference written on Arc, a pay page that checks everything before the wallet signs, refunds that are never sent twice, signed webhooks, and x402 for agents.
- Payment links for a fixed or open amount in USDC or EURC, with a due date, part payments that add up, overpaid and late payments flagged, and a name shown to payers.
- The pay page checks the wallet type, the balance and the gas, runs the exact transaction as a dry run, shows what will be signed, and confirms the payment from Arc itself. A payment whose confirmation is lost is checked, never offered again.
- Multisigs and exchanges pay with a plain transfer that the payer claims with a signature or the payee counts from the dashboard.
- Refunds from your own wallet, recorded as money out with their gas, sent at most once.
- Webhooks signed with HMAC-SHA256, retried with growing waits, with every resolved address checked so a webhook can never reach a private network.
- x402 on payment links for agents, settled by Circle’s facilitator, where a deployment has a Circle key.
2026-09-22
Payouts and reconciliation on Arc
Pay a whole spreadsheet from your own wallet with a reference on every payment, reconcile any Arc address, and read any transaction back as ledger lines.
- Payouts from a CSV: up to 2,000 rows, 100 payments per signed transaction through Arc’s Memo contract, each carrying your reference. Checked on Arc before you sign. Never paid twice, even if the browser closes halfway.
- Reconcile any Arc address into ledger lines that count each USDC movement once, with the gas each transaction cost.
- A proof page for any transaction. Memoline’s first real payout on Arc mainnet, three payments on 2026-09-23, is here.