Basis Theory

Money20/20 is great and all but I am SO EXCITED to announce that Kelly Mayes has joined us at Basis Theory as our Chief Marketing Officer 🎉 I've long admired her work at Lightspeed and Alloy (the State of Fraud Report is something I still always look forward to) - more recently at Increase as well - so I cannot wait to see what she cooks up for us here! She will be building on an incredibly strong foundation thanks to Eryn Lueders, Peyton McGovern, Joey Aguirre, Jorge Iván Boizo, Lucca Signorelli and the rest of the BT team. We are almost ~6 years into our journey but (ugh, insert cliche here) truly just getting started. Last quarter, we added 100+ new customers which means we are compounding every single day 🚀 and are now supporting **TRILLIONS** in market cap across or platform 🤯 It's time we start talking more publicly about all of the awesome work we've been doing to drive payments innovation forward and Kelly is the perfect partner to help tell our story 🤝 I think this is that inflection point you always dream about along the way? WELCOME!!!

The new commerce era is heating up! 🔥 And consumer adoption is continuing to grow! Only 2.2% of US households are paying for AI, yet the agent competition is starting to heat up, and you're seeing them embedded directly in the same surfaces you're used to. Instinct pushed iMessage, Texting is having a renaissance, Grok is embedded in Tesla and X, Facebook's Muse is everywhere on Facebook. Today, we are sharing the platform we've been building with these Agent builders over the last 18 months! 🟢 Agentic Payments - with full support for Visa Intelligent Commerce, Mastercard Agent Pay, Stripe SPTs + Link, Stablecoins, and more 🟢 PCI Agent Runtimes - secure access to Vercel, OpenAI, Anthropic, LlamaIndex, Meta or any other model 🟢 Browser Proxy & Aperture 🟢 Agent Credential Proxy Coming soon: 🟡 Managed Auth 🟡 PCI LLM Router HUGE shoutout to Lucas Chociay, Eryn Lueders, Joey Aguirre, Radilson Gomes, Colin Luce, Basis Theory and all of the amazing partners and builders (we can mention 😉) that have built with us along the way - Crossmint, Tanner Riche, Seemal Zaman, Aditya Bhamu, Gene Reda, Angad Banga, Dan H., MoonPay, Allowance (YC P26), Alchemy ( and my bestie Flor Ronsmans De Vry), and sooo many more. No matter where you are on this journey, we want to TALK! 👏

We've been building something new Basis Theory 🚀, and the new site is live: https://basistheory.ai Agents are starting to do real work. They buy things, sign in, call APIs, and work with customer data. All of that needs a credential, and right now the easy path is putting a card number, password, or API key somewhere the agent can read it. We want agents to be able to act without ever holding the secret. That's what we're building now: a platform where agents can operate securely. The original credential stays with you, and the agent gets a scoped, revocable credential for one job, in whatever format the destination accepts. The first pieces: - Agentic Payments: an agent can pay without seeing the card https://lnkd.in/dF3ExW92 - PCI Agent Runtimes: run the agent code you already have on card data, inside a PCI Level 1 environment https://lnkd.in/d22_rgAC - Browser Proxy: your browser automation can pay at checkout without the card number ever passing through your code https://lnkd.in/dQZqedNU Coming soon: - Browser Aperture: an agent can shop a site and check out inside the limits you set - Agent Credential Proxy: an agent can call an API without holding the key Managed Auth and a PCI LLM Router are next, with more to come after that. If you're building agents and running into this, I'd love to hear how you're handling it! Happy coding! 🙂

Agentic commerce is HERE📍 Finally... And with that, I couldn't be more excited (and proud of the Basis Theory team!) to launch BT/AI (2.0) - Basis Theory, for agents One secure & compliant platform to handle everything your agent needs from calling APIs to interacting with customer data to making payments 🤖 💳 Available today: 🟢 Agentic Payments - with full support for Visa Intelligent Commerce, Mastercard Agent Pay, Stripe SPTs + Link, Stablecoins and more 🟢 PCI Agent Runtimes - secure access to Vercel, OpenAI, Anthropic, LlamaIndex, Meta or any other model 🟢 Browser Proxy & Aperture 🟢 Agent Credential Proxy Coming soon: 🟡 Managed Auth 🟡 PCI LLM Router Check it out here: https://basistheory.ai/ Shout out Lucas Chociay, James Armstead, Radilson Gomes, Eryn Lueders, Joey Aguirre and all of our partners Tanner Riche Seemal Zaman at Visa, Gene Reda Sherri Haymond at Mastercard, Jeff Weinstein at Stripe, Alchemy, Allowance (YC P26), CartAI, Crossmint, Locus (YC F25), MoonPay, Sponge (YC W26) and more!

"Integration takes 15 minutes." It's true. Fast to integrate is the floor these days. What nobody puts on a landing page is what happens after, and that's exactly where the real project begins. Vaults are here to help unlock advanced payment decisioning. Part of that unlock needs to be supporting your payment strategy on more than just a code level. An integration in 15 minutes is meaningless if you have to rip your stack out and replace it after six months because you weren't getting the support you expected. So instead of telling you how quickly you can integrate to Basis Theory or how developer-friendly we are, I want to run through a few considerations that are vault-adjacent. None of them are actually about Basis Theory. Do you want to own orchestration in-house, or use an orchestration platform? No wrong answer, and honestly a combination of the two can make sense depending on your markets. Maybe bring on a second PSP and start small with light failover logic you handle directly. For hyper-local connections and APMs, maybe look at adding an orchestrator, because you can't be bothered to connect to a Mongolian PSP as a US-based company. Do you get the data you need back? Gateways and orchestration platforms tend to normalize responses on the way back. Nothing inherently wrong with that, as long as you're getting everything you need, and that's harder to verify when you only interact with a single point. Are you building your own source of truth where you need raw data, or is normalization fine for your payment strategy? How detailed does your logic need to be? More a question of what are you actually trying to solve. Are you optimizing for auth rates or interchange? What does your failover strategy look like? How are you handling declines, whether that's 3DS as a recovery mechanism or offering an APM when a card payment fails? Do you have recurring traffic, how are you handling retries, and is that recurring volume portable between PSPs or locked into a third-party engine? What does changing your payment stack actually look like? When you use a vault, you meaningfully change the way you interact with PSPs for customer-initiated transactions. Typically you're moving from a hosted field to a server-to-server flow where the card data gets injected in transit. Do your preferred PSPs support that flow? How many other services can you run agnostic of the PSP, and do your PSPs support them, whether that's an external MPI for 3DS or an endpoint to update a stored credential so you can cascade account updates from your vault down to your PSPs? 15 minute integration. Cool. Nobody cares. The important thing is whether your vault provider is capable of having these conversations with you and providing meaningful guidance. Plenty more to consider. Drop a comment and share some knowledge.

PCI compliance has been pretty boring for most of my career. That's a feature, not a bug. I'm realizing more and more that this is absolutely NOT the experience for everyone. And apparently, some people are still answering 300+ question SAQs. 😬 I was reading through our case study with Ansa and one number jumped out at me: 95%. That's how much they reduced their PCI scope by using Basis Theory as their cardholder data environment. Their SAQ-D went from 300+ potential questions to answering just four through Basis Theory. Four. 🍀 But here's the part I actually find most interesting as a payments person... They didn't have to trade control for simplicity. One of the easiest ways to make PCI someone else's problem has always been to hand your payment credentials to a processor. And it works! Until you want another processor. Or your enterprise customers already have their own PSP relationships. Or you simply want the freedom to make a different decision later. Ansa gets the boring PCI experience while still maintaining the flexibility to work with whatever processors their customers need. That's the combination I love. ♥️ Compliance shouldn't be your payments strategy. It should be boring infrastructure that lets you get back to your payments strategy. Pretty cool example of that here 👇 https://lnkd.in/g7ctnEPc #payments #PCI #fintech