WooCommerce XRP

WooCommerce XRP is a payment gateway which makes it easy to accept XRP as a payment method. You can choose between multiple different cryptocurrency exchanges in order to get the latest XRP rates upon checkout. With the ease of XRPL Webhooks, the order is updated in seconds after the payment is made. This is particularly useful if your customer is making a partial payment, since a new QR-code is generated with the remaining amount of XRP to pay to complete the order.

Acknowledgments

• A huge thank you to both Ripple and XRPL Labs for being awesome.
• A huge thank you to Jens Twesmann for his code contributions.
• Thanks to the translators! (Chronos Ananké, Bert de Hoogh and Tarotaro)
• Thanks to everyone who tests new unreleased code to help us nail bugs.

1. Upload the plugin to the /wp-content/plugins/woocommerce-xrp directory folder, or install the plugin through the WordPress plugin screen directly.
2. Activate the plugin through the Plugins screen in WordPress.
3. Create a free account at XRPL Webhook and obtain your API keys. This is required as the plugin uses this webhook to update the checkout page whenever a payment is made.
4. Go to “WooCommerce -> Settings -> Payments” and configure the plugin.

Which XRP server (rippled) is used by default?

The node s2.ripple.com is being used to talk to the XRP network. This can easily be changed under Advanced and you can use any public XRP server.

What is XRPL Webhooks?

XRPL Webhooks is a free service that send HTTP requests to a specified URL each time a transaction is made to a specific XRP account. The plugin use this service to update the order in real-time when the customer makes a payment.

Which exchanges is supported?

You can use the decentralized exchange (DEX) on the XRP Ledger, Binance, Bitbank, Bitfinex, Bitlish, BitMEX, Bitrue, Bitsane, Bitstamp, Bittrex, Bitcoin Exchange Thailand, CEX.IO, Coinbase, Kraken, OKEx or Uphold as the exchange to get the XRP rate when your customer is checking out.

Which base currencies are supported?

The supported currencies are AUD, BGN, BRL, CAD, CHF, CNY, CZK, DKK, EUR, GBP, HKD, HRK, HUF, IDR, ILS, INR, ISK, JPY, KRW, MXN, MYR, NOK, NZD, PHP, PLN, RON, RUB, SEK, SGD, THB, TRY, USD and ZAR. The rates are updated daily using the XML feed from ECB.

What does the bypass firewall feature do?

By default, we speak JSON-RPC on port 51234 with the XRP server. Some webservers are behind a firewall that doesn’t allow outgoing traffic on non-standard ports. By enabling this feature, we talk to cors-anywhere.herokuapp.com, using TLS on port 443, which then acts as a proxy and relays the traffic to the XRP server.

1. 

   Plugin settings screen.

2. 

   Advanced options.

3. 

   Checkout page, waiting for payment.

1.1.4

• Add a new exchange. (OKEx)
• Add support for GBP as base currency for Bitstamp.

1.1.3

• Add support for the new X-addresses.
• Change the XRP-address in the QR-code to support more wallets.

1.1.2

• Add the decentralized exchange. (DEX)
• Fix the text style on the checkout page.

1.1.1

• Add new exchanges. (Bitsane, CEX.IO, Coinbase, Uphold)
• Add missing sanitation checks for user input.
• Add new order status (Overpaid) for when a customer pays too much.
• Fix potential rounding error when processing payments.
• Fix a bug where the payment gateway was loaded twice.
• Add so the webhook try again if we’re unable to talk to the XRP node.

1.1.0

• Remove the use of Google Chart to generate the QR-code. Use qrcodejs instead.
• Change to a singleton layout to avoid conflicting with other plugins.
• Add check to ensure that the specified XRP account is activated.
• Add a new exchange. (Bitrue)
• Fix a bug which prevents us from running on 32bit systems.

1.0.3

• Add 3 new exchanges. (Bitbank, Bitcoin Exchange Thailand and Bitlish)
• Add 31 new currencies.
• Add 2 new languages. (Dutch and Japanese))
• Add a proxy feature to bypass your servers firewall.
• Lots of bugfixes.

1.0.2

• Add mitigations against the partial payment exploit.

1.0.1

• Remove the cURL dependency and use wp_remote_get() and wp_remote_post() instead.

1.0.0

• Initial release!