Sendclap Notes

Taking crypto payments without holding the money: how Sendclap's contract pays creators in USDC on Base

Sendclap's contract sends a supporter's USDC straight to the creator and 1% to its fee address, and never holds a balance. What the code does, checked on Base on 2026-11-18, and what it doesn't cover.

5 min read

On this page
  1. How a one-off payment moves
  2. Subscriptions without a custodian
  3. Paying from an AI agent: why there is a second contract
  4. What this does not cover
  5. Where this fits next to Coinbase Commerce
  6. FAQ

Sendclap takes crypto payments without ever holding the money: a supporter’s USDC goes from their wallet to the creator’s wallet in a single transaction on Base, and the same transaction sends Sendclap’s 1% to its fee address. The contract has no balance to lose, no withdraw function and no way to charge more than 1%. This is how it works, read from the code and checked on-chain on 2026-11-18, including what it deliberately does not do.

If you went looking for a crypto payment option after Coinbase Commerce, the reason to care about this design is custody. A processor that holds your balance between the payment and your payout is a company you have to trust with it. Here there is nothing in between to trust, only a short contract you can read.

How a one-off payment moves

The contract is called Sendclap and lives at 0x3aFF4fa297B7aa8D009281e348E5312d8e93ef9b on Base. A tip or a product purchase is one call to pay(creator, amount, ref). Inside it does the arithmetic and two token transfers:

fee = amount * feeBps / 10_000;
usdc.transferFrom(from, to, amount - fee);          // the creator
if (fee > 0) usdc.transferFrom(from, feeRecipient, fee);  // Sendclap

Both transfers pull from the payer’s own wallet, so USDC is never parked in the contract. I read its USDC balance on Base today and it was 0, which is what the code predicts: there is nowhere for money to sit. The ref field is a 32-byte reference that ties the payment to an order on Sendclap’s side, and the contract emits it in a Paid event so the checkout can confirm what happened.

The fee is 100 basis points on-chain today (feeBps() returned 100). A constant MAX_FEE_BPS = 100 is the ceiling: setFee reverts with FeeTooHigh above it, so the owner can lower the fee or change where it goes, and can never raise it past 1%. There is no proxy and no upgrade path in the source, and no function that moves anyone’s tokens, so the owner’s powers stop there. Both contracts are verified on Sourcify as exact matches (verified 2026-11-13), which means the source on that page is the code running at those addresses.

Subscriptions without a custodian

A crypto membership is a standing permission, not a deposit. The member calls subscribe, which records the creator, the amount and the period and pays the first period right away. After that the payer needs to keep a USDC allowance for the contract. Anyone can call charge(id) once a period is due, and Sendclap runs a keeper that does so, but the contract only ever moves exactly the agreed amount.

A few details from the code that matter if you are comparing this to a card subscription:

  • charge collects at most one period per call and never backfills. A lapsed membership resumes from now instead of billing for the months it was unpaid.
  • Either side can end it with cancel, and the payer can also lower the allowance in their own wallet, which stops the next charge without asking anyone.
  • If the wallet doesn’t hold enough USDC when a charge is due, the transfer reverts and nothing is collected.
  • The keeper pays the gas for charges, so the member doesn’t pay a network fee on each renewal.

On mainnet the nextSubId counter reads 2, so exactly one subscription had been created at the time of writing. The design is live and the volume is small, and I’d rather say that than imply otherwise.

Paying from an AI agent: why there is a second contract

The x402 standard lets a program pay for a request, and its “exact” scheme names a single recipient. That doesn’t fit a 99/1 split. So SendclapSplit gives every creator a deterministic address, built with CREATE2 as a tiny EIP-1167 proxy that works before anything is deployed to it. USDC sent there belongs to nobody else. Anyone can call release(creator) afterwards and the creator’s share goes to the creator and the fee to Sendclap, again with a 1% cap in the code.

I fetched the live challenge for the demo creator today:

GET https://sendclap.com/x402/demo/tip?amount=5
HTTP/2 402
"scheme":"exact","network":"eip155:8453","amount":"5000000",
"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"payTo":"0x356fA73928F97900F923B503515F93dB7Ab82eB3","maxTimeoutSeconds":120

The amount is $5 in USDC’s six decimals, on Base (eip155:8453), and payTo is that creator’s split address, not Sendclap’s. Its USDC balance was 0 as well. The project’s notes say a full paid flow was run on a local fork of Base mainnet and that no real mainnet x402 payment had been made yet, so I did not make one either.

What this does not cover

  • Taxes. Sendclap is not a merchant of record. You report your own income and handle any VAT, the same as when you accept crypto directly.
  • Refunds. The contract has no refund function. Money moves once, to the creator, and sending some back is a payment you make yourself. Card payments through Stripe have dispute handling; this path does not.
  • Gas. For a one-off payment the supporter’s wallet sends the transaction, so they pay Base network fees, usually small but theirs.
  • Other tokens. The contract takes USDC only. A supporter with another token or another chain is routed to USDC on Base by the checkout page first, through a third-party swap and bridge service, before the contract is called.
  • An audit. I found no audit linked in the repository. The source is short and verified, and the tests are in contracts/test/, but I did not run them for this post.
  • Fiat. A crypto payment ends up as USDC in the creator’s wallet. Turning it into local currency is on you.

Where this fits next to Coinbase Commerce

Coinbase Commerce was reported to close on 31 March 2026. I could not read Coinbase’s own notice (its help site shows a bot check to automated readers), so I am relying on secondary reports for that date and won’t describe its details. What I can describe is how Sendclap differs: no custody at any step, a fee fixed in code at 1% with no processing fee on crypto, and a memberships model that needs no deposit. What it lacks is invoices, physical goods and tax handling, so a business that needs those will want something else.

Sendclap’s fee on a $10 crypto payment is $0.10, so the creator receives $9.90. The full table for $10, $50 and $100, by card and by crypto, is in what a 1% creator fee works out to.

FAQ

Can Sendclap’s owner take creators’ money? Not through the contracts. They have no function that moves anyone’s tokens, only one that sets the fee (capped at 1%) and the address it is sent to.

Which chain and token? USDC on Base mainnet. Telegram Wallet payments in USDT on TON are a separate path with the same 1% split.

Who pays gas on a renewal? The keeper that calls charge, not the member.

Written and checked on 2026-11-18 against backmeupplz/sendclap at commit 1c5ac91, Base mainnet and sendclap.com. Contract values were read with eth_call on a public Base RPC.

Sendclap is a page for memberships, tips and digital products at a flat 1% fee, paid by card or crypto.

Read next