The decision to work for a startup can be stressful. Everyone wants to get rich, but it is impossible to accurately predict the trajectory of any given company. One important lesson I learned: examine its capital efficiency when deciding to join a startup. https://t.co/Sn1FmS61HR
@shl@jeff_weinstein Improve the UX and fix bugs. A few after using it for 1 min:
1. Login state doesn’t persist after force quitting.
2. Support FaceID.
3. Add visual feedback to the “Continue” buttons to the sign-in flow.
4. Return status shows “received” and “still being processed” when no refund.
@GergelyOrosz@benjaminbooth I remember having a pilot slack account during the test period and also hearing about the scaling challenges. It is nice to read the full story ten years later.
@samhenrigold@stevesi Love the write up. I learned programming in a similar way. Got handed down a 486 PC with 2MB RAM and no HDD. Had two floppy disks running MSDOS and some applications. My first programming language was CONFIG.SYS and AUTOEXEC.BAT.
@dps Great work there, David! I would love to try this, but the Continue button doesn't work for me. Network traces in Chrome shows a `POST confirm-access` call with 404 response that says "Agent not found". Hope that is useful.
@Scholars_Stage One hypothesis is that Korea shared the same world view and value systems as China through Confucianism, whereas China would go to war in the north and the west since those people were not “civilized” in the Confucian sense. It is like why the US doesn’t go to war with Canada.
Always fascinated with traffic light countdown in Amap in China. Turns out it is implemented by crowdsourcing motion data. Had thought they had integration with city govs (which they do but with just a small number of cities). What is Google doing with maps all these years?
TL;DR: We built a transformer-based payments foundation model. It works.
For years, Stripe has been using machine learning models trained on discrete features (BIN, zip, payment method, etc.) to improve our products for users. And these feature-by-feature efforts have worked well: +15% conversion, -30% fraud.
But these models have limitations. We have to select (and therefore constrain) the features considered by the model. And each model requires task-specific training: for authorization, for fraud, for disputes, and so on.
Given the learning power of generalized transformer architectures, we wondered whether an LLM-style approach could work here. It wasn’t obvious that it would—payments is like language in some ways (structural patterns similar to syntax and semantics, temporally sequential) and extremely unlike language in others (fewer distinct ‘tokens’, contextual sparsity, fewer organizing principles akin to grammatical rules).
So we built a payments foundation model—a self-supervised network that learns dense, general-purpose vectors for every transaction, much like a language model embeds words. Trained on tens of billions of transactions, it distills each charge’s key signals into a single, versatile embedding.
You can think of the result as a vast distribution of payments in a high-dimensional vector space. The location of each embedding captures rich data, including how different elements relate to each other. Payments that share similarities naturally cluster together: transactions from the same card issuer are positioned closer together, those from the same bank even closer, and those sharing the same email address are nearly identical.
These rich embeddings make it significantly easier to spot nuanced, adversarial patterns of transactions; and to build more accurate classifiers based on both the features of an individual payment and its relationship to other payments in the sequence.
Take card-testing. Over the past couple of years traditional ML approaches (engineering new features, labeling emerging attack patterns, rapidly retraining our models) have reduced card testing for users on Stripe by 80%. But the most sophisticated card testers hide novel attack patterns in the volumes of the largest companies, so they’re hard to spot with these methods.
We built a classifier that ingests sequences of embeddings from the foundation model, and predicts if the traffic slice is under an attack. It leverages transformer architecture to detect subtle patterns across transaction sequences. And it does this all in real time so we can block attacks before they hit businesses.
This approach improved our detection rate for card-testing attacks on large users from 59% to 97% overnight.
This has an instant impact for our large users. But the real power of the foundation model is that these same embeddings can be applied across other tasks, like disputes or authorizations.
Perhaps even more fundamentally, it suggests that payments have semantic meaning. Just like words in a sentence, transactions possess complex sequential dependencies and latent feature interactions that simply can’t be captured by manual feature engineering.
Turns out attention was all payments needed!
The @stripe product keynote just finished!
We announced a lot of new stuff. (We actually couldn't fit everything into the keynote.) Some highlights:
• We've built and deployed the first general-purpose Payments Foundation Model. Trained on tens of billions of transactions and already leading to very large fraud reductions.
• We announced Stablecoin Financial Accounts. Businesses in 101(!) more countries can now store stablecoin balances in Stripe and use our regular fiat money movement rails around the world. The magic of stablecoins comes when they're integrated with the rest of the financial ecosystem. I think it's the biggest international launch we'll ever do -- businesses from 151 countries can now use Stripe.
• Stripe Profiles: your public identity on the Stripe network. Stripe Profiles will let you streamline invoicing and payments with other businesses on Stripe. (We’ll soon launch reservations for Stripe Profiles.)
• Stripe Verified, a new service that will help you navigate global requirements for payment processing with personalized monitoring, enhanced protections, and expert assistance.
• We're adding multicurrency support to Stripe accounts: instead of converting all balances to a single currency, we're going to make it easy to store, convert, and operate across different currencies. We want to make it possible to use Stripe as your financial home.
• Stripe Orchestration: manage multiple payment processors directly within Stripe.
• Support for many new payment methods. You can now access more than 125 global payment methods on Stripe, including stablecoins and real-time payment schemes like Pix and UPI.
• We’ve upgraded the AI models built into Optimized Checkout Suite and now use more than 100 signals to personalize the checkout in real time. A/B tests indicate that Optimized Checkout Suite increases revenue by 11.9% on average.
• Managed Payments: merchant of record is coming to Stripe! Enter new markets while we take care of global taxes, fraud prevention, dispute management, fulfillment, and more.
• A new Connect dashboard, with vastly improved visibility into what's happening across your platform.
• Radar for Connect: it’s now way easier to detect and manage fraud and compliance issues with subaccounts.
• Networked onboarding for platforms: users no longer need to re-enter their details if they’ve onboarded before.
• Smart Disputes: AI automatically responds to disputes for you. Early results show that companies win 13% more chargebacks. We also put skin in the game: we cover the fee if you lose.
• Radar now supports ACH and SEPA. This reduces fraud rates by 20% and 42% respectively.
• A bunch of usage-based billing improvements. It can now ingest up to 100,000 events every second.
• Stripe Terminal can now be used with third-party hardware, starting with Verifone.
• Klarna is coming to Link.
• Authorization Boost. AI automatically updates cards and tokens, determines optimal transaction routing across networks, and determines if and how to retry failed payments (if we’re confident that the failure was ephemeral).
• Radar risk scores are now available via the API. (I.e. they can become a feature for in-house fraud systems.)
• Stripe Tax is now available in 102 countries (up from 57 last year), and we also now automate the entire tax lifecycle (monitoring, registration, collection, filing).
• New FX Quotes API.
• Payment method sharing: if you have multiple Stripe accounts, you can now share payment details across them, saving the need to have customers re-enter their details.
• Stripe Issuing now supports consumer card programs. (Long-requested!)
• Global Payouts: pay customers, contractors, and other third parties with just an email address.
• Stripe Workflows: build, test, and execute multistep flows that orchestrate behavior across Stripe multiple products—using your data, Stripe APIs, and conditional logic.
• Stripe Scripts: a new way to extend and customize the logic in Stripe Billing. This will soon expand to cover many parts of the Stripe platform.
• Benchmarking: compare your performance to similar businesses on Stripe.
• You can now import third-party data into Stripe Capital, which enables expanded eligibility for your customers.
• A new Issuing rules engine: granular configurability over authorization decisions.
• Global Issuing via stablecoins: a simple and cohesive way to administer global card programs. Ramp is using this to massively accelerate their global expansion.
• Data in Sigma is now far faster (6 hour latency, down from 24 hours). That'll continue to get faster in the coming months. Similar data freshness improvements across other products.
• You can now use Instant Payouts to withdraw funds from Stripe to debit cards in 32 countries.
• The Dashboard AI agent: create products, process refunds, and generate payment links by just telling our little critter what to do.
Whew! I’m not sure I even covered everything. A few of the above are years in the works and could have received launch events by themselves. I’m very proud of the team. So what are the common themes?
• We’re rethinking and upgrading pretty much every part of the stack with AI. (Embedding/foundation models, agents, etc.)
• Stablecoins are enabling unprecedented global access and expansion.
• We’re making a lot of things deeply configurable that weren’t previously. (Scripts, Workflows, and more.) Ties to our goal of building truly programmable, global financial services.
Excited to share my chat with @saranormous & @eladgil
We talked about how Stripe is applying AI across our products, our journey from traditional ML to LLMs, what we are seeing across the AI ecosystem, and how AI can be applied to grow the economy: https://t.co/WI5CQbKlWA
Our internal LLM tool, built last March, allows Stripes to safely experiment with LLMs.
With 3K Stripes using the tool weekly and over 700 shared prompts, the tool is reshaping how we work and build for our users.
We shared more with @bentossell
@GergelyOrosz I think your interpretation is most likely to be correct, but I still want to give them some benefit of doubt because I don't know the exact structure. PPUs are a good one for this thought exercise. IIUC Employee PPUs can be bought back. Will the buy-back be capped at 100x?
@GergelyOrosz That is plausible, but an alternate interpretation is that the cap is on returns, and shares can be traded on secondary markets. E.g. an investor puts in $1, and later sells for $150. They keep $100, but the extra $50 goes back to OAI. "Any excess returns go to OpenAI Nonprofit."
@GergelyOrosz So they buy back investors’ shares with profits generated in the business? Can you share the source? I looked at their blog post which just says returns: https://t.co/ZDRelAcWpO
@stevesi@retornam IIRC Communicator/Lync/SfB are different branding of the same codebase. Lync was a major rebrand in O14/2010, but it was soon deprecated after the Skype acquisition. I was on the Lync team and didn’t like the Skype for Business name.
8 years after my start date at Uber, I am calling dibs on recounting the tale of DIBS, drawing inspiration from Matt Basta’s captivating piece titled No sacred masterpieces.
https://t.co/fkAPHiNew7