Build with CoinStats’ all-in-one API. Learn more

Deutsch한국어日本語中文EspañolFrançaisՀայերենNederlandsРусскийItalianoPortuguêsTürkçePortfolio TrackerCryptocurrenciesPricingCrypto APIMCPIntegrationsNewsRWA MarketEarnBlogNFTWidgetsDeFi Portfolio TrackerDerivativesETF FlowsCrypto GamingPrediction Markets24h ReportPress KitAPI Docs

XRP price at $1.33, Stripe unit Privy builds wallets on the Ledger: what it means for your XRP

23m ago•
bullish:

0

bearish:

0

The XRP price stands at $1.33 on Wednesday evening, around 2.7 percent lower than 24 hours earlier. On the same day Ripple delivered what is probably the month's most tangible distribution news: Privy, a subsidiary of payment provider Stripe since last year, is bringing embedded wallets to the XRP Ledger. Developers will be able to create accounts directly inside their own app, without a user installing a separate wallet.

The news and the price tell different stories, and that is exactly what makes the day interesting. Anyone holding XRP gets a reach story in a market that is not paying for it today. This piece places both, recalculates the usage figures Ripple cites for it, and shows the two points at which the matter becomes concrete for investors in Germany.

XRP price at $1.33: where things stand on Wednesday evening

XRP trades at $1.33, around 1.20 euros. The daily high was $1.38 and the daily low $1.33. The price therefore sits at the lower edge of its own daily range, which makes the $1.33 level not just any round number but the point at which trading is fighting out the day.

Over a week XRP is down 6.9 percent, over a month 5.1 percent. Market capitalisation stands at $84.2 billion and trading turnover over the past 24 hours at $1.87 billion. The price is 63.4 percent away from its record of $3.65. All figures come from CoinGecko, as of October 14.

On Tuesday we described an additional 90 million XRP in the accounts of Upbit and Bithumb in this space, with the price at $1.36 at the time. Three cents have come off since then, around 2.2 percent. The $1.30 level named in yesterday's piece as the next support zone has not been tested so far. It has therefore held nothing yet; it simply has not had its turn.

The macro day belongs in the picture as well. US consumer prices rose to 3.7 percent on Wednesday and the core rate came in above expectations. The whole crypto market gave way in response, and Bitcoin slipped below $82,000. XRP's loss of 2.7 percent therefore falls within the market average and is not an XRP story of its own.

What Ripple and Privy announced

Privy builds what are known as embedded wallets. That means an app, say a payment service or a fintech, creates an account on a blockchain in the background, and the user notices nothing about it beyond a pay button. Stripe bought the company last year, and Privy continues to operate independently.

From now on this infrastructure also covers the XRP Ledger. Developers can create XRPL accounts through Privy and build them into their application. XRP, Ripple's stablecoin RLUSD and further assets of the network are supported. Anyone who wants to hold their own keys can export the private key. The target group is expressly payment providers and fintechs, not retail investors.

The second part of the announcement concerns AI agents. Software is to be able to pay independently in future, without a human approving every booking. The x402 protocol is intended for that. Spending limits and the app operator covering the network fees are in the works according to the two companies, but not yet generally available.

x402 is a payment standard with which a program pays for access to data or a service before it receives it. The name alludes to the HTTP status code 402, reserved for "Payment Required" since the early years of the web and until recently practically never used.

Bundle of fibre-optic cables against the light in front of the blurred run of a server aisle
Software paying software: the x402 protocol settles individual requests, often in the range of fractions of a cent.

x402: how software pays software

The mechanism is simpler than the name sounds. An AI agent queries a data source, say a weather service or a search engine. Instead of a subscription or an API key, the provider charges a micro payment for precisely that one request. The agent settles it from its own wallet, the answer comes back, and the process is complete.

For a blockchain that is attractive business, because such payments arise in large numbers and with very small amounts. The XRP Ledger settles a transaction in a few seconds and for fractions of a cent, which makes it technically suitable for the purpose. That is exactly what Ripple has been aiming at since the summer: since June there have been tools with which agents create their own accounts, check balances and pay in XRP or RLUSD. In September support for the payment standard from Stripe and Tempo was added.

The Privy connection is the distribution step that goes with it and lowers the barrier for developers who would previously have had to build their own wallet infrastructure. Whether revenue comes out of it is decided not by the technology but by how many apps actually build it in.

14.3 million transactions, around $22,000 in value

Ripple cites usage figures alongside the announcement, and they are worth a calculation of their own. J. Ayo Akinyele, head of engineering at RippleX, wrote on X of more than 13 million agent payments via x402 and put their share at around 25 percent of ledger activity. The XRPL AI Hub, operated by infrastructure developer t54, reports more than 14.3 million cumulative transactions across 169 registered merchants as of October 14.

The second figure from the same source gets considerably less attention: the cumulative value of these payments comes to around 6,991 XRP and 12,752 RLUSD. Convert that at today's price and the order of magnitude becomes clear. At $1.33, 6,991 XRP corresponds to about $9,300. RLUSD is pegged to the dollar, which makes a further $12,750 or so. Together, then, roughly $22,050.

Spread across 14.3 million transactions, that is around $0.0015 per payment, about a seventh of a cent. That is technically impressive and economically small. Anyone who reads the 25 percent figure and infers demand for XRP from it is confusing the number of bookings with their value. CoinDesk, which compiled the figures, puts it cautiously in its report of Wednesday: it remains open how much real economic activity sits behind the transactions.

On where the numbers come from: the 13 million figure and the 25 percent share come from Ripple itself and are not independently verified. The hub figures come from t54. Neither value is wrong for that reason, but both describe a system whose operator has an interest in large numbers.

The 1 XRP reserve: what every new account costs

This is where the matter becomes concrete for the first time, for investors and for developers. The XRP Ledger requires a minimum reserve for every new account, which currently stands at 1 XRP. That is how Privy's documentation puts it, and it applies regardless of whether the account later moves XRP or only the stablecoin RLUSD.

This 1 XRP is not lost, it is blocked. It stays in the account as a balance and can only be moved again once the account is deleted. At today's price that is 1.20 euros per account created.

For a payment service with a million users that means a million XRP it has to hold, around $1.33 million at today's price. That is the point at which reach would actually create demand for XRP, and it would do so regardless of how small the individual payments are. Whether the operators put up that amount themselves or pass it on to users is open; the announced fee coverage by app operators points to the first variant.

If you use an app that offers you an embedded XRPL wallet, it is therefore worth a look at the terms: who bears the reserve, and do you get it back when you close the account? An app that deducts 1 XRP from your balance and does not explain it has a transparency problem, not a technical one.

Hand holding an unbranded smartphone with a dark display up to a card terminal on a shop counter
To the user, an embedded wallet looks like an ordinary payment function in the app.

RLUSD lacks MiCA authorisation in the EU

The second concrete point concerns the stablecoin that the new wallets expressly support. RLUSD is not authorised under the MiCA regulation in the European Union. Standard Chartered has just taken over custody of the stablecoin, as we described on Wednesday in a separate piece on the $2.41 billion of RLUSD. European authorisation does not come with that, however.

In practice that means an exchange or a payment service regulated under MiCA in Germany may not offer RLUSD to retail customers without further ado. The embedded wallets can technically hold the stablecoin, but the regulatory route to the German user is missing for now. Anyone wanting to get in from Germany therefore still goes via XRP itself and via an authorised trading platform, not via Ripple's stablecoin.

For judging the announcement, that is no aside. A large part of the benefit Ripple and Privy describe hangs on RLUSD as the unit of account for agent payments. In the EU that part is currently not available.

What of the deal is already running today, and what is not

Available since June is the toolkit with which agents create accounts, query balances and pay in XRP or RLUSD. Since September, support for the Stripe and Tempo standard belongs to it. Both run independently of this week's announcement.

Newly announced is the Privy integration itself, that is, the option of embedding XRPL wallets in any app. No start date has been named for it. Not yet available are the spending limits for agents and the operator covering the network fees. Both are announced, and both are missing today.

So anyone reading that AI agents now pay on the XRP Ledger is reading something that in parts has been true since June and that, in the part which is new this week, still has no date.

Our assessment: the number of payments says little about their value

From the newsroom's point of view the Privy connection is the more valuable half of this news, and it is the half discussed least. The reason is in the calculation above: 14.3 million transactions at around $22,050 in value works out at a seventh of a cent per payment. Agent payments are therefore proof today that the technology works, and not a source of demand.

What would actually create demand is the minimum reserve of 1 XRP per account. This reserve falls due once per user, not per payment, and it stays tied up. If Privy reaches meaningful user numbers through Stripe customers, a measurable need for XRP arises from it, independently of trading volume. That is the lever worth watching.

Three things speak against it. First, no start date has been named for the Privy integration. Second, RLUSD lacks MiCA authorisation, which means part of the benefit described falls away in the EU. Third, the usage figures come from Ripple and from the hub operator themselves. Anyone deriving a price move from that today is building on three open points. The market reacted accordingly on Wednesday, namely not at all: the loss of 2.7 percent matches the market average after the inflation data.

Tax: every agent payment in XRP is a disposal

One point missing from the discussion of agent payments so far concerns German users directly. If a program pays with XRP on your behalf, that is a disposal of those coins for tax purposes, exactly like a sale. The one-year holding period under section 23 of the German Income Tax Act applies unchanged, and the threshold for private disposal transactions stands at 1,000 euros a year.

With tiny amounts that sounds theoretical. The difficulty lies not in the size but in the number: thousands of micro payments mean thousands of individual events for which the acquisition date and acquisition cost have to be established under the FIFO order. Anyone using an app with an embedded wallet should therefore clarify in advance whether it offers an export of the events. Without that export, a clean tax return is practically unachievable with many bookings. A tax tool with an XRPL connection takes the allocation off your hands, but it does not replace the export from the app.

The same thought applies to self-custody. Privy allows the export of the private key, and that is the difference between a balance held with a provider and an account that belongs to you. Anyone who cannot find the export, or is not offered one, effectively holds a claim against the app and not XRP on the blockchain. Which wallet types separate this cleanly is shown by the software wallet comparison further below.

Privy wallets on the XRP Ledger: the 1 XRP reserve remains the catch

XRP stands at $1.33, the news of the day is a distribution step without a start date, and the best number in it is not the one with the most zeros. Three steps make sense now:

  1. Check the reserve before you use an app wallet. One XRP per account, currently 1.20 euros, stays tied up. Clarify who bears it and whether you get it back when the account is closed. Anyone who would rather buy in the ordinary way will find the terms in the crypto exchange comparison.
  2. Clarify the key export. Only with an export do you hold XRP yourself. The differences between the wallet types are set out in the software wallet comparison.
  3. Secure the export of events. Many micro payments mean many taxable events. Without an export function, the allocation under FIFO becomes laborious; a tax tool helps with the evaluation.

The next checkable date is the start date of the Privy integration, which both companies have so far left open. Until then the news stays what it is today: an access route that is being built, and a price that has not responded to it.

(As of October 14, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)

23m ago•
bullish:

0

bearish:

0

Manage all your crypto, NFT and DeFi from one place

Securely connect the portfolio you’re using to start.