<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tom Wang</title>
    <description>The latest articles on DEV Community by Tom Wang (@tomwangcn).</description>
    <link>https://dev.to/tomwangcn</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3850103%2F8fa92041-b06f-4727-9b1f-4b9b304d4c8e.png</url>
      <title>DEV Community: Tom Wang</title>
      <link>https://dev.to/tomwangcn</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tomwangcn"/>
    <language>en</language>
    <item>
      <title>USDC vs USDT Blacklist: Where a Payout Gets Stuck</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Sat, 14 Nov 2026 08:25:05 +0000</pubDate>
      <link>https://dev.to/tomwangcn/usdc-vs-usdt-blacklist-where-a-payout-gets-stuck-3g2a</link>
      <guid>https://dev.to/tomwangcn/usdc-vs-usdt-blacklist-where-a-payout-gets-stuck-3g2a</guid>
      <description>&lt;p&gt;Send USDC to an address Circle has blacklisted and the transaction reverts. You keep the money and get an error string. Send USDT to an address Tether has blacklisted and the transaction succeeds, the balance lands, and from then on only Tether can move it.&lt;/p&gt;

&lt;p&gt;I checked both against live mainnet state this morning, using addresses Tether froze on Tron at 23:32 UTC and on Ethereum at 23:35 UTC on 13 November 2026. Two of the guides ranking for "USDT blacklist check" and "can USDC be frozen" say a blacklisted address cannot receive USDT. The contract says otherwise, and if you run payouts, that difference decides who absorbs the loss.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can USDC and USDT Be Frozen?
&lt;/h2&gt;

&lt;p&gt;Yes. Both issuers can freeze any address on any chain where they control the token contract. What differs is which side of a transfer gets checked, who holds the key, and whether the issuer can destroy the frozen balance afterwards.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;USDC / EURC&lt;/th&gt;
&lt;th&gt;USDT (Ethereum, Tron)&lt;/th&gt;
&lt;th&gt;PYUSD&lt;/th&gt;
&lt;th&gt;RLUSD&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Freeze call&lt;/td&gt;
&lt;td&gt;&lt;code&gt;blacklist(address)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;addBlackList(address)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;freeze(address)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;pauseAccounts(...)&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who calls it&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;blacklister&lt;/code&gt;, a single EOA&lt;/td&gt;
&lt;td&gt;Owner, a 3-of-6 multisig&lt;/td&gt;
&lt;td&gt;&lt;code&gt;ASSET_PROTECTION_ROLE&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;PAUSER_ROLE&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Status getter&lt;/td&gt;
&lt;td&gt;&lt;code&gt;isBlacklisted&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;isBlackListed&lt;/code&gt;, &lt;code&gt;getBlackListStatus&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;&lt;code&gt;isFrozen&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;accountPaused&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Recipient checked?&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;No&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Destroy frozen balance?&lt;/td&gt;
&lt;td&gt;No function exists&lt;/td&gt;
&lt;td&gt;&lt;code&gt;destroyBlackFunds&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;wipeFrozenAddress&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;clawback&lt;/code&gt;, no freeze needed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;USDC and EURC share one implementation contract (&lt;code&gt;0x4350…02dd&lt;/code&gt;, &lt;code&gt;FiatTokenV2_2&lt;/code&gt;), so everything below about USDC applies to EURC on Ethereum too.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Does the USDC Blacklist Work?
&lt;/h2&gt;

&lt;p&gt;Circle's FiatToken puts a &lt;code&gt;notBlacklisted&lt;/code&gt; modifier on every function that moves value. &lt;code&gt;transfer&lt;/code&gt; checks &lt;code&gt;msg.sender&lt;/code&gt; and &lt;code&gt;to&lt;/code&gt;. &lt;code&gt;transferFrom&lt;/code&gt; checks the spender, &lt;code&gt;from&lt;/code&gt; and &lt;code&gt;to&lt;/code&gt;. EIP-3009's &lt;code&gt;transferWithAuthorization&lt;/code&gt; checks &lt;code&gt;from&lt;/code&gt; and &lt;code&gt;to&lt;/code&gt; but not the relayer that submits it, which I covered in the &lt;a href="https://dev.to/news/2026-10-20-eip-3009-vs-eip-2612-vs-permit2-gasless-usdc"&gt;gasless USDC comparison&lt;/a&gt;. Any hit reverts with &lt;code&gt;Blacklistable: account is blacklisted&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Three implementation details matter for integrators.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The flag lives in the balance slot.&lt;/strong&gt; Since v2.2, &lt;code&gt;balanceAndBlacklistStates[account]&lt;/code&gt; stores the balance in the low 255 bits and the blacklist flag in bit 255. &lt;code&gt;isBlacklisted&lt;/code&gt; is a shift, &lt;code&gt;&amp;gt;&amp;gt; 255 == 1&lt;/code&gt;. Packing the two saves gas on every transfer, but anyone reading the raw slot, in a storage proof for example, gets the flag mixed into the balance and has to mask bit 255.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;approve&lt;/code&gt; no longer checks the blacklist.&lt;/strong&gt; Commit &lt;code&gt;e5e7a2a&lt;/code&gt; (17 August 2023) removed the modifier from &lt;code&gt;approve&lt;/code&gt;, &lt;code&gt;permit&lt;/code&gt; and the allowance helpers. I confirmed it on mainnet: a blacklisted owner can still set an allowance, and anyone can approve a blacklisted spender. The allowance is useless, because &lt;code&gt;transferFrom&lt;/code&gt; checks all three parties, but a monitoring rule that alerts on "approval by blacklisted address" will fire on things that are not attacks.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-11-14-usdc-vs-usdt-blacklist-freeze-guide" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>stablecoin</category>
      <category>usdc</category>
      <category>cryptopayments</category>
      <category>security</category>
    </item>
    <item>
      <title>Bacs ARUDD, ADDACS, AUDDIS Codes: Which to Retry</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Sun, 08 Nov 2026 12:03:49 +0000</pubDate>
      <link>https://dev.to/tomwangcn/bacs-arudd-addacs-auddis-codes-which-to-retry-49n2</link>
      <guid>https://dev.to/tomwangcn/bacs-arudd-addacs-auddis-codes-which-to-retry-49n2</guid>
      <description>&lt;p&gt;ARUDD code &lt;code&gt;0&lt;/code&gt; is a failed payment you can try again. ADDACS code &lt;code&gt;0&lt;/code&gt; is a cancelled mandate you must stop debiting. Both are one character from the same scheme, so a handler that switches on the character alone will eventually collect against an instruction that no longer exists.&lt;/p&gt;

&lt;p&gt;Bacs Direct Debit reports trouble through separate report types, each with its own code table and clock, and providers then squash those codes into their own API enums. Below are the full tables, the codes that are safe to re-present, the arithmetic that limits you to about two retries, and how GoCardless and Stripe expose all of it. On sourcing: the Bacs Service User's Guide and DDIC challenge guide are login-only, so some timings come from bureau and participant documentation, and I name those. Confirm them with your sponsor bank.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Are Bacs ARUDD, ADDACS and AUDDIS Reports?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Report&lt;/th&gt;
&lt;th&gt;Fires when&lt;/th&gt;
&lt;th&gt;Typical arrival&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AUDDIS&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;A new instruction (&lt;code&gt;0N&lt;/code&gt;) is rejected&lt;/td&gt;
&lt;td&gt;About 3 working days after submission (GoCardless)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;ARUDD&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;A collection goes unpaid&lt;/td&gt;
&lt;td&gt;1 to 2 working days after the collection date&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;ADDACS&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The payer's bank cancels or changes a mandate&lt;/td&gt;
&lt;td&gt;Early on the working day after the bank's input&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;DDIC&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The payer claims under the Direct Debit Guarantee&lt;/td&gt;
&lt;td&gt;Any time, with no published limit&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;AWACS is the Direct Credit counterpart, so it concerns payroll and supplier payments. You get three working days to act on an AWACS or ADDACS advice, and receiving an AWACS is itself your authority to update the details.&lt;/p&gt;

&lt;p&gt;Reports expire. Most stay on the Bacs Payment Services Website for 37 calendar days, ADDACS and AWACS for 60, so an ingestion job that fails quietly for six weeks loses data for good. Bacs's guide to maintaining payment details gives each advice record a sequential &lt;code&gt;A0SN&lt;/code&gt; reference, which is the field to watch for gaps. If you normalise to ISO 20022 internally, Bacs's 2017 translation guide maps ARUDD to &lt;code&gt;camt.054&lt;/code&gt;, AUDDIS returns to &lt;code&gt;pain.012&lt;/code&gt; and ADDACS to &lt;code&gt;pain.010&lt;/code&gt; and &lt;code&gt;pain.011&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  ARUDD Reason Codes: Which Unpaid Direct Debits Can You Retry?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Code&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;th&gt;Handling&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;0&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Refer to payer&lt;/td&gt;
&lt;td&gt;Re-present&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Instruction cancelled&lt;/td&gt;
&lt;td&gt;Stop, new mandate needed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;2&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Payer deceased&lt;/td&gt;
&lt;td&gt;Stop permanently&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;3&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Account transferred&lt;/td&gt;
&lt;td&gt;Get new details or a new mandate&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;4&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Advance notice disputed&lt;/td&gt;
&lt;td&gt;Stop until resolved&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;5&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;No account (or wrong account type)&lt;/td&gt;
&lt;td&gt;Fix details or new mandate&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;6&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;No instruction&lt;/td&gt;
&lt;td&gt;Check your records, new mandate&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;7&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Amount differs&lt;/td&gt;
&lt;td&gt;Stop until resolved&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;8&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Amount not yet due&lt;/td&gt;
&lt;td&gt;Stop until resolved&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;9&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Presentation overdue&lt;/td&gt;
&lt;td&gt;Fresh advance notice&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;A&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Service user differs&lt;/td&gt;
&lt;td&gt;Fix your submission&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;B&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Account closed&lt;/td&gt;
&lt;td&gt;Stop, new mandate needed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-11-08-bacs-arudd-addacs-auddis-reason-codes-guide" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>paymentinfrastructure</category>
    </item>
    <item>
      <title>Privy vs Turnkey vs Coinbase CDP: Agent Spend Caps</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Sat, 07 Nov 2026 12:56:31 +0000</pubDate>
      <link>https://dev.to/tomwangcn/privy-vs-turnkey-vs-coinbase-cdp-agent-spend-caps-284h</link>
      <guid>https://dev.to/tomwangcn/privy-vs-turnkey-vs-coinbase-cdp-agent-spend-caps-284h</guid>
      <description>&lt;p&gt;Write a Coinbase CDP wallet policy that caps &lt;code&gt;sendEvmTransaction&lt;/code&gt; at $100 and nothing else, and your agent can still call &lt;code&gt;signEvmHash&lt;/code&gt;, which signs any 32-byte hash, with no limit at all. CDP's documented rule is that an operation no policy mentions is accepted. Privy and Turnkey both do the opposite and deny anything you did not allow.&lt;/p&gt;

&lt;p&gt;That difference, and a handful like it, decides how much an agent wallet can lose when the model goes wrong. None of the pages ranking for "privy vs turnkey" show it. The top results are Turnkey's own &lt;code&gt;/vs/privy&lt;/code&gt; pages, Crossmint's alternatives page and cost calculators. None of them puts the three policy formats side by side or says whether the wallet can enforce a daily cap, which is the first thing an agent builder needs to know. Everything below is checked against each vendor's docs, OpenAPI spec and pricing page as of 7 November 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is a Wallet Policy Engine for AI Agents?
&lt;/h2&gt;

&lt;p&gt;An agent wallet is a server-side key that your code, or an LLM acting through your code, asks to sign things. A policy engine sits between the request and the key. It parses what is about to be signed (destination, value, calldata, typed-data fields), checks that against rules you wrote, and refuses to sign if they fail.&lt;/p&gt;

&lt;p&gt;All three vendors run keys in AWS Nitro Enclaves. Privy splits each key 2-of-2 with Shamir secret sharing, with one share that only the enclave can decrypt. Turnkey runs its signer and its policy engine inside enclaves on QuorumOS, its own minimal Linux unikernel, with reproducible builds that operators check against the enclave attestation. CDP keeps keys in a Nitro TEE and guards wallet calls with a Wallet Secret, a P-256 key that signs a JWT sent as &lt;code&gt;X-Wallet-Auth&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The enclave stops someone stealing the key. It does nothing about your own agent asking for a bad signature, and that is where the policy engine has to do the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Privy vs Turnkey vs Coinbase CDP: Policy Engines Compared
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Coinbase CDP&lt;/th&gt;
&lt;th&gt;Privy&lt;/th&gt;
&lt;th&gt;Turnkey&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Rule format&lt;/td&gt;
&lt;td&gt;JSON rules with typed criteria&lt;/td&gt;
&lt;td&gt;JSON rules with field conditions&lt;/td&gt;
&lt;td&gt;Expression language strings&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Unmatched operation&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;Accepted&lt;/strong&gt; if no rule targets it&lt;/td&gt;
&lt;td&gt;Denied&lt;/td&gt;
&lt;td&gt;Denied (implicit deny)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Conflict rule&lt;/td&gt;
&lt;td&gt;Matching &lt;code&gt;reject&lt;/code&gt; beats &lt;code&gt;accept&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;DENY&lt;/code&gt; beats &lt;code&gt;ALLOW&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;EFFECT_DENY&lt;/code&gt; beats &lt;code&gt;EFFECT_ALLOW&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Policies per wallet&lt;/td&gt;
&lt;td&gt;1 project + 1 account&lt;/td&gt;
&lt;td&gt;1 per wallet, 1 override per signer&lt;/td&gt;
&lt;td&gt;5 per organisation (250 on Enterprise)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;USD-denominated check&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;netUSDChange&lt;/code&gt;, per transaction&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rolling spend cap&lt;/td&gt;
&lt;td&gt;Not public (&lt;code&gt;rateLimiting&lt;/code&gt; in spec only)&lt;/td&gt;
&lt;td&gt;Yes, aggregations, 1 to 72 hours&lt;/td&gt;
&lt;td&gt;Not released ("usage controls" in SDKs)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who can bypass&lt;/td&gt;
&lt;td&gt;API key with "Manage" scope edits policy&lt;/td&gt;
&lt;td&gt;Wallet owner; app secret if no owner set&lt;/td&gt;
&lt;td&gt;Root quorum, by design&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rejection error&lt;/td&gt;
&lt;td&gt;HTTP 403 &lt;code&gt;policy_violation&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;HTTP 400 &lt;code&gt;policy_violation&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;OUTCOME_DENY_EXPLICIT&lt;/code&gt; / &lt;code&gt;_IMPLICIT&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-11-07-privy-vs-turnkey-vs-coinbase-cdp-agent-wallet-policies" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>aiagents</category>
    </item>
    <item>
      <title>Transactional Outbox in Postgres: Polling vs CDC</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Fri, 06 Nov 2026 08:28:37 +0000</pubDate>
      <link>https://dev.to/tomwangcn/transactional-outbox-in-postgres-polling-vs-cdc-4dmn</link>
      <guid>https://dev.to/tomwangcn/transactional-outbox-in-postgres-polling-vs-cdc-4dmn</guid>
      <description>&lt;p&gt;An outbox poller that reads &lt;code&gt;WHERE id &amp;gt; last_seen_id&lt;/code&gt; loses events in Postgres, and it takes two transactions to prove it. The first took &lt;code&gt;id = 1&lt;/code&gt; and committed three seconds late. The second took &lt;code&gt;id = 2&lt;/code&gt; and committed at once, so the poller advanced its cursor to 2 and never published the &lt;code&gt;payment.captured&lt;/code&gt; event in row 1.&lt;/p&gt;

&lt;p&gt;Most pages ranking for "transactional outbox pattern" explain the dual-write problem and stop there. Of the seven top results I checked, one mentions this skip, via a link. None warns that the CDC alternative can fill your disk, and none is written for payment events, where a lost message is a merchant who never hears a refund cleared. So I ran the failure modes in a throwaway Postgres 18.6 container. Unless I say otherwise, the output below is pasted from those runs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is the Transactional Outbox Pattern?
&lt;/h2&gt;

&lt;p&gt;When a capture succeeds, a payment service posts ledger entries and tells everything downstream: webhooks, reconciliation, the warehouse. Commit to Postgres and then publish to Kafka, and a crash between the two leaves money moved with no event. Publish first, and a rollback announces money that never moved. Kafka transactions are atomic across Kafka partitions only, so two-phase commit is off the table.&lt;/p&gt;

&lt;p&gt;The outbox puts the event inside the same database transaction:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;BEGIN&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;INSERT&lt;/span&gt; &lt;span class="k"&gt;INTO&lt;/span&gt; &lt;span class="n"&gt;ledger_entries&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;account&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;VALUES&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'acc_123'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1000&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'clearing'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;1000&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="k"&gt;INSERT&lt;/span&gt; &lt;span class="k"&gt;INTO&lt;/span&gt; &lt;span class="n"&gt;outbox&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;aggregate_id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;type&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;payload&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;VALUES&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'pay_8f2c'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'payment.captured'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'{"amount":1000,"currency":"GBP"}'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="k"&gt;COMMIT&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A relay then publishes committed rows. That gives at-least-once delivery, because the relay can crash after publishing and before recording progress. Every interesting decision sits in how the relay reads the table.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does an Outbox Poller Skip Events in Postgres?
&lt;/h2&gt;

&lt;p&gt;A sequence hands out its value when the row is inserted, but the row only becomes visible when its transaction commits. &lt;code&gt;BIGSERIAL&lt;/code&gt; is a sequence, so &lt;code&gt;id&lt;/code&gt; order is insert order, not commit order:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;B got id=2 txid=755
--- t~1s naive poller (id &amp;gt; 0):
2|pay_B
A got id=1 txid=754
--- t~4s naive poller resumes from high-water mark id &amp;gt; 2:
(empty = pay_A skipped forever)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A transaction that does more work after its outbox insert, such as a fraud-score call before the final ledger write, can commit after a later one. The poller sees a gap at &lt;code&gt;id = 1&lt;/code&gt; that looks exactly like a rolled-back insert, so it cannot tell a lost event from a harmless hole. A &lt;code&gt;created_at&lt;/code&gt; cursor has the same flaw, plus clock skew between pods.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-11-06-transactional-outbox-postgres-polling-vs-cdc" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>paymentinfrastructure</category>
    </item>
    <item>
      <title>rust_decimal vs bigdecimal: Money Types in Rust</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Tue, 03 Nov 2026 11:01:45 +0000</pubDate>
      <link>https://dev.to/tomwangcn/rustdecimal-vs-bigdecimal-money-types-in-rust-3bhc</link>
      <guid>https://dev.to/tomwangcn/rustdecimal-vs-bigdecimal-money-types-in-rust-3bhc</guid>
      <description>&lt;p&gt;&lt;code&gt;Decimal::from_str("100000000000.000000000000000001")&lt;/code&gt; returns &lt;code&gt;Ok&lt;/code&gt;. The value inside is &lt;code&gt;100000000000.00000000000000000&lt;/code&gt;: rust_decimal dropped the last wei to fit its 96-bit mantissa and raised no error. Call &lt;code&gt;Decimal::from_str_exact&lt;/code&gt; on the same string and you get &lt;code&gt;Err(Underflow)&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The pages ranking for "rust_decimal vs bigdecimal" mostly stop at "fixed-size and fast versus arbitrary precision", which is true and not enough to choose with. So I built a scratch crate against rust_decimal 1.43.0 and bigdecimal 0.4.11 on Rust 1.98 and ran the cases payment code hits: token amounts, rounding, JSON, Postgres and overflow. Unless I say otherwise, every output below is pasted from that run.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Should You Represent Money in Rust?
&lt;/h2&gt;

&lt;p&gt;There are five realistic options, and one of them is wrong.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Type&lt;/th&gt;
&lt;th&gt;Exact decimals?&lt;/th&gt;
&lt;th&gt;Size&lt;/th&gt;
&lt;th&gt;Heap?&lt;/th&gt;
&lt;th&gt;Range&lt;/th&gt;
&lt;th&gt;Use it for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;f64&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;8 bytes&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;15 to 17 significant digits&lt;/td&gt;
&lt;td&gt;Nothing involving amounts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;i64&lt;/code&gt; minor units&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;8 bytes&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;±9.22 × 10¹⁸ minor units&lt;/td&gt;
&lt;td&gt;Fiat balances and postings&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;i128&lt;/code&gt; / &lt;code&gt;u128&lt;/code&gt; minor units&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;16 bytes&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;up to 3.4 × 10³⁸&lt;/td&gt;
&lt;td&gt;Token balances, TigerBeetle-style ledgers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;rust_decimal::Decimal&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Yes, to 28 digits&lt;/td&gt;
&lt;td&gt;16 bytes&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;±79,228,162,514,264,337,593,543,950,335&lt;/td&gt;
&lt;td&gt;Rates, fees, tax, FX, API amounts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;bigdecimal::BigDecimal&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Yes, unbounded&lt;/td&gt;
&lt;td&gt;40 bytes + digits&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Memory&lt;/td&gt;
&lt;td&gt;Boundaries where inputs can exceed 28 digits&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;code&gt;f64&lt;/code&gt; fails the first test anyone runs. Adding &lt;code&gt;0.1&lt;/code&gt; ten times gives &lt;code&gt;0.9999999999999999&lt;/code&gt;, and &lt;code&gt;0.1 + 0.2 == 0.3&lt;/code&gt; is &lt;code&gt;false&lt;/code&gt;. Both decimal crates return &lt;code&gt;true&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Integer minor units are what Stripe and Adyen put on the wire, and what I used for the Postgres schema in the &lt;a href="https://dev.to/news/2026-09-20-tigerbeetle-vs-postgres-payment-ledger-guide"&gt;TigerBeetle vs Postgres ledger guide&lt;/a&gt;. An &lt;code&gt;i64&lt;/code&gt; holds 92,233,720,368,547,758.07 when the unit is pence. No fiat ledger gets close. The same &lt;code&gt;i64&lt;/code&gt; holds 9.223372036854775807 ETH when the unit is wei. That gap between fiat and 18-decimal tokens shapes most of what follows.&lt;/p&gt;

&lt;h2&gt;
  
  
  rust_decimal vs bigdecimal vs fastnum in 2026: Which Crate?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;rust_decimal 1.43.0&lt;/th&gt;
&lt;th&gt;bigdecimal 0.4.11&lt;/th&gt;
&lt;th&gt;fastnum 0.7.5&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Representation&lt;/td&gt;
&lt;td&gt;96-bit integer, scale 0 to 28, sign bit&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;BigInt&lt;/code&gt; plus &lt;code&gt;i64&lt;/code&gt; scale&lt;/td&gt;
&lt;td&gt;Fixed N-bit coefficient plus 64-bit control block&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Significant digits&lt;/td&gt;
&lt;td&gt;28 (29 in some cases)&lt;/td&gt;
&lt;td&gt;Unbounded&lt;/td&gt;
&lt;td&gt;19 (D64), 38 (D128), 77 (D256), 154 (D512)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;Copy&lt;/code&gt;, no heap&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;No (&lt;code&gt;Clone&lt;/code&gt;, heap digits)&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Default rounding&lt;/td&gt;
&lt;td&gt;Half-even&lt;/td&gt;
&lt;td&gt;Half-even for &lt;code&gt;round&lt;/code&gt;, truncation for &lt;code&gt;with_scale&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Half-up&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;NaN and Infinity&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;serde default&lt;/td&gt;
&lt;td&gt;String out; string or number in&lt;/td&gt;
&lt;td&gt;String out; string or number in&lt;/td&gt;
&lt;td&gt;String out; string only in&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Postgres support&lt;/td&gt;
&lt;td&gt;sqlx, Diesel, tokio-postgres&lt;/td&gt;
&lt;td&gt;sqlx, Diesel&lt;/td&gt;
&lt;td&gt;sqlx, Diesel, tokio-postgres&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Total downloads (3 Nov 2026)&lt;/td&gt;
&lt;td&gt;169.1M&lt;/td&gt;
&lt;td&gt;139.5M&lt;/td&gt;
&lt;td&gt;10.6M&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Latest release&lt;/td&gt;
&lt;td&gt;2 Sep 2026&lt;/td&gt;
&lt;td&gt;28 Sep 2026&lt;/td&gt;
&lt;td&gt;11 Jun 2026, pre-1.0&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-11-03-rust-decimal-vs-bigdecimal-money-in-rust" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>paymentinfrastructure</category>
    </item>
    <item>
      <title>Visa VAMP Thresholds in 2026 vs Mastercard ECP</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Mon, 02 Nov 2026 08:42:34 +0000</pubDate>
      <link>https://dev.to/tomwangcn/visa-vamp-thresholds-in-2026-vs-mastercard-ecp-g3l</link>
      <guid>https://dev.to/tomwangcn/visa-vamp-thresholds-in-2026-vs-mastercard-ecp-g3l</guid>
      <description>&lt;p&gt;A fraudulent order that turns into a chargeback counts twice against your Visa VAMP ratio: once for the issuer's TC40 fraud report and once for the TC15 dispute. Since 1 April 2026 the Excessive line for merchants in Europe, the US, Canada and Asia Pacific has been 150 basis points, and a merchant over it pays USD 8 per counted event.&lt;/p&gt;

&lt;p&gt;Some pages ranking for "VAMP ratio" still quote Visa's October 2024 draft: acquirer levels of 30 and 50 bps, a merchant threshold falling to 90 bps, a 1,000-event floor and USD 10 fees. Visa replaced all of that in May 2025. At least one widely read guide also defines the TC15 side as "non-fraud disputes", which was true under the old programme and is wrong now. The figures below come from Visa's VAMP fact sheet, the Visa Core Rules edition of 24 October 2026, and acquirer and PSP documentation from Stripe, Adyen, Checkout.com and Antom, all checked on 2 November 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is Visa VAMP and What Did It Replace?
&lt;/h2&gt;

&lt;p&gt;The Visa Acquirer Monitoring Program launched on 1 April 2025. It replaced the Visa Dispute Monitoring Program (VDMP) and the Visa Fraud Monitoring Program (VFMP), which tracked disputes and fraud separately with different thresholds. VAMP folds both into one ratio and, as the name says, aims it at the acquirer first. Visa identifies and bills the acquirer, and the acquirer decides how much to pass down to you.&lt;/p&gt;

&lt;p&gt;The rollout came in stages:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Date&lt;/th&gt;
&lt;th&gt;Change&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1 April 2025&lt;/td&gt;
&lt;td&gt;VAMP launches, VDMP and VFMP retired&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1 June 2025&lt;/td&gt;
&lt;td&gt;Thresholds apply; acquirers notified of breaches&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;30 September 2025&lt;/td&gt;
&lt;td&gt;Advisory period ends&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1 October 2025&lt;/td&gt;
&lt;td&gt;Fees start&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1 January 2026&lt;/td&gt;
&lt;td&gt;Acquirer "Above Standard" tier starts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1 April 2026&lt;/td&gt;
&lt;td&gt;Merchant Excessive threshold cut from 220 to 150 bps (pushed back from 1 January)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The detailed thresholds and fee tables live in the Visa Acquirer Monitoring Program Guide, which is not public (Core Rules ID# 0029286). Everything public is the May 2025 fact sheet plus what acquirers and PSPs have chosen to publish, which is why the secondary pages disagree so much.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Is the VAMP Ratio Calculated?
&lt;/h2&gt;

&lt;p&gt;Visa's formula, from the fact sheet:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;VAMP ratio = count(TC40 fraud reports + TC15 disputes)
             / count(TC05 settled transactions)

scope: card-not-present only, domestic and cross-border
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-11-02-visa-vamp-thresholds-vs-mastercard-ecp-guide" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>paymentinfrastructure</category>
    </item>
    <item>
      <title>Circle Gateway vs CCTP: Unified USDC Balance Guide</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Sat, 31 Oct 2026 08:26:08 +0000</pubDate>
      <link>https://dev.to/tomwangcn/circle-gateway-vs-cctp-unified-usdc-balance-guide-ba2</link>
      <guid>https://dev.to/tomwangcn/circle-gateway-vs-cctp-unified-usdc-balance-guide-ba2</guid>
      <description>&lt;p&gt;Circle Gateway can mint USDC on another chain in under half a second, but only after your deposit has sat through 13 to 19 minutes of Ethereum finality. Getting that deposit back without Circle's API takes about a week, and the two functions that do it stop working whenever Circle pauses the contract.&lt;/p&gt;

&lt;p&gt;None of that makes Gateway a bad product, just a different one from CCTP, and the pages ranking for "Circle Gateway" don't explain how. They are Circle's own docs, launch coverage that stops at "under 500 ms", and one competitor's comparison that lists CCTP's latency as Gateway's. None prices a transfer. The figures below come from Circle's docs, the contracts on GitHub, live calls to the Gateway API and on-chain reads of the wallet contracts on 31 October 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is Circle Gateway?
&lt;/h2&gt;

&lt;p&gt;Gateway gives a wallet address one USDC balance spread across several chains. You deposit USDC into a &lt;code&gt;GatewayWallet&lt;/code&gt; contract on any supported chain. Circle's off-chain ledger credits your unified balance once the deposit finalises, and from then on you can mint that value on any other supported chain by signing a message.&lt;/p&gt;

&lt;p&gt;It went live on mainnet on 19 August 2025 on seven chains. It now covers 13 domains: Ethereum, Avalanche, OP, Arbitrum, Solana, Base, Polygon PoS, Unichain, Sonic, World Chain, Sei, HyperEVM and Arc. Solana arrived on 14 January 2026 and Arc on 16 September 2026. EURC (on six chains) and cirBTC (on Ethereum and Arc) joined USDC on 23 October 2026.&lt;/p&gt;

&lt;p&gt;The EVM contracts share one address on every chain: &lt;code&gt;GatewayWallet&lt;/code&gt; at &lt;code&gt;0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE&lt;/code&gt; and &lt;code&gt;GatewayMinter&lt;/code&gt; at &lt;code&gt;0x2222222d7164433c4C09B0b0D809a9b52C04C205&lt;/code&gt;. Gateway reuses CCTP's domain IDs (Ethereum 0, Base 6, Arc 26) and nothing else. It has its own contracts, its own attestation signers, its own API, and its own USDC minter role. On Base, &lt;code&gt;GatewayMinter&lt;/code&gt;'s minter allowance stood at about 44.9m USDC when I read it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Does Circle Gateway Work?
&lt;/h2&gt;

&lt;p&gt;A transfer has five steps, and their order is what matters.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Deposit.&lt;/strong&gt; Call &lt;code&gt;deposit&lt;/code&gt;, &lt;code&gt;depositFor&lt;/code&gt;, &lt;code&gt;depositWithPermit&lt;/code&gt; (EIP-2612) or &lt;code&gt;depositWithAuthorization&lt;/code&gt; (EIP-3009) on the wallet contract. A plain ERC-20 &lt;code&gt;transfer&lt;/code&gt; to the contract is not credited, and Circle's docs say that USDC is lost.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign a burn intent.&lt;/strong&gt; On EVM chains this is EIP-712 typed data. On Solana it's an ed25519 signature over the byte-encoded struct behind a 16-byte prefix.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Request the transfer.&lt;/strong&gt; &lt;code&gt;POST /v1/transfer&lt;/code&gt; with an array of signed intents. The API checks the signature, fee and balance, then returns HTTP 201 with a &lt;code&gt;transferId&lt;/code&gt;, an &lt;code&gt;attestation&lt;/code&gt; and Circle's &lt;code&gt;signature&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mint.&lt;/strong&gt; Anyone can submit &lt;code&gt;gatewayMint(attestation, signature)&lt;/code&gt; on the destination chain, unless you set &lt;code&gt;destinationCaller&lt;/code&gt;, in which case only that address can. Attestations expire after 10 minutes, and an unused one is credited back to your balance.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Burn, later.&lt;/strong&gt; Circle's operator calls &lt;code&gt;gatewayBurn&lt;/code&gt; on the source chain. The contract re-verifies your signature, sends the fee to Circle and burns the rest.&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-10-31-circle-gateway-vs-cctp-unified-usdc-balance-guide" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>stablecoin</category>
      <category>usdc</category>
      <category>cryptopayments</category>
      <category>crossborder</category>
    </item>
    <item>
      <title>DCC vs Multi-Currency Pricing: Who Pays the FX?</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Fri, 30 Oct 2026 08:36:36 +0000</pubDate>
      <link>https://dev.to/tomwangcn/dcc-vs-multi-currency-pricing-who-pays-the-fx-hi9</link>
      <guid>https://dev.to/tomwangcn/dcc-vs-multi-currency-pricing-who-pays-the-fx-hi9</guid>
      <description>&lt;p&gt;If your checkout reads the card number to decide which currency to show, Visa says you are doing dynamic currency conversion, and its registration, disclosure and dispute rules apply. Pick the same currency from the shopper's IP address and it counts as multi-currency pricing, and almost none of those rules apply.&lt;/p&gt;

&lt;p&gt;The two models look the same on screen, but they move money differently. Under DCC the shopper pays a conversion mark-up and the merchant gets a cut. NatWest found one Spanish accommodation provider charging 13.4% more for paying in pounds. The pages ranking for "DCC vs MCP" are mostly acquirers selling one or the other. Most skip the scheme rule IDs, the UK legal position and the API fields involved. Rules here were checked against the Visa Core Rules (24 October 2026 edition), Mastercard's Transaction Processing Rules (10 June 2025), the UK Payment Services Regulations 2017 and PSP documentation on 30 October 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is Dynamic Currency Conversion (DCC)?
&lt;/h2&gt;

&lt;p&gt;DCC is a conversion offered at the point of sale. The terminal, ATM or checkout spots a foreign card, quotes the price in the cardholder's billing currency at the provider's own rate, and asks the cardholder to choose. If they accept, the transaction enters the network already in their currency, so the issuer has nothing to convert. Mastercard's rulebook calls it POI currency conversion and states plainly that the merchant or acquirer applies the rate.&lt;/p&gt;

&lt;p&gt;The provider's mark-up is the revenue, and the merchant shares in it. Fiserv's published US DCC terms add a 3.5% margin to the wholesale rate and credit the merchant a 0.50% "foreign currency fee" on its DCC turnover. Adyen settles the merchant the original amount plus a share of the mark-up, which shows up as a negative (credit) value in the &lt;code&gt;DCC Markup (NC)&lt;/code&gt; column of its settlement details report.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is Multi-Currency Pricing (MCP)?
&lt;/h2&gt;

&lt;p&gt;With multi-currency pricing the merchant sets prices in the shopper's currency before payment starts. Visa defines an MCP transaction as one where the merchant displays prices in currencies other than its local one, the transaction currency is one of those displayed, and no DCC takes place (ID# 0030764). The cardholder is charged in the currency they saw. The merchant's acquirer converts to the settlement currency later and charges the merchant for it.&lt;/p&gt;

&lt;p&gt;Those conversion fees are published. Stripe adds 2% on a UK account when a payment needs converting, and 1% on a US account. Shopify Payments charges 1.5% for US stores and 2% almost everywhere else, and its automatic pricing passes this to the customer as &lt;code&gt;(price × rate) × (1 + fee)&lt;/code&gt; before rounding. The merchant also carries refund FX risk. Stripe's own example: a 60 USD charge settles as 52.80 EUR at 0.88, and a refund at 0.86 debits 51.60 EUR. If the rate had moved the other way, the merchant would have lost the difference.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-10-30-dcc-vs-multi-currency-pricing-visa-mastercard-guide" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>paymentinfrastructure</category>
    </item>
    <item>
      <title>Sanctions Screening API: OFAC vs UK vs EU Lists</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Thu, 29 Oct 2026 08:55:41 +0000</pubDate>
      <link>https://dev.to/tomwangcn/sanctions-screening-api-ofac-vs-uk-vs-eu-lists-5737</link>
      <guid>https://dev.to/tomwangcn/sanctions-screening-api-ofac-vs-uk-vs-eu-lists-5737</guid>
      <description>&lt;p&gt;In August 2026 OFSI fined Citibank's London branch £4,732,830.58, and part of the case came down to three letters. The bank's screening system did not treat "PAO Sovcomflot" in its customer records as a match for "Sovcomflot" on the sanctions list, so 32 accounts stayed unrestricted and 328 transactions worth about £5.4 million went through.&lt;/p&gt;

&lt;p&gt;Most screening failures look like that: a legal-form prefix, a transliteration, a list update that arrived nearly fourteen hours late. The pages ranking for "sanctions screening API" are mostly vendor product pages that skip the official download URLs, the thresholds open-source engines ship with and the licence terms on the data. The counts below come from the OFAC, UK, EU and UN files as I downloaded and parsed them on 29 October 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Does Sanctions Screening Work in Payments?
&lt;/h2&gt;

&lt;p&gt;A screening system keeps a local copy of one or more government lists, compares names (and ideally dates of birth, passport or IMO numbers) against it, and sends anything above a score threshold to an analyst who decides whether the hit is real.&lt;/p&gt;

&lt;p&gt;Most firms screen at two points. Customer screening runs at onboarding and again whenever a list changes, because a customer who was clean on Monday can be designated on Tuesday. Payment screening checks every party in a transfer, intermediary banks and free text included, before the money moves. The hard part is the comparison: names are not identifiers, and every list writes them differently.&lt;/p&gt;

&lt;h2&gt;
  
  
  OFAC SDN List vs UK Sanctions List vs EU Consolidated List
&lt;/h2&gt;

&lt;p&gt;The four lists a UK or EU payment firm usually screens differ in size, in scope and in what counts as an entry.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;OFAC SDN&lt;/th&gt;
&lt;th&gt;UK Sanctions List&lt;/th&gt;
&lt;th&gt;EU consolidated (FSF)&lt;/th&gt;
&lt;th&gt;UN consolidated&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Entries, Oct 2026&lt;/td&gt;
&lt;td&gt;19,484&lt;/td&gt;
&lt;td&gt;6,420&lt;/td&gt;
&lt;td&gt;6,269&lt;/td&gt;
&lt;td&gt;1,007&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Individuals&lt;/td&gt;
&lt;td&gt;7,529&lt;/td&gt;
&lt;td&gt;4,070&lt;/td&gt;
&lt;td&gt;4,490&lt;/td&gt;
&lt;td&gt;733&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ships and aircraft&lt;/td&gt;
&lt;td&gt;1,568 vessels, 342 aircraft&lt;/td&gt;
&lt;td&gt;683 ships&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Formats&lt;/td&gt;
&lt;td&gt;XML, advanced XML, CSV, fixed-width, PDF&lt;/td&gt;
&lt;td&gt;XML, CSV, ODS, ODT, HTML, TXT, PDF&lt;/td&gt;
&lt;td&gt;XML, CSV, PDF&lt;/td&gt;
&lt;td&gt;XML&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Access&lt;/td&gt;
&lt;td&gt;Public, User-Agent required&lt;/td&gt;
&lt;td&gt;Public&lt;/td&gt;
&lt;td&gt;Public token in the URL&lt;/td&gt;
&lt;td&gt;Public, one-hour signed redirect&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Entry ID&lt;/td&gt;
&lt;td&gt;integer &lt;code&gt;uid&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;UniqueID&lt;/code&gt;, e.g. &lt;code&gt;RUS1653&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;logicalId&lt;/code&gt;, &lt;code&gt;euReferenceNumber&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;REFERENCE_NUMBER&lt;/code&gt;, &lt;code&gt;DATAID&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;OFAC's list is the largest because it spans 72 programmes, with 6,346 entries under Russia EO 14024 alone, and carries 1,075 digital currency addresses. Only 5,743 UK entries impose an asset freeze: 668 of the 683 ships are under shipping sanctions only. Alert on every UK entry and your payments queue fills with vessels that freeze no funds. The EU file has no ship type at all.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-10-29-sanctions-screening-api-ofac-uk-eu-lists-guide" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>paymentinfrastructure</category>
    </item>
    <item>
      <title>Merchant Category Codes (MCC): Visa vs Mastercard</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Wed, 28 Oct 2026 08:32:39 +0000</pubDate>
      <link>https://dev.to/tomwangcn/merchant-category-codes-mcc-visa-vs-mastercard-3eap</link>
      <guid>https://dev.to/tomwangcn/merchant-category-codes-mcc-visa-vs-mastercard-3eap</guid>
      <description>&lt;p&gt;MCC 5967 tells a Visa issuer that the merchant sells adult content. In Mastercard's latest public code booklet, dated April 2024, the same four digits still mean inbound telemarketing. Visa renamed the code between its April 2024 and April 2025 manuals, and this month it moved escort services into it too.&lt;/p&gt;

&lt;p&gt;The merchant category code rides on every card authorisation. It sets US interchange, decides whether a UK credit card prices the payment as a cash advance and whether a bank's gambling block fires, and can leave an acquirer owing Visa USD 100,000 a month. The pages ranking for "merchant category code" are code lists and glossaries. Most get wrong who assigns the code, and none maps it to the API fields that carry it. Rules here were checked against Visa's Merchant Data Standards Manual (October 2026), the Visa Core Rules (18 April 2026) and PSP OpenAPI specs on 28 October 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is a Merchant Category Code (MCC)?
&lt;/h2&gt;

&lt;p&gt;An MCC is a four-digit number that classifies a merchant outlet by what it mainly sells: 5411 for grocery stores, 5812 for restaurants, 4511 for airlines. It travels with every card transaction. In the authorisation request it sits in ISO 8583 data element 18 (Merchant Type). In Mastercard's clearing file it goes in DE 26 (Card Acceptor Business Code), and an invalid value gets the presentment rejected with error 0531. The ISO 20022 card messages carry it as &lt;code&gt;MrchntCtgyCd&lt;/code&gt; in cain.001, typed &lt;code&gt;ISO18245MerchantCategoryCode&lt;/code&gt; with the pattern &lt;code&gt;[0-9]{4}&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Of the few merchant fields an issuer sees on an authorisation, the MCC is the only one built for software to reason about. Fraud models, spend controls and rewards engines all lean on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who Assigns a Merchant Category Code?
&lt;/h2&gt;

&lt;p&gt;The acquirer. Not the merchant, not the card issuer and not the scheme. Visa Core Rules section 1.5.1.11 says an acquirer "must assign to a Merchant Outlet the MCC that most accurately describes its business". Mastercard Rules 5.8.1 requires the code to reflect the primary business and gives Mastercard the final word in a dispute.&lt;/p&gt;

&lt;p&gt;Public explanations drift here, including from banks. Nationwide's gambling-support page says gambling companies assign their own codes. A Financial Ombudsman decision describes the code as applied by the merchant. Santander's cashback terms say Mastercard assigns them. What actually happens: the merchant describes its business at onboarding, and the acquirer, or a payment facilitator acting for it, picks the code and answers for it.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-10-28-merchant-category-codes-mcc-visa-vs-mastercard" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>paymentinfrastructure</category>
    </item>
    <item>
      <title>CCTP V2 vs USDT0: Moving Stablecoins Cross-Chain</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Tue, 27 Oct 2026 08:23:40 +0000</pubDate>
      <link>https://dev.to/tomwangcn/cctp-v2-vs-usdt0-moving-stablecoins-cross-chain-19ik</link>
      <guid>https://dev.to/tomwangcn/cctp-v2-vs-usdt0-moving-stablecoins-cross-chain-19ik</guid>
      <description>&lt;p&gt;Circle starts cutting CCTP V1 burn limits on 31 October 2026 and pauses the V1 contracts on 1 December. From then on, any integration still calling V1 stops moving USDC between chains. Some explainers that still rank give a July date, and one of the most complete third-party guides has the finality thresholds the wrong way round.&lt;/p&gt;

&lt;p&gt;CCTP V2 is the replacement, and it changes more than contract addresses. Nonces are assigned off-chain, a transfer can settle before finality if you pay for it, and the burn message can carry hook data that CCTP never executes. On 27 October 2026 I pulled every route's fee from Circle's API and decoded three hours of live burns on Base. The numbers below come from that, followed by a comparison with USDT0, Chainlink CCIP and Wormhole NTT.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is CCTP V2 and How Is It Different From V1?
&lt;/h2&gt;

&lt;p&gt;CCTP (Cross-Chain Transfer Protocol) burns native USDC on the source chain and mints it on the destination. There is no liquidity pool in the middle and no wrapped token at the end. Circle's attestation service, Iris, signs a message once the source chain reaches the finality you asked for, and the destination contract mints against that signature.&lt;/p&gt;

&lt;p&gt;It is less a bridge than Circle's own mint authority behind an API. The only party you trust is the one you already trust by holding USDC.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;CCTP V1&lt;/th&gt;
&lt;th&gt;CCTP V2&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Nonce&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;uint64&lt;/code&gt;, in the source-chain event&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;bytes32&lt;/code&gt;, assigned off-chain by Circle&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Finality&lt;/td&gt;
&lt;td&gt;Hard finality only&lt;/td&gt;
&lt;td&gt;Confirmed (Fast) or finalised (Standard)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Protocol fee&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;Fast 0–13 bps, Standard free&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hooks&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;depositForBurnWithHook&lt;/code&gt; carries &lt;code&gt;hookData&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Expiry&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;Fast messages get an &lt;code&gt;expirationBlock&lt;/code&gt; about 24h out&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Status&lt;/td&gt;
&lt;td&gt;Limits cut from 31 Oct 2026, paused 1 Dec 2026&lt;/td&gt;
&lt;td&gt;Current, about 30 domains&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The nonce change is the one that breaks indexers. On the source chain, V2 emits zeros where the nonce, &lt;code&gt;finalityThresholdExecuted&lt;/code&gt;, &lt;code&gt;feeExecuted&lt;/code&gt; and &lt;code&gt;expirationBlock&lt;/code&gt; will go, and Circle fills them in when it signs. The V2 &lt;code&gt;DepositForBurn&lt;/code&gt; event has no nonce at all. If your V1 reconciliation keyed transfers on a nonce read from the burn event, there is nothing left to key on. Key on source domain plus transaction hash, which is what the attestation API takes anyway, and store &lt;code&gt;eventNonce&lt;/code&gt; once Iris returns it.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-10-27-cctp-v2-vs-usdt0-cross-chain-stablecoin-guide" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>stablecoin</category>
      <category>usdc</category>
      <category>cryptopayments</category>
      <category>crossborder</category>
    </item>
    <item>
      <title>Web Bot Auth vs Visa TAP: How to Verify AI Agents</title>
      <dc:creator>Tom Wang</dc:creator>
      <pubDate>Mon, 26 Oct 2026 08:39:45 +0000</pubDate>
      <link>https://dev.to/tomwangcn/web-bot-auth-vs-visa-tap-how-to-verify-ai-agents-27d4</link>
      <guid>https://dev.to/tomwangcn/web-bot-auth-vs-visa-tap-how-to-verify-ai-agents-27d4</guid>
      <description>&lt;p&gt;Copy the signed request from Visa's Trusted Agent Protocol spec into a unit test, run it through an Ed25519 verifier, and it fails. Mastercard's Agent Pay example fails too. Both reuse a signature from an IETF test vector that signs a different message, and both set a 60-minute validity window that breaks the 8-minute limit each network tells merchants to enforce.&lt;/p&gt;

&lt;p&gt;Web Bot Auth, Visa TAP and Mastercard Agent Pay are how an AI agent proves who it is to a merchant's website in 2026. All three sit on RFC 9421 HTTP Message Signatures, and they disagree on tags, windows, nonces and the syntax of a single header. This guide shows a real signed request, the signature base a verifier rebuilds, and verification code that copes with all three.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is Web Bot Auth?
&lt;/h2&gt;

&lt;p&gt;Web Bot Auth gives bots and AI agents a cryptographic identity at the HTTP layer. The agent operator signs each request with a private key and publishes the public key in a directory. The site verifies the signature and knows which operator sent it, with no shared secret and no change to TLS.&lt;/p&gt;

&lt;p&gt;It is still a draft. The IETF chartered the webbotauth working group on 23 October 2025, and its only adopted document is &lt;code&gt;draft-ietf-webbotauth-httpsig-protocol-00&lt;/code&gt;, published 1 September 2026 by authors from Cloudflare and Google. Adoption was contested: the poll at IETF 126 came out 22 yes, 6 no, 5 no opinion.&lt;/p&gt;

&lt;p&gt;Deployment has run ahead of the standard anyway. Cloudflare, Akamai, AWS WAF, Vercel and HUMAN verify signatures; ChatGPT's cloud browser, Google-Agent and AWS AgentCore Browser send them. On 23 October 2026 IANA registered &lt;code&gt;ml-dsa-44&lt;/code&gt;, &lt;code&gt;ml-dsa-65&lt;/code&gt; and &lt;code&gt;ml-dsa-87&lt;/code&gt; for HTTP Message Signatures, though Cloudflare and AWS WAF still accept Ed25519 only.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Does Web Bot Auth Work? A Signed Request, Line by Line
&lt;/h2&gt;

&lt;p&gt;These headers are the current draft's own example (Appendix E.2.1), with line wrapping removed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;Signature-Agent: agent2="https://signature-agent.test"
Signature-Input: sig2=("@authority" "signature-agent";key="agent2");created=1735689600;keyid="poqkLGiymh_W0uP6PZFw-dvez3QJT5SolqXBCW38r0U";alg="ed25519";expires=4889289600;nonce="n9p433xm+NJ3ph3upfBIGmsuwHw387YV7Q/F+6BSpGCVjYCqQw6rznNA8PVVLySrAWsv0hQtFioQb6E1YsauiA==";tag="web-bot-auth"
Signature: sig2=:RdNFx5Bj6au3YgAMQL/RzmUlZE8QZLIaXGRpw985hWnwPfMxT228NMk6ehRS1PSl4e8PhbNZACSanGdhEwYCCg==:
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The verifier does not check the headers directly. It rebuilds a &lt;strong&gt;signature base&lt;/strong&gt;, one line per covered component, with &lt;code&gt;@signature-params&lt;/code&gt; required as the last line:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;"@authority": example.com
"signature-agent";key="agent2": "https://signature-agent.test"
"@signature-params": ("@authority" "signature-agent";key="agent2");created=1735689600;keyid="poqkLGiymh_W0uP6PZFw-dvez3QJT5SolqXBCW38r0U";alg="ed25519";expires=4889289600;nonce="n9p433xm+NJ3ph3upfBIGmsuwHw387YV7Q/F+6BSpGCVjYCqQw6rznNA8PVVLySrAWsv0hQtFioQb6E1YsauiA==";tag="web-bot-auth"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Those bytes verify against the RFC 9421 Appendix B.1.4 Ed25519 test key. I checked. The key is public, so the vector is for tests only.&lt;/p&gt;

&lt;p&gt;What the draft requires of a signer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Coverage&lt;/strong&gt;: at least one of &lt;code&gt;@authority&lt;/code&gt; or &lt;code&gt;@target-uri&lt;/code&gt;, plus the &lt;code&gt;Signature-Agent&lt;/code&gt; member that belongs to this signature.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Parameters&lt;/strong&gt;: &lt;code&gt;created&lt;/code&gt;, &lt;code&gt;expires&lt;/code&gt;, a &lt;code&gt;keyid&lt;/code&gt; that "MUST be a base64url JWK SHA-256 Thumbprint", and &lt;code&gt;tag&lt;/code&gt; set to &lt;code&gt;web-bot-auth&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Expiry&lt;/strong&gt;: "RECOMMENDED that expiry be no more than 24 hours".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nonce&lt;/strong&gt;: no requirement. Earlier versions asked for a unique 64-byte nonce; the WG draft dropped it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Algorithms&lt;/strong&gt;: anything registered except shared-secret HMAC, which is banned.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keys&lt;/strong&gt;: a JWKS at &lt;code&gt;/.well-known/http-message-signatures-directory&lt;/code&gt;, media type &lt;code&gt;application/http-message-signatures-directory+json&lt;/code&gt;, HTTPS only. Failed lookups may be cached for at most five minutes. There is no revocation.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;strong&gt;&lt;a href="https://tomcn.uk/news/2026-10-26-web-bot-auth-vs-visa-tap-mastercard-agent-pay" rel="noopener noreferrer"&gt;Read the full article on tomcn.uk →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  About the Author
&lt;/h3&gt;

&lt;p&gt;I'm &lt;strong&gt;Tom Wang&lt;/strong&gt;, an AI Developer &amp;amp; Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Currently open to new opportunities&lt;/strong&gt; in fintech, crypto payments, and AI agent engineering.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tomcn.uk" rel="noopener noreferrer"&gt;Portfolio&lt;/a&gt; | &lt;a href="https://www.linkedin.com/in/tomwangcn/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; | &lt;a href="https://github.com/tomwangcn" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; | &lt;a href="mailto:hi@tomcn.uk"&gt;Email&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>fintech</category>
      <category>payments</category>
      <category>paymentdeveloper</category>
      <category>aiagents</category>
    </item>
  </channel>
</rss>
