Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Machine Payments Protocol (MPP)

stripe.com

Post reply on HN
Print view View original

51–60 of 116 posts

Re: Machine Payments Protocol (MPP)

#51

Post by devmor »

neya wrote: post #29

I feel like the word "protocol", is just abused like it is a glorified marketing term. Kind of like how the word "hacker" was abused in everything else that had nothing to do with hacking. MCP was just a glorified way of tool calling but generated so much hype (and it eventually died down). Now we have MPP. Which again - could have just been another tool call exposed to the agent. Imagine you hire someone who claimed…

I've been thinking this, but never really put it into words.

Every time I see one of these I think "You are just describing an API".

Re: Machine Payments Protocol (MPP)

#54

Post by david_shi »

lihorne wrote: post #35
david_shi wrote: post #4

It seems like this is designed for atomic purchases, could it be extended for subscriptions?

Hey, I'm one of the developers at Tempo. We're working on an extension type for subscriptions to propose being added to the spec as well! We're starting with the simple types, but subscriptions are a natural extension. The subscription intent will work similarly to a one-time charge—the server returns a 402 with intent="subscription", and the client signs a recurring authorization.

Cool, would be nice to get specifics on how payments are processed, failures, and cancellations re: the recurring model.

Re: Machine Payments Protocol (MPP)

#55

Post by pear01 »

pertsix wrote: post #50
Xirdus wrote: post #45

Earlier quoted context omitted.

This one is even worse IMO > Servers MAY return 402 when: > * Offering optional paid features or premium content This implies that a successful GET request to a resource that user already does have access to, might still return 402 instead of 200. This makes 402 basically unworkable.

An RFC is a request for comments, contributions. Are you open to contributing to this RFC?

Was it AI generated? If so, should I just delegate my AI to do so?

Re: Machine Payments Protocol (MPP)

#56

Post by leptons »

ezekg wrote: post #23
codeulike wrote: post #5

You're absolutely right! I should have sent $5.00 for that transaction and not $500,000. I will generate a letter for you to print and sign and send to your bank to notify them of my mistake. Would you like me to generate a bankruptcy filing for you as well?

LLMs rarely admit fault, you gotta shift blame onto the user: > You're absolutely right! The transaction was submitted as $500,000 instead of $5.00. Since that's what was entered on your end, you'll need to contact your bank to resolve it. I will generate a letter for you to print, sign, and send to your bank if needed. Would you like me to generate a bankruptcy filing for you as well?

Claude always says it is sorry for screwing up when I point out that it screwed up.

Re: Machine Payments Protocol (MPP)

#57

Post by leptons »

codeulike wrote: post #5

You're absolutely right! I should have sent $5.00 for that transaction and not $500,000. I will generate a letter for you to print and sign and send to your bank to notify them of my mistake. Would you like me to generate a bankruptcy filing for you as well?

This is the funniest (but seriously not funny at all) thing I've seen on the internet since the start of the whole "AI" craze. And it's all too true.

Re: Machine Payments Protocol (MPP)

#58

Post by giovannibonetti »

For those of you in Brazil, my company jota.ai has built a financial AI-assistant that you can chat with to open a bank account, connect with accounts from other banks, make instant Pix payments with any of them, all of that through WhatsApp right now. We're working hard to release long-running agents soon that can do increasingly complex workflows involving payments and whatnot.

Please let us know if you have suggestions of what complex workflows you would like to build.

Re: Machine Payments Protocol (MPP)

#59

Post by pythonaut_16 »

XzAeRosho wrote: post #32
seanmcau wrote: post #22

Earlier quoted context omitted.

I'm probably overlooking something, but what makes the problem of being able to get from item in basket to item is shipping different from choosing which item(s) to put in the basket? In other words, if Agents are able to navigate marketplaces, shouldn't that imply they can also navigate a subset of the marketplace, the payment section? Especially given that that section is "easier: theres no need for qualitative (or…

It's not actually doing browser actions like Playwright or other browser automation tools, rather than direct API and MCP calls/actions. This is a whole new subset of API and connections that are all contained within the Agent context, no browser mocking. That's why they are creating these new protocols, so the full governance can work within the context of the Agent and its available tools. As I said, it doesn't hav…

Thanks for sharing your insights!

It seems like this workflow suffers the same problem as Alexa and Amazon dash buttons: consumers don't typically want the computer to just go buy things for them with no oversight. At least I don't.

Adding a checkout step would make this more plausible to me. "Agent, go find the most efficient dishwasher under $600" where it adds its recommendation to a cart, or even "Find me the best dishwashers under $600" where it creates a catalog page with its recommendations and an easy checkout process with whatever store is actually providing.

Re: Machine Payments Protocol (MPP)

#60

Post by fragmede »

leptons wrote: post #56
ezekg wrote: post #23

Earlier quoted context omitted.

LLMs rarely admit fault, you gotta shift blame onto the user: > You're absolutely right! The transaction was submitted as $500,000 instead of $5.00. Since that's what was entered on your end, you'll need to contact your bank to resolve it. I will generate a letter for you to print, sign, and send to your bank if needed. Would you like me to generate a bankruptcy filing for you as well?

Claude always says it is sorry for screwing up when I point out that it screwed up.

"Never apologize" into the customized instructions seems to work well for that specific issue.
Post reply on HN