Soap Payments

Filip Michalsky Verified account @FilipMichalsky · 3d

Most AI software factories try to remove the human. Ours keeps one at every decision that can't be undone. 🐴

Introducing the Soap AI org at @paywithsoap: dozens of AI coding agents working as one team. They claim work and report back on one shared board. No server, no database, just a cloud bucket that costs cents a month. The first agent to claim a task gets it, and if it goes quiet, the claim lapses.

What one agent learns, every agent learns. 🧠

AI does the work. People make the calls.

#AIagents #Payments #Engineering

View quoted post on X

Filip Michalsky Verified account @FilipMichalsky · Nov 2

October at @paywithsoap 🧼

Proud to share what our team shipped in October. Here's what's new for merchants and players.

1. 𝗟𝗶𝗴𝗵𝘁𝗻𝗶𝗻𝗴 𝗽𝗮𝘆𝗺𝗲𝗻𝘁𝘀, 𝗻𝗼𝘄 𝗶𝗻 𝗦𝗼𝗮𝗽 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 ⚡
Through our integration with @voltage_cloud, your customers 𝗱𝗼𝗻'𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗼𝘄𝗻 𝗯𝗶𝘁𝗰𝗼𝗶𝗻 to pay with Lightning. Eligible Cash App customers can scan a Lightning QR code and 𝗽𝗮𝘆 𝘀𝘁𝗿𝗮𝗶𝗴𝗵𝘁 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲𝗶𝗿 𝗨𝗦𝗗 𝗯𝗮𝗹𝗮𝗻𝗰𝗲.

2. 𝗣𝗮𝘆-𝗶𝗻 𝗿𝗲𝘃𝗶𝗲𝘄𝘀
Flagged deposits don't have to be lost to an automatic decline. Merchants 𝗿𝗲𝘃𝗶𝗲𝘄 𝘁𝗵𝗲𝗺, 𝗮𝗽𝗽𝗿𝗼𝘃𝗲 𝘁𝗵𝗲 𝗹𝗲𝗴𝗶𝘁𝗶𝗺𝗮𝘁𝗲 𝗼𝗻𝗲𝘀, and the player gets an email the moment their deposit goes through.

3. 𝗡𝗲𝘄 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 𝗮𝗻𝗮𝗹𝘆𝘁𝗶𝗰𝘀
Business Metrics and Checkout Funnel views show exactly where payment activity flows and 𝘄𝗵𝗲𝗿𝗲 𝗽𝗹𝗮𝘆𝗲𝗿𝘀 𝗱𝗿𝗼𝗽 𝗼𝗳𝗳, with deposit and withdrawal filters and custom date ranges.

4. 𝗪𝗲𝗿𝘁(wert.io), 𝗻𝗼𝘄 𝗹𝗶𝘃𝗲 𝗶𝗻 𝗦𝗼𝗮𝗽 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁
𝗠𝗼𝗿𝗲 𝘄𝗮𝘆𝘀 𝘁𝗼 𝗽𝗮𝘆, inside the same embedded Soap checkout.

5. 𝗢𝗧𝗣 𝗳𝗼𝗿 𝗻𝗲𝘄 𝗽𝗮𝘆𝗼𝘂𝘁 𝗺𝗲𝘁𝗵𝗼𝗱𝘀
Every new bank account or payout method is now confirmed with a 𝗼𝗻𝗲-𝘁𝗶𝗺𝗲 𝗰𝗼𝗱𝗲. It's an extra layer of protection for players and merchants.

6. 𝗧𝗵𝗲 @paywithsoap 𝗔𝗜 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗙𝗮𝗰𝘁𝗼𝗿𝘆
This is how we ship at this pace. Because of our AI Software Factory, we merged 𝟯𝟭𝟮 𝗽𝘂𝗹𝗹 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀 in October: 𝟮𝘅 𝗦𝗲𝗽𝘁𝗲𝗺𝗯𝗲𝗿 and 𝗮𝗹𝗺𝗼𝘀𝘁 𝟲𝘅 𝗢𝗰𝘁𝗼𝗯𝗲𝗿 𝗹𝗮𝘀𝘁 𝘆𝗲𝗮𝗿.

Parallel AI engineers coordinate through a shared board, backed by automated builds, feature flags and fast rollbacks, so new capabilities reach merchants quickly and every rollout stays under control.

More on the software factory soon.

#Payments #Fintech #iGaming #Lightning #ClaudeCode

View quoted post on X

Filip Michalsky Verified account @FilipMichalsky · Oct 5

Mandi tried to deposit $16 into her favorite online game. Her ID says Amanda.

Our previous deterministic-only fraud checks blocked her account right away. For most merchants, that's the last time Mandi ever plays.

Name matching exists for a good reason: the name on the card has to match the verified player, so stolen cards don't clear. But names are messy. Nicknames, middle names, double last names, diacritics that get dropped (José vs. JOSE), suffixes like Jr., and card networks that cut long names short. A deterministic check can't tell any of that from a stranger. So every mismatch was treated as fraud, and a block was permanent.

The obvious fix is "let an LLM decide." In payments, that sentence should scare you. We were afraid of a model that approves everything to be helpful, a family member's card waved through, an unblock nobody can audit.

So at @paywithsoap we built an AI revenue recovery engine whose job is mostly to say no. It only runs after the deterministic check has already failed. It gets both names and a strict written policy, and it answers only one question: semantically the same name, or not? Only a high-confidence "yes" lifts the block. On a timeout or an error, it fails closed. Every unblock is written to the audit trail as performed by AI.

After a soft launch in production:

- 21,000+ name checks
- ~4.8% of blocked payments recovered that would otherwise have been lost
- Minimal latency, zero API errors

It refused a family member's card, the same person retrying someone else's card five times, and a street address typed into the name field. It approved "Robert Carter Jr." against "Robert Carter", a card network that cut "Abernathy" to "ABERNATH", and a Spanish double surname the card only carried half of.

It says no far more often than it says yes, and that's exactly why we trust the yeses.

Built with Claude Haiku 4.5 from @Anthropic and @OpenRouter for routing. Speed and safety weren't in tension, because the guardrails were designed before the model was invited in.

#Fintech #PaymentsInnovation #AI #FraudPrevention #LLM

View quoted post on X

Voltage ⚡ Verified account @voltage_cloud · Oct 27

AI Native Payment Orchestration companies are integrating bitcoin payments.

🚀

View quoted post on X