The Paygate and BillSplit examples are fictional, intended to show what the flow looks like. But there are two apps which have already integrated LexeConnect for real:
Zaptrain: https://zaptrain.com - a payment gateway where merchants hand over receive-only credentials to their Lexe wallet. Indeed, this is easier than BTCPay Server because merchants don't have to host their own checkout pages - Zaptrain does it for them. cc @zaptrain
Zaprite P2P: https://zapritep2p.com/ - a peer-to-peer payments app where users can request payments from contacts, and connect their Lexe wallet in one tap. @zaprite
I agree the BillSplit example is a bit contrived, but one thing I've very excited about is subscriptions and pay-as-you-go. Once we have budgets built, you'll be able to share your credentials to a website similar to OpenRouter, which has a spending limit of say $10 a month, and have it draw from your Lexe balance as you consume inference tokens. Basically, any form of pull payment is possible with LexeConnect. You can think of Lexe's client credentials like a credit card with a spending limit attached.
The Paygate and BillSplit examples are fictional, intended to show what the flow looks like. But there are two apps which have already integrated LexeConnect for real:
I agree the BillSplit example is a bit contrived, but one thing I've very excited about is subscriptions and pay-as-you-go. Once we have budgets built, you'll be able to share your credentials to a website similar to OpenRouter, which has a spending limit of say $10 a month, and have it draw from your Lexe balance as you consume inference tokens. Basically, any form of pull payment is possible with LexeConnect. You can think of Lexe's client credentials like a credit card with a spending limit attached.