@richardturrin National rails don't need to merge for cross-border payments to improve. The hard part is the connection: FX, settlement, and who handles a failed transfer. That's what I'd watch in the Bakong-eKash trial.
@laurashin If Toss lets people send to a saved phone contact instead of a wallet address, that's the part that will actually get used. The wallet is the container. The contact book is the UX. That's already how domestic transfers work in a lot of markets.
@NikMilanovic@Plaid Detecting agent traffic is useful. I'd want to know how that signal links to the payment authorization and receipt. Can the merchant retrieve it when a payment is disputed, or does it stay in the web logs?
@jeff_weinstein The flow is clean. The part I'd still want on the receipt is who approved what: Alice's request, Bob's payment, the amount that settled. If one of the agents retries after a timeout, that record is what keeps it from turning into a dispute.
@oost_marcel Worth being precise: the Central Bank is developing offline contactless Pix, with no launch date yet. The international links are a separate, slower track. I'd watch which one actually ships first.
@TheBlockCo This is the exploratory version of a story that already has a live, narrower instance. DBS and JPMorgan turned on 24/7 USD transfers between Singapore and the US yesterday, with Ant International as the first client. Multi-currency, plus a Swift link, is the harder half.
@CoinDesk@dbsbank@jpmorgan What changed isn't the asset. It's still a bank deposit. What changed is the cutoff, for clients already on both banks' tokenized deposit accounts. That's a narrower, more useful story than "banks went 24/7 onchain."
@lemonsqueezy The date I'd worry about less is March 31. It's which subscribers actually move. Cards can migrate; PayPal can't, and some customers, including India-issued cards, have to reauthorize. If that revenue matters, start the customer email now.
@linw2949 Agreed. The approval is only half the record. You also need the amount that actually settled, and a rule for what happens if the session dies after the biometric. Otherwise the merchant and the wallet will tell two different stories.
ChatGPT Wallet is rolling out to US Pro users. Agents pay with a card token, you approve each buy biometrically, and that approval is the record.
Agent payments got a first answer. On cards.
In Brazil or Thailand a lot of checkout is Pix or QR. Who builds that step there?
@ankita080393 A portable mandate is the right object. The hard part is who has to honor it at checkout: the wallet, the acquirer, or the store. If only the agent carries it, the merchant will keep asking the customer to tap confirm anyway.
Eric Seufert's “agentic commerce is a mirage” take raises a real issue: consumer platforms may resist outside agents.
B2B has a different starting point.
Recurring supplier payments come with invoices, approval rules and deadlines. Less discovery, more execution.
DBS and JPMorgan went live Monday with 24/7 USD transfers between Singapore and the US. Weekends included.
Ant International is first, using it for treasury between entities.
It's still a bank deposit. Coming off a regular account onto Kinexys still pauses Saturday 3-6 p.m. ET.
Rwanda and Cambodia launched a trial Sunday linking eKash and Bakong. Send from Cambodia into a Rwandan bank account or wallet.
It's a proof of concept, not a live corridor yet.
Two instant-payment systems, a bank on each side. A lot of South-South links start this way now.
@achiever4L Only in Nigeria do you have to beg someone to accept money. Fair though, 10 digits and the transfer lands in seconds. The account number basically became a social handle.
@goelrishabh The card token export is the part more providers should put in the contract upfront. Most founders only find out whether their subscribers can move with them on the day they need to.
@eric_seufert Agree payments isn't the blocker. The one new piece is the record: a network token tied to an explicit approval. That helps more with disputes than with checkout. Whether retailers let agents in is still about margin and who owns the customer.
@GergelyOrosz From the merchant side, five hours of declines from one issuer looks like a fraud spike or a broken checkout. Most teams find out from support tickets. Decline-rate alerts split by issuer catch it in minutes.
@BuilderLabsAI Fair point. Pix already has the confirm step, and Pix Automático gives recurring payments a mandate. What's missing is the merchant knowing an agent started it, which is your second point.
@SherifKozman@OpenAI Signed rules checked per purchase makes sense. The question I'd ask is where the check runs. If it sits with the issuer or wallet, merchants can lean on it. If it's only inside the agent, they'll keep their own controls anyway.
@dr_andrewlaw Probably whoever sits closest to the money. For API and agent payees I'd bet on the provider tagging the payee at onboarding, the way acquirers assign MCCs today. Self-declared categories won't survive the first fraud wave.