@theo I think the biggest reason for still needing to read the code is the human to begin with, not providing enough information about the goal and existing foundations. If the AI’s can fill these gaps to get a better understanding than the human, then we wont need to check the code.
@AzianMike Genuine question: What information are you using to determine it's fraudulent after you get these? I get these, but find there's little to no information as to why it thinks it's fraudulent, and sometimes they arrive after the chargebacks already happened.
@levelsio This is worth making for sure, but I have a feeling the card companies don't even review the information submitted and the outcome is solely based on their own internal data such as whether 2FA was used when purchasing, customer loyalty, internal margins and reversal quotas etc
I fully believe card providers don’t even investigate the evidence. It’s not in their interest to side with the seller, they don’t want to lose their customer. The card provider loses nothing, Stripe loses nothing, the customer loses nothing, and the seller loses because they have 0 power.
Next stage: agents discover via llms.txt → test with short-lived key → pay per real call or subscribe to plan autonomously via @stripe machine payments.
@jeff_weinstein is this open to the public yet?
Just shipped autonomous API key generation for AI agents on https://t.co/J57trojI6i! 🤖
An agent discovers everything via llms.txt first → requests a key → gets a short-lived one instantly → and starts testing the VAT validation API, rates & more in seconds.
Zero account. Zero signup. Zero human in the loop.
Try prompting your agent: https://t.co/XfOhsY8E3T
Who's making their API agent-native like this?
#AIAgents #API #DevTools
It's needing the control over the checkout experience for more complex ecommerce. Hosted and Embedded Checkout is great for simple purchases and subscriptions, but if you need discount codes, credit usage, account actions, etc, on the checkout page then Elements is needed. If Elements gave the MoR features, then it would be a huge game changer.
What would be useful with @stripe support is to tick a box to say “I am a developer. The issue is highly technical.” So it can be passed to someone with development experience and not have to go through a week of irrelevant responses until it’s passed up the chain. @jrfarr
It’s just frustrating how every time I contact about a bug or a complex dev question, I have to go through days of back and forth emails where the issue isn’t being listened to and irrelevant answers to wrong topics are given, until finally it’s passed on to the engineering team who understand the issue where they’ll address it with “yes its a bug” or “we can do x, y, z to fix this for you”, which is all I’m after. But every single time I get in touch I have to go through the same wasted exchanges for days.
@marclou@jrfarr@AzianMike@jeff_weinstein Only if you have a big following, otherwise you get “we’ll pass your feedback on to our engineering team” and it’ll never be looked at again
People seem to forget that what you see on a webpage in a browser is just HTML. Want something to change on the page? You just change the HTML with some javascript. You can do that with jQuery or you use more complex state managing methods like React, but you’re still just changing the HTML on a page.