Cherum Pay for WooCommerce

Changelog

1.3.8

• The settings screen no longer says “Connected” over a connection Cherum has switched off. Cherum switches a notification endpoint off by itself — when the store’s address answers “no such route” long enough (a plugin update, maintenance mode), when every delivery fails for days, or when another endpoint takes over the same address. The store now reads that state, switches notifications back on and prints the reason it was off; it also asks Cherum four times a day instead of only when somebody presses Save.
• Changing the API key no longer leaves a dead endpoint behind. This store keeps one notification secret, and Cherum keeps an endpoint per key: swapping the key — test to live, or a re-issued one — used to register a new endpoint, overwrite the only secret, and leave the previous endpoint switched on and rejecting every delivery for a day and a half. The old endpoint is now switched off at the moment of the change, while the store still holds the key that is allowed to do it.
• Events that happen while notifications are off are no longer lost: Cherum holds them and sends them when the endpoint comes back on, and the store says how many are on their way.

1.3.7

• A discount can no longer make an order too small to pay for. Cherum will not invoice less than $0.50 — below that the network fee to move the money is larger than the money — and with a large discount next to a coupon the cart could land under that: the buyer filled in the checkout, pressed “Place order” and was told “Amount is below the minimum of $0.5” with nothing they could do about it. The discount now stops at the smallest payable amount, whatever the rate and the currency.
• An order that is too small on its own does not offer this payment method at all, and when it is the only method the buyer is told why and what to do — instead of “there are no payment methods for your location”, which was neither true nor useful. The settings screen names the figure. In a shop whose currency is not the US dollar the exact figure is the one Cherum priced your last order at, so it is known from your first Cherum order onwards.
• An invoice that expires on an order that has already been paid no longer writes to the buyer. An order can be paid on an invoice that was replaced since — a buyer coming back to a pending order and paying the first one — and when the replacement expired, “Leave it pending” e-mailed the person who had already paid the details of their order with a link to pay it. The expiry is recorded on the order and nothing else happens; the safety-net check no longer asks about paid orders either.

1.3.6

• A refund that has not been paid out yet can be called off from the order screen: Order actions → “Cancel Cherum refund” → Update. Cherum allows one open refund per payment, and an open one can wait days for the buyer to give a wallet — until now that left the shop unable to finish it, replace it or end it without opening another dashboard.
• Deleting the refund line WooCommerce recorded (Order → Refunds → ×) cancels the Cherum refund too, so a payout can no longer reach the buyer with no record of a refund left in the store.
• An order put on hold because a refund failed is put back where it was when you delete that refund line. It used to stay “On hold” for ever — including when you did exactly what the note told you to do.
• “A refund is already open on this payment” now names the refund and says how to end it, instead of stating a rule you could not act on.
• The Cherum Pay box on the order screen names an open refund while there is one.

1.3.5

• The classic checkout re-totals when you change the payment method. Since 1.3.3 the crypto discount appears there, and the totals on screen did not follow the choice: pick crypto last and you placed the order looking at the full price; pick crypto and then something else and you were looking at the discounted total while the order was written at the full price. The amount charged was always the right one — the number on the screen was not.
• The discount can no longer round a cart down to zero. 1.3.3 said the 90% cap had closed that; the zero came from the rounding, not from the cap, so a cart left at a few cents by a coupon still reached 0.00 — and WooCommerce completes a zero order without calling any payment method, so the goods left the shop with no invoice and no payment. One unit of the currency always survives now, in currencies with minor units and without.
• Refunds go against the invoice that was actually paid. An order that was paid on an invoice replaced since — a buyer coming back to a pending order and paying the first one inside the late window — could not be refunded from WooCommerce at all: the refund was opened against the newest invoice, which nobody had paid. Orders paid by earlier versions are recognised too.
• “Leave it pending” really does e-mail the buyer now. 1.3.3 said it did and it did not: it asked whether WooCommerce’s “Order details” e-mail was switched on, and that e-mail is a manual one with no such switch, so the answer was no on every store and nothing was ever sent. The plugin now sends it the way the “Send order details to customer” order action does, and reports what actually happened.
• Money in order notes is written in the currency of the ORDER, not of the shop. On a store that has changed currency, or on any multi-currency store, the refund box offered “€52.92” and the note beside it called the same money “$52.92”.

1.3.4

• Packaging only, for the WordPress.org directory review: the listing images (banner, icon, screenshots) and the bundled Russian translation are no longer inside the plugin; translations come from translate.wordpress.org. The payment method’s logo at checkout is the plugin’s own file.
• No change in behaviour.

1.3.3

• The crypto discount now works on the classic checkout. It never had: the discount was hooked from the payment method’s own object, and on a classic checkout that object does not exist yet when the cart is totalled — so the order was written at the full price, with no sign anywhere that a discount had been set.
• The discount is taken off the price after coupons, not before. With a 50% coupon and a 2% crypto discount the shop was handing back 2% of the full price, twice what it meant; a large discount next to a large coupon could bring the cart to 0.00, which WooCommerce completes without calling any payment method at all.
• An order remembers every invoice it has ever had. When a buyer paid a second time, the store kept only the newest invoice id and answered “unknown order” to everything about the older one — including money arriving late on its address, and a payment confirmed on it inside the 24-hour window that follows an expiry. That left a paid buyer looking at an unpaid order, with nothing in the order history to explain it.
• The late-payment note carries the figures again. It read the two fields the service does not send, so every such note in every shop said “(amount in dashboard, tx —)”. It now names the amount, the coin, the network and the date you have to decide by.
• “Leave it pending” really does e-mail the buyer a way back. Both the setting and the order note promised a link in the buyer’s e-mail, and WooCommerce sends a customer nothing at all for an order that stays pending. The plugin now sends WooCommerce’s own order-details e-mail, once, and says plainly when it could not.
• The overpayment note no longer promises an automatic refund. A surplus goes back only after the buyer names a wallet on the payment page, and a surplus below Cherum’s minimum refund amount does not go back at all.
• The credited amount is written as money: “$60.83 credited… the exact amount is 60.82758 USD” instead of a bare “60.82758”, which a shop in another currency read as its own.
• A refused refund is written on the order. Every refusal used to live only in the pop-up you then closed: no note, no log line, no reason.
• Two deliberate refunds of the same amount, with the same reason, are two refunds. They shared an idempotency key, so the second was answered with the first and WooCommerce recorded a refund line for money that had left once. A retry after a timeout still replays the same request, which is what that key is for.
• Refunds say up front that a rehearsal key cannot make them. The rehearsal notice says so too.
• “Receipt from Cherum” checks, when you save, whether Cherum is sending buyer receipts at all, and tells you if it is not — rather than sending the buyer’s e-mail address out of the store for a letter that cannot be sent.
• The suggested privacy-policy text follows the settings instead of stating, always, that no e-mail address is sent.

1.3.2

• Paying a second time works. With “Leave it pending” set, an order whose invoice had expired sent the buyer straight back to the expired invoice — the only page they could reach was the one telling them it was too late. The plugin now checks the invoice before reusing it and asks for a fresh one when the old one is dead.
• Refunds are no longer refused when the service is reachable and accepted when it is not. The two cases were the wrong way round: a timeout blocked the refund and showed the raw cURL line, while the service’s own “cannot price a refund right now” was mistaken for a hiccup and the refund was sent anyway.
• A refusal without a sentence now names its reason and its numbers instead of “Cherum Pay returned status 409”.
• One e-mail per payment. With “Order status once paid = Completed” the buyer received both “Processing order” and “Completed order” for the same payment, and the order history showed a transition that never needed to happen.
• An order rescued by the fallback check keeps “Paid with 8.83 USDC · base”, like an order closed by a notification.
• The fallback check goes oldest first and remembers what it has asked about. On a store with more than ten stale orders the oldest — the ones about to fall out of the window for good — were never asked about at all.
• The discount and the invoice lifetime are checked when they are saved. “95%” saved happily and no discount ever appeared; “2 minutes” was quietly turned into 5. Both now say what was actually stored.
• A failed connection attempt no longer forgets the endpoint number, which made the next successful save roll the notification secret for nothing.
• A network failure at checkout tells the buyer nothing was charged, instead of showing them “cURL error 28: Operation timed out”.
• “Invoice created” is written to the order history only when the invoice really is a new one.

1.3.1

• “Back to the shop” on the payment page no longer cancels the order. It used to open WooCommerce’s cancel link, so a buyer who just wanted another look at the basket lost the order without being asked. It now goes to the order’s own pay page, where they can pay again or pick another method.
• The payment page opens in the store’s language. Russian, Spanish, Indonesian, Arabic, Brazilian Portuguese and Chinese shops send their buyers to a translated page instead of an English one.
• The “order received” page says whether the crypto payment is confirmed or still on its way, with a link to the payment page — that page is the receipt and keeps the transaction.

1.3.0

• One-field setup: paste the API key and save; the plugin registers the store for notifications and keeps the secret. The settings screen shows the connection state and says in plain words when a key is wrong, lacks a permission or the site has no https yet.
• A notice in the settings when a test key is in use.
• The readme and the settings texts rewritten for people.
• Refund notifications now reach the order. They were answered but not applied: the order was looked up by the refund id instead of the invoice id. Found on a live refund rehearsal, fixed before release.

1.2.2

• The block checkout shows the Cherum mark next to the method name.
• The checkout text names what the buyer can actually pay with.

1.2.1

• An “underpaid” event that arrives after the payment completed no longer demotes a paid order. The replay lock is taken before the event is applied and released if applying fails.

1.2.0

• “Order status once paid” and “Write a log” now do what they say.
• Translations load on self-installed copies.
• Refunds from a non-USD store convert at the order’s own rate.
• Fallback check for lost notifications: the “order received” page and a 15-minute cron pass.
• Gateway icon on the classic checkout; uninstall removes settings and transients.

1.1.0

• Every platform event handled. Refunds from the order screen. Optional crypto discount. Choice of order status once paid. Optional log. Russian translation.

1.0.0

• First release: classic checkout, Cart and Checkout blocks, High-Performance Order Storage.