Building a Reliable Event-Driven Payment Service With XRP Ledger
Receiving a transaction notification is only the first step. Production software still has to decide whether that event is safe to turn into application state.
A WebSocket callback can arrive in milliseconds. What happens afterward is harder. The XRP Price may be the public-facing metric most people associate with the asset, but developers integrating the XRP Ledger have a different concern. A long-running service has to detect transactions, determine whether their outcomes are final, and update local application state without acting twice or acting too soon.
When an XRPL Event Actually Means Something
A WebSocket connection can save an application from constantly polling for new activity. On a Linux service, that means keeping the connection open and listening for the XRP Ledger events the application cares about.
The XRP Ledger’s subscribe documentation explains how applications can listen for ledger activity, transactions, and account-related events. The transactions stream reports transactions associated with closed ledgers. The transactions_proposed stream goes further and can include proposed activity that never reaches a validated ledger.
That makes an incoming notification useful, but not necessarily authoritative. A service that treats every notification as an instruction to change business state can act before the ledger has established a final result.
For a payment service, the event is where processing begins.
Validation Comes Before Fulfillment
Transaction notifications can include a validated field. When validated is true, the transaction has been included in a validated ledger and its outcome is final.
A service might see a payment involving an account tied to an order and immediately tell a fulfillment system to release the product. If that payment came from proposed activity and has not reached a validated ledger, the application has acted before it knows the final outcome.
Validation is only the first check. Transaction metadata also includes TransactionResult. A transaction can be final without producing the successful result the application expected, so inclusion in a validated ledger should not be treated as proof that a payment succeeded.
For payments, delivered_amount is the field that shows what actually reached the destination. That can matter when the amount requested and the amount ultimately delivered are not identical.
Before an order changes state, the service needs to know whether the transaction is final, whether it succeeded, and what value actually arrived.
KDE Plasma 6.8 has been released, arriving on the 30th anniversary of the free, open-source desktop environment’s founding. Changes are, as you’d expect, varied across the stack. A new backup tool, Kup, is included as part of Plasma 6.8 to make automated backups to external media easier, while Spectacle, the screenshot and screen capture tool, is now able to record system audio and microphone alongside screen contents. When running the Steam desktop client, it now renders shadows and rounded corners for better visual consistency with other apps run-on the desktop. Accessibility is boosted by a new ‘click dwell’ option to […]
A new version of free, open-source productivity suite ONLYOFFICE is out, bringing more than a thousand bug fixes and an expanded set of AI features. ONLYOFFICE Desktop Editors v10.0 is billed as a “fully rebuilt app”, and the developers warn those upgrading from earlier versions that not all of their settings and preferences will transfer over. Notably, its AI integrations are no longer included as a plugin that ships with the app. Inside, AI features in ONLYOFFICE 10.0 are provided via a separate AI Tools add-on. This needs to be downloaded and installed (the app has a flow for that). […]
Linux Mint shook up its release schedule this year and now it’s shaking up its versioning scheme as well – the next major release won’t be Linux Mint 23, but Linux Mint 27. Releases will now be numbered by year. Linux Mint 27 will be followed by v28, and so on. The release also sees the start of a new series of release codenames. Mint has traditionally used feminine first names, cycling through the alphabet from Linux Mint 1.0 ‘Ada’ in 2006 through to Linux Mint 22.3 ‘Zena’ in 2026. The series returns to ‘A’ with Linux Mint 27 and […]
Canonical has confirmed the codename of next year’s Ubuntu 27.04 release as Tenacious T-Rex. It follows Ubuntu 26.10 Stonking Stingray, which is out on 15 October, both sequentially and alphabetically. The previous T release was Ubuntu 14.04 LTS Trusty Tahr. Quite a contrast in creature between the two, no? As you likely know, every Ubuntu release has an alliterative codename coupling combining an adjective with an animal (or, on rare occasions, a mythological beast like a minotaur, werewolf or jackalope). The first part of the codename is not fluff, but a critical label used to distinguish and keep the backend […]
The multi-OS NexPhone went up for pre-order at the start of 2026, 14 years later than initially planned. Fitting, then, to hear the handset’s arrival has been delayed until 2027. Nex Computer CEO Emre Kosmaz says devices won’t begin shipping until March 2027 because of issues with antenna placement and casing issues. Given that it took 14 years for this to go from vapourware to tangible product, I doubt long-time fans of the concept will see a delay from Q3 2026 to Q1 2027 as a comparative blink of the eye. While they sort out the the hardware snags, work […]