Title: Ledger Direct Author: LedgerDirect Published: 19 Desember 2025 Last modified: 26 Oktober 2026 --- Cari plugin ![](https://s.w.org/plugins/geopattern-icon/ledger-direct.svg) # Ledger Direct Oleh [LedgerDirect](https://profiles.wordpress.org/ledgerdirect/) [Unduh](https://downloads.wordpress.org/plugin/ledger-direct.1.4.1.zip) * [Detail](https://id.wordpress.org/plugins/ledger-direct/#description) * [Ulasan](https://id.wordpress.org/plugins/ledger-direct/#reviews) * [Instalasi](https://id.wordpress.org/plugins/ledger-direct/#installation) * [Pengembangan](https://id.wordpress.org/plugins/ledger-direct/#developers) [Bantuan](https://wordpress.org/support/plugin/ledger-direct/) ## Deskripsi LedgerDirect is a WordPress plugin that allows you to accept direct payments in XRP, USDC, and RLUSD on the XRP Ledger. It provides a seamless integration with WooCommerce, enabling merchants to receive payments directly in their XRP Ledger accounts without the need for intermediaries. ### Features * Accept payments in XRP, USDC and RLUSD. * Receive payments directly to your wallet without any intermediaries. #### How do I know if my XRP account is setup correctly? The best way is to configure the plugin to use the testnet and make a test payment. ### Test Payments To test the plugin, you can configure it to use the XRP Ledger Testnet. This allows you to simulate transactions without using real funds. Follow these steps: 1. Go to the plugin settings in WooCommerce. 2. Enable the Testnet mode. 3. Use a XRP Ledger test account to make test payments. 5. You can create test account from https:// xrpl.org/xrp-testnet-faucet.html for XRP or https://tryrlusd.com/ for RLUSD. ### External services LedgerDirect uses public APIs from Coinbase, Coingecko, Binance, and Kraken to retrieve current cryptocurrency exchange rates. These rates are needed to correctly calculate and display payments. No personal or payment data is sent to these services. Only requests for current rates are made when a payment is processed or displayed. For more information about each service, see: – Coinbase API: [Terms of Service](https://www.coinbase.com/legal/user_agreement), [Privacy Policy](https://www.coinbase.com/legal/privacy) – Coingecko API: [Terms of Service](https://www.coingecko.com/en/terms), [Privacy Policy](https://www.coingecko.com/en/privacy) – Binance API: [Terms of Use](https://www.binance.com/en/terms), [Privacy Policy](https://www.binance.com/en/privacy) – Kraken API: [Terms of Service](https://www.kraken.com/legal), [Privacy Policy](https://www.kraken.com/privacy) ### Source Code of minified assets The payment page’s script and stylesheet (`public/js/ledger-direct-payment-ui/payment- page.js`, `wallets.js`, `public/css/payment-page.css`) are the built files of the package `@ledger-direct/payment-ui`, MIT, whose source and build are at https:// github.com/ledger-direct/ledger-direct-payment-ui — the tag is in `public/js/ledger- direct-payment-ui/VERSION`. `wallets.js` bundles XRPL Connect (https://github.com/ XRPL-Commons/xrpl-connect) and xrpl.js. The checkout block script `includes/assets/ js/frontend/blocks.js` is built from `resources/js/frontend/index.js` with @wordpress/ scripts. ## Instalasi #### Minimum Requirements * PHP version 8.2 or greater * WordPress 6.7 or greater * WooCommerce 8.6.1 or greater #### Automatic installation 1. Search for LedgerDirect plugin in the plugin section of your admin panel. 2. Activate the plugin. 3. Go to WooCommerce -> Settings -> Payments and enable the LedgerDirect gateway to manage the plugin settings. 4. Configure the plugin settings, including your XRP Ledger account details and the currencies you want to #### Manual installation 1. Clone the repo from https://github.com/ledger-direct/ledger-direct-woocommerce into the ‘plugins’ directory. 2. Run ‘composer install –no-dev –no-scripts –optimize-autoloader’ to install the composer dependencies. 3. Activate the plugin. 4. Go to WooCommerce -> Settings -> Payments and enable the LedgerDirect gateway to manage the plugin settings. 5. Configure the plugin settings, including your XRP Ledger account details and the currencies you want to accept. ## Ulasan Belum ada ulasan untuk plugin ini. ## Kontributor & Pengembang “Ledger Direct” adalah perangkat lunak open source. Berikut ini mereka yang sudah berkontribusi pada plugin ini. Kontributor * [ LedgerDirect ](https://profiles.wordpress.org/ledgerdirect/) * [ alexanderbuzz ](https://profiles.wordpress.org/alexanderbuzz/) [Terjemahkan “Ledger Direct” dalam bahasa Anda.](https://translate.wordpress.org/projects/wp-plugins/ledger-direct) ### Tertarik mengembangkan? [Lihat kode](https://plugins.trac.wordpress.org/browser/ledger-direct/), periksa [repositori SVN ](https://plugins.svn.wordpress.org/ledger-direct/), atau mendaftar ke [log pengembangan](https://plugins.trac.wordpress.org/log/ledger-direct/) melalui [RSS](https://plugins.trac.wordpress.org/log/ledger-direct/?limit=100&mode=stop_on_copy&format=rss). ## Log Perubahan #### 1.4.1 * Core 0.9: the synced transactions store the CTID in the column tx_ctid instead of ctid, the name every LedgerDirect plugin uses from now on (PostgreSQL reserves ctid for a system column). The column is renamed in place on the first request after the update; nothing changes for customers or merchants. * Core 0.9: a transaction whose CTID is malformed is skipped during sync, and logged, instead of being stored truncated. #### 1.4.0 * New order status “XRPL payment incomplete”: a payment that arrives but does not pay the order (too little, or another token) moves the order there, with a note saying what arrived, what was requested and what is still due. The order stays open, the page keeps polling, the background job keeps matching, and a top-up settles it. WooCommerce’s hold-stock cancellation, which only cancels “Pending payment”, leaves such orders alone. * A LedgerDirect panel on the admin order page: the payment state, what was quoted( asset, amount, rate, account, destination tag, issuer, quote validity), what arrived, what is still due, the transaction, and every transaction on the order’s destination tag linked to the explorer. * The receiving accounts are validated as XRPL addresses when the settings are saved; another chain’s address or a destination tag in the field is refused and the previous value kept. * Core 0.8.1: a payment in the other asset class, a token sent for an XRP order or XRP for a token order, is reported as a wrong-token payment with the full amount still due, instead of being ignored. Before, the page stayed on “waiting” while the money sat on the ledger. #### 1.3.0 * The payment page is redesigned on the shared package @ledger-direct/payment-ui: the amount to send is the largest thing on the page with a copy button, the receiving address, the destination tag (marked as required) and, for tokens, the issuer are numbered fields with copy buttons, a countdown with a bar, one column on phones, dark mode follows the system. * One QR code with the receiving address, the destination tag and the amount (for tokens also currency and issuer); a server-rendered code stays for browsers without JavaScript. * Browser wallets over XRPL Connect (Crossmark, GemWallet, MetaMask Snap, Ledger, Otsu, Xyra) when detected; Xaman and WalletConnect when the merchant enters their public identifier in the settings. The wallet library is loaded only when the wallet list is opened. * New settings: the logo of the payment page (site logo, a picture from the media library, or a monogram), an accent colour (refused when too light for white text), the Xaman API key and the WalletConnect project id. * The plugin’s scripts and styles load on the payment page only, no longer on every page of the site. * Icons for XRP, RLUSD and USDC next to the payment options in the checkout. * Requires hardcastle/ledger-direct-core 0.8. #### 1.2.0 * The payment page now follows the payment on its own: it polls every 8 seconds and shows one of five states – waiting (with a countdown for the quote), partial payment, payment in the wrong token, expired quote, and paid – and leaves for the order confirmation as soon as the order is paid or closed. No more reloading. * New status endpoint `/wp-json/ledger-direct/v1/payment-status/`, the same payload as every other LedgerDirect plugin. Access is by the order key, as on the “Order received” page, so guest orders work without a login. * The ledger is synced at most once per five seconds per receiving account, however many customers are waiting; the background job is unaffected. * An expired quote is no longer replaced silently on reload; the page says so and offers an updated amount on request. * Whether a payment is in the wrong token is decided by the shared library, the same rule as on every other platform. #### 1.1.1 * Fix: an order that received a partial payment could never be completed. The first payment was recorded and the plugin stopped looking, so a customer who then sent the remaining amount was never marked as paid, neither on the payment page nor by the background job. Payments in the quoted asset now add up, and the order is matched until it settles. * Fix: a payment in the right stablecoin from another issuer no longer blocks a later payment from the correct issuer. * Core 0.7: the shared library is now required at ^0.7. * Release build: a developer document that had been copied into the bundled library was shipped with 1.1.0; it is removed, and the build now refuses to ship such files. #### 1.1.0 * Core 0.4: the sync cursor is now kept per receiving account and network. A mainnet transaction can no longer stall the testnet sync, and a testnet reset no longer requires cleaning the database – the plugin resyncs on its own. * Core 0.3: when several transactions carry the same destination tag, the newest one in the quoted asset is used. A stray payment in another asset no longer blocks settlement of the real one. * Database schema version 3: `network` column on the transactions table, backfilled from the CTID; migrates automatically on the first request after the update. #### 1.0.0 * The plugin is now an adapter over the shared `hardcastle/ledger-direct-core` library, so prices, exchange rates, destination tags, transaction sync and the settlement decision are identical across all LedgerDirect plugins. * Fix: XRP payments were only accepted when the delivered amount was at or below the requested amount. Overpayment now settles, and a shortfall of up to 0.15 % is tolerated, as in every other LedgerDirect plugin. * Fix: stablecoin payments were compared as raw arrays; a payment from another issuer is now always rejected and an overpayment accepted. * Fix: the RLUSD and USDC switches were wired to the wrong asset depending on the network. * Fix: the quote expiry setting was ignored (every quote lasted 15 hours). Quotes now expire as configured and are refreshed in place on the payment page, keeping the same destination tag. * New: orders are settled in the background every five minutes via Action Scheduler, so a customer who closes the payment page still gets their order marked paid. * New: the payment page shows how much of the requested amount has arrived and what is still missing. * New: exchange rates are cached briefly (60 s) so a checkout render no longer waits for three price oracles. * Database schema version 2: numeric ledger index, per-account destination-tag counter; migrates automatically on the first request after the update. * Requires PHP 8.2. #### 0.11.0 * Fix: the destination-tag table existed under three different names across install. php and XrplTxService, so reserved destination tags were silently never persisted on fresh installs. Unified to `ledger_direct_xrpl_destination_tag`, with an automatic upgrade routine for existing installs. * Fix: add a unique constraint on the transactions table’s `hash` column to enforce deduplication at the database level. * Fix: KrakenOracle only ever returned a price for the XRP/USD pair (it read a hardcoded response key); it now reads any pair generically. * Fix: price oracle failures are now logged instead of silently discarded, to make pricing issues diagnosable. * Fix: the “change payment method” AJAX action always failed due to a typo reading the wrong POST field. * Add: order pricing metadata now includes `base_asset` and `quote_currency` fields alongside the existing `pairing`/`exchange_rate`/`amount_requested`. * Remove: the unused, always-returns-zero RippleOracle. * Internal: added automated tests, a CI pipeline (lint, coding standards, static analysis, PHPUnit, WordPress Plugin Check), and a WordPress.org SVN release workflow. ## Meta * Versi **1.4.1** * Diperbarui **2 hari yang lalu** * Instalasi Aktif **Kurang dari 10** * Versi WordPress ** 6.7 atau yang terbaru ** * Diuji hingga **7.1.3** * Versi PHP ** 8.2 atau yang terbaru ** * Bahasa * [English (US)](https://wordpress.org/plugins/ledger-direct/) * Tag * [rlusd](https://id.wordpress.org/plugins/tags/rlusd/)[usdc](https://id.wordpress.org/plugins/tags/usdc/) [woocommerce](https://id.wordpress.org/plugins/tags/woocommerce/)[xrp](https://id.wordpress.org/plugins/tags/xrp/) * [Tampilan lanjut](https://id.wordpress.org/plugins/ledger-direct/advanced/) ## Rating No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/ledger-direct/reviews/#new-post) [Lihat semua ulasan](https://wordpress.org/support/plugin/ledger-direct/reviews/) ## Kontributor * [ LedgerDirect ](https://profiles.wordpress.org/ledgerdirect/) * [ alexanderbuzz ](https://profiles.wordpress.org/alexanderbuzz/) ## Bantuan Ada yang ingin dikatakan? Butuh bantuan? [Lihat forum bantuan](https://wordpress.org/support/plugin/ledger-direct/)