About this plugin
Blipply lets a WooCommerce store take crypto without touching a blockchain, holding a coin, or learning what a wallet is.
Your customer chooses Pay with crypto at checkout, is taken to a secure Blipply payment page, and pays from whichever of hundreds of cryptocurrencies they hold. You are credited in dollars. The order is marked paid and the customer is returned to your store.
Setting it up takes one sign-in. You do not create an API key, copy a secret, or configure a webhook. Sign in with your Blipply email and PIN, choose which business the store sells for, and the plugin does the rest itself.
What you should know before installing
The money arrives in Blipply, not in WooCommerce. Crypto payments settle as USDC into your Blipply wallet. WooCommerce records the sale and marks the order paid, but your bank balance will not move and your usual payout will not include these orders.
You spend or withdraw them from Blipply, including with the Blipply card.
Refunds are manual. There is no way to send crypto back automatically. You refund from your Blipply wallet and mark the order refunded in WooCommerce yourself.
This plugin deliberately does not add a Refund button that could not work.
You need a Blipply account, created in the Blipply app or web app before you start. It is free and takes a few minutes. It cannot be created from inside WordPress, because your wallet is created on your own device.
Everything after that — the API key, the webhook, the return address — this plugin does for you.
Test and live are separate accounts. The plugin can run against Blipply’s test system, but that is a different system with its own sign-up and its own keys — nothing you create there exists in your live account. While in test mode the payment option is labelled “(Test mode — not a real payment)” at the checkout, so a store cannot quietly take orders that moved no money.
Features
- Set up by signing in — no API key to create, no secret to copy, no webhook to configure
- Works with both the block checkout and the classic checkout
- Prices in your own store currency — Blipply converts at payment time, so a link is worth what it says whenever the customer gets to it
- Signed payment notifications, verified before an order is ever marked paid
- An independent reconciliation job, so a dropped notification delays an order rather than losing it
- Unpaid orders are cancelled after a period you choose, which releases the stock they were holding
- HPOS (High-Performance Order Storage) compatible
External services
This plugin connects to the Blipply payment API, operated by Blipply, in order to create and track crypto payments. It is required for the plugin to function.
When data is sent: when you save your settings, when a customer places an order using Blipply, and periodically while an order is awaiting payment.
What is sent:
- On saving settings — your store’s web address, so customers can be returned to it after paying, and the address this store should receive payment notifications on.
- When an order is placed — the order total and currency, your order number, the description of the order, and the customer’s billing email address so you can identify who paid.
- While an order is awaiting payment — the identifier of that payment only.
Your API key is sent with every request to identify your business.
com
com/terms-of-use
com/privacy-policy
This plugin also uses OpenStreetMap’s Nominatim geocoding service, operated by the OpenStreetMap Foundation, to turn a business address into map coordinates. It is used once, only if you create a new Blipply business from the plugin’s settings screen, and never during a payment or at checkout. The only thing sent is the address you type into that form, along with your store’s country to narrow the search.
Nothing about your customers or your orders is sent, and nothing is sent if you pick a business you already have.
org
org/policies/nominatim/
org/wiki/Privacy_Policy