The TSPβs F Fund was supposed to offer a little more return in exchange for a little more risk

Β© Getty Images/iStockphoto/designer491

Β© Getty Images/iStockphoto/designer491

Β© AP Photo/Ringo H.W. Chiu

Β© Federal News Network
MoonPay has launched PayBox, a payment tool designed to let crypto transactions happen directly inside Grok AI chatbot workflows.
It is a neat little glimpse of where consumer crypto may be heading. Not another standalone wallet app. Not another checkout page buried three clicks away. The idea is much simpler: let users move from chat to transaction inside the same flow.
That does not mean MoonPay has suddenly turned Grok into a crypto exchange, and it should not be treated as an official xAI partnership unless MoonPay says that directly. But it does show how payment companies are starting to think about AI interfaces as the next place where users may actually spend, send, or move digital assets.
For more details, visit the official Moonpay platform.
For years, crypto payments have had a usability problem.
The technology may work, but the experience often asks too much of normal users. Open a wallet. Copy an address. Switch apps. Confirm the network. Check fees. Hope the transaction went where it was supposed to go.
That is fine for crypto-native users. It is less appealing for everyone else.
Chat-based payments try to hide some of that friction. If a user is already asking an AI assistant to help with a task, there is a natural next step where the assistant can also help complete the payment.
That is where PayBox becomes interesting.
It suggests MoonPay sees crypto not just as something users access through exchanges, but as something that can sit inside broader digital workflows.
Grok gives the launch a bigger consumer-facing hook.
AI chatbots are becoming places where users search, plan, shop, code, write, and make decisions. If payments can happen inside that same interface, the chatbot becomes more than a conversation tool. It starts to look like a transaction layer.
That is a big idea, even if the actual product is still early.
Crypto companies want to be close to where users already are. AI chat is one of those places. So a tool that brings crypto payments into chatbot workflows fits the direction of travel.
The question is whether people will actually use it.
This is where the language needs care.
PayBox is a utility product. It is not proof that AI chatbots are about to replace wallets. It is not proof that Grok users will suddenly start making crypto payments at scale. It is not a sweeping signal that every AI platform is becoming a crypto platform.
It is a product release that shows a possible new interface.
That is enough.
The more interesting story is not hype. It is distribution. If crypto payments are going to become more normal, they probably need to show up inside tools people already use.
Crypto has spent years building infrastructure.
Now the harder challenge is experience. Stablecoins, wallets, payment processors, on-ramps, and compliance tools have improved, but users still need simple ways to interact with all of it.
AI assistants could help with that.
They can guide users through actions, explain what is happening, reduce confusion, and turn complicated flows into plain-language steps. But they also create risks around mistaken prompts, spoofing, approvals, and user consent.
So the opportunity is real, but so is the need for guardrails.
MoonPayβs PayBox launch is another sign that crypto payments are looking beyond the exchange screen.
The next wave may be less about making users visit crypto-specific apps and more about embedding crypto actions into everyday digital environments. Chatbots are one of the more obvious places to try that.
For now, PayBox is an early product signal.
If it works, it could make crypto payments feel less like a separate task and more like something that happens naturally inside the tools people are already using.
That is the part worth watching.
This article draws on MoonPayβs PayBox product announcement.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Moonpay. at Moonpay


Β© Getty Images/iStockphoto/ivandan

Β© (AP Photo/Elise Amendola, File)

Β© Getty Images/Techa Tungateja

Β© The Associated Press

Β© The Associated Press

Β© Getty Images/iStockphoto/Ben185

Β© Getty Images/Dilok Klaisataporn
Apple Pay may be getting ready to launch in Pakistan for the first time, according to a new report citing code found in the iOS 27 beta.
The post Apple Pay May Be Coming To Pakistan Soon first appeared on Redmond Pie.
BTCPay Server has released version 2.4.2 to patch a critical vulnerability that allowed unauthenticated remote access to LND credential files, after attackers used the issue to drain merchant Lightning wallets.
The projectβs release notes describe a serious bug involving .macaroon files, which are used by LND to manage access permissions. In plain English, those files can act like keys. If an attacker gets hold of the wrong one, they may be able to interact with a Lightning node in ways the operator never intended.
BTCPay supporters have also backed a recovery bounty equal to 10% of returned funds, capped at 3 BTC. At current prices, that puts the maximum reward around $190,000.
This is not a Bitcoin protocol exploit. It is not a native on-chain wallet failure. It is a server-side security issue affecting certain BTCPay Server setups using LND.
That distinction matters.
For more details, visit the official Github platform.
BTCPay Server is popular because it lets merchants accept Bitcoin payments without relying on a centralized payment processor.
That self-sovereign model is powerful, but it also means server security matters. When a merchant runs their own payment infrastructure, they are also responsible for keeping that infrastructure updated and properly configured.
The vulnerability patched in v2.4.2 is serious because LND macaroons can grant access to node functions. Depending on the permissions attached, an exposed macaroon can be extremely sensitive.
For Lightning operators, credential security is as important as private-key security in practical terms. A wallet can be technically sound, but if a server leaks access credentials, funds can still be at risk.
It is easy for infrastructure exploits to get misread.
When people hear that Bitcoin payment servers were drained, they may assume something broke in Bitcoin. That is not what this story shows.
Bitcoinβs base protocol was not exploited. The issue involved BTCPay Server deployments using LND and the exposure of credential files. That makes it an application and infrastructure security event, not a failure of Bitcoin consensus or the Bitcoin blockchain.
That does not make it minor.
For affected merchants, the difference may not feel comforting. Lost Lightning funds are still lost funds. But accurate framing matters because the remedy is different. Bitcoin does not need a protocol patch for this. BTCPay Server operators need to update, check configuration, and secure node credentials.
Lightning is designed for faster, cheaper Bitcoin payments, but it introduces operational complexity.
Node operators deal with channels, liquidity, backups, remote access, routing, credentials, and server exposure. That creates a different security model from holding BTC in cold storage.
A merchant running Lightning infrastructure is not simply holding Bitcoin. They are running live payment software connected to the internet.
That can be safe when managed properly, but it requires discipline. Updates matter. Permissions matter. Credential storage matters. Monitoring matters.
The BTCPay incident is a reminder that self-hosted payment systems are not βset and forgetβ products.
The recovery bounty adds another layer to the story.
Offering 10% of returned funds, capped at 3 BTC, is an attempt to create an incentive for recovery or information. That may help if attackers, intermediaries, or people with knowledge of the funds decide cooperation is better than continued exposure.
Bounties do not guarantee recovery.
They can, however, create a channel for negotiation or disclosure. Crypto projects often use them after exploits because stolen funds can be traceable, exchange deposits can be monitored, and attackers may face difficulty cashing out cleanly.
For affected merchants, the bounty is not a complete solution. The more immediate step is making sure vulnerable systems are patched.
The practical lesson is simple: update BTCPay Server and review LND exposure.
Operators should not assume that because a system has worked for years, it is safe indefinitely. Payment infrastructure lives in a changing threat environment. Attackers look for old versions, misconfigurations, leaked credentials, weak permissions, and internet-exposed services.
BTCPay Server remains an important tool for Bitcoin merchants, but self-custody and self-hosting come with responsibilities.
Version 2.4.2 is the fix point for this issue. Anyone running affected setups should treat the update as urgent.
Bitcoin payments can be sovereign, but sovereignty includes maintenance.
This article is based on BTCPay Serverβs v2.4.2 release materials and the projectβs recovery-bounty details.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Github. at Github

Bitcoin Magazine
![]()
BTCPay Server Offers a 3 Bitcoin Bounty for Recovery of Stolen Funds After Wallet Exploit
Supporters of BTCPay Server have committed to funding a bounty of up to three Bitcoins for the recovery of funds stolen through a recently disclosed vulnerability in the open-source bitcoin payment processor, the project said in a statement.
The bounty is set at 10 percent of whatever is recovered, capped at three coins in the event of a full recovery.Β
The project even extended the offer to the attacker directly alongside anyone else holding actionable information, directing them to a dedicated security address and offering Signal or other encrypted channels on request.Β
Hackers last week managed to extract Lightning Network admin macaroon credentials from affected BTCPay Server instances. The project published technical details and remediation guidance in a separate security advisory.
βTo the users who lost funds: we are sorry,β the project said in a statement. βWe will examine our mistakes, but regret alone will not help affected users or secure the project. There is no time to waste. We have to learn, improve, and act quickly.β
The BTCPay Server Foundation said it would donate 0.21 Bitcoins to Sparrow Wallet developer Craig Raw and a further 0.21 Bitcoins to the Bitcoin Red Team fund in recognition of their responsible disclosure of the vulnerability.
Separately, the project said it has been contacted by security teams at exchanges, blockchain analytics firms and law enforcement agencies offering assistance in tracking the stolen coins.Β
Affected users who have not yet come forward are being asked to share on-chain addresses and transaction details, and to file reports with local authorities and any exchange or service where the funds surface.Β
Individual reports, the project said, help preserve records and establish a chain of evidence that improves the odds of funds being frozen.
The project added that improving AI models are making it faster and cheaper to comb large codebases for weaknesses, shifting the balance toward attackers, and that Bitcoin projects are feeling it first because they are unusually valuable targets.
This post BTCPay Server Offers a 3 Bitcoin Bounty for Recovery of Stolen Funds After Wallet Exploit first appeared on Bitcoin Magazine and is written by Mathew Di Salvo.

X has launched its X Money feature, including Apple Pay support. The feature was previously only available on an invitation-only basis. But it's now available to users across the United States.
The post X Money Launches With Apple Pay Support first appeared on Redmond Pie.