Von Payments for Medusa changelog
Each release of vonpay-medusa, newest first, with what to do when you update. To install an update, follow Apply an update.
1.6.0
When you update:
- Run
npx medusa db:migratein the Medusa server project, as after every update. 1.6.0 adds no tables. Coming from 1.4.x or older, also do the 1.5.0 steps. - If one-click offers are on, update
vonpay-medusain the storefront to 1.6.0 too and redeploy it, or offers stay off. Then add theprepareVonpayClaimaction to theactions.tsfile insrc/lib/vonpay(Offers stay with the shopper's browser). With offers off (the default), the storefront needs no change. - Update when few shoppers are checking out: an offer page open when the new plugin starts disappears.
- Update the Medusa server and the worker together. While a 1.5.x process runs beside a 1.6.0 one, a 1.5.x save can still erase a record.
- Run the setup check. If its new
collection_handleline fails, fix it as the line says.
What changed:
- One-click offers stay with the shopper's browser. Someone who got hold of a checkout's cart id can no longer accept that shopper's offers. A storefront that is not updated gets no offer page, and an order the storefront did not complete gets none either (Offers stay with the shopper's browser).
- Recovery without a shared locking module. When Medusa's default locking module is not Redis or Postgres, the recovery job no longer completes paid checkouts. Each one it finds waits on Held payments as Paid, order not created, or Payment held, no order for a held wallet payment or held card (
recovery). With Redis or Postgres locking, nothing changes. - Recovery under a flood of checkouts. Many unpaid checkouts can no longer keep a paid one out of reach. When runs keep ending with checkouts left for later, the plugin logs the error
recovery_backlog. - Records are saved safely. The records the plugin keeps on a payment (offer proof, held payments, refunds, renewals) are no longer lost when two processes save at once. A store whose database connection cannot see its payment records now gets an error and a failed
collection_handleline in the setup check, instead of a silent fallback (Check the setup). - Cancelled, payment not closed. A cancelled order whose payment could not be closed now shows on Held payments, with Release and Mark resolved (Held payments).
- Why an offer did not show is logged as
vonpay_log_upsell_offer_proof_skipped, with the reason (Offers stay with the shopper's browser). - Checkout in your own words and language. The card step and the 3-D Secure return page take
copy,localeandcardPlaceholder(Your own words and language). The offer pages'localealso reaches the wallet button. Leave them out and nothing changes. - Medusa 2.22. Amounts are copied exactly with Medusa 2.22's newer number handling. Tested on Medusa 2.15.5, 2.21.2 and 2.22.7.
- Subscription renewals. A renewal declares the saved card's own stored-credential use, as before. Only when the card has none does it use the value its $0 card check declared. When the two differ, the plugin logs the warning
renewal_declaration_differs.
1.5.1
When you update: run npx medusa db:migrate as after every update. Nothing else. Coming from 1.4.x or older, also do the 1.5.0 steps.
What changed:
- Held payments text. The Payment held, no order and Payment held, release failed rows said a held card is taken when the order ships. They now say when the order is fulfilled, which is when the plugin takes it (Card hold, then capture). Nothing else changes.
1.5.0
When you update:
- Run
npx medusa db:migratein the Medusa server project, as after every update. 1.5.0 adds no table of its own. Coming from 1.3.x or older, also do the 1.4.0 steps. - If your server's outbound traffic is filtered, allow
https://www.vonpay.com/medusa/timestamp.json(same host as the update file). - If you sell items that need no delivery and changed the starter's Payment step, Review step or pay button, switch their delivery check to
deliveryDone(cart)(Items that need no delivery).
Card payments work as before until you set the new cardCapture option.
What changed:
- Card hold, then capture. With
cardCapture: "at_fulfillment", the card is held at checkout and charged when the order is fully fulfilled (when the amount due fits the hold), or when you press Capture (Card hold, then capture). The setup check failscard_holdswhen your card connection cannot hold, whenrecoveryis off, or without a shared locking module. - Held cards on Held payments. A hold 3 days old, an order fulfilled but not collected, and a capture the plugin stopped retrying each show there (Held cards).
- Wallet payments. When Von Payments refuses to take a held wallet payment, the plugin now treats that as final and stops retrying. A wallet payment Von Payments reports as cancelled (for example, an abandoned 3-D Secure check) counts as released.
- Update notice. It always names
npx medusa db:migrateand always shows What changed. Your server also reads a "still current" file that Von Payments signs (When an update is available). - Items that need no delivery. A cart with nothing to deliver (a digital product or a service) now starts the Von Payments payment. The storefront kit adds
deliveryDoneandnoDeliveryNeeded.
1.4.0
When you update:
1.4.0 replaces 1.3.0. Coming from 1.2.x, update straight to 1.4.0 and also do the 1.3.0 steps (and the 1.2.1 steps from 1.2.0 or older). One db:migrate covers them all.
- Run
npx medusa db:migratein the Medusa server project. Every store needs it. Until it runs, the plugin refuses every ReorderJS renewal charge (nothing is charged) and logs an error that names the command; the setup check reportsrenewal_period. Ifmedusa-config.tsdoes not list the plugin underplugins:, its job modulevonpay-medusa/modules/vonpay-jobsmust be inmodules. - With subscription renewals on, give your secret key the
payment_intents.readpermission (restricted keys). Without it, every renewal is refused and the setup check failsrenewal_search. - Make sure
VONPAY_WEBHOOK_SECRETholds your endpoint's signing secret. 1.4.0 installs@vonpay/checkout-node4.10.0, which refuses a webhook secret that is empty, a documentation sample or an API key: payment updates then fail. - A store that runs a server and a separate worker needs Medusa's Redis or Postgres locking module (Before you install).
What changed:
- One charge per subscription period. The plugin keeps its own record of each ReorderJS renewal period and refuses a second charge for a period that is already paid, or whose earlier charge is not finished (Subscription renewals).
- A retry limit after a declined renewal. Only ReorderJS's own retries of the declined order charge that card again, at most once in 24 hours, and never after a decline marked final. A new order for the same period on that card is refused. Another card charges as normal (a decline from before 1.4.0 can hold it for up to 24 hours).
- Renewal periods on Held payments. A period that ReorderJS keeps asking to charge shows there, with Keep blocked, Reopen this period and Reopen for one order (Renewal periods).
1.3.0
When you update:
Coming from 1.2.0 or older, also do the 1.2.1 steps. One db:migrate covers both releases.
- Run
npx medusa db:migratein the Medusa server project. Every store needs it. Until it runs, the plugin cannot follow refunds (below), and its background job logs one error per run that names the command. - If you use one-click add-ons, add the
upsellOfferShownline to your storefront (Offer results).npx vonpay-medusa setup-storefrontnames the missing lines. Without it, Results counts answers and money but no offer views. - Keep the shared Redis locking module that Before you install asks for. The refund follow-ups lock each row. With more than one server or worker process and no shared lock, the job skips the rows and logs an error each run.
What changed:
- Offer results. Orders › One-click offers › Results shows how shoppers answered each offer and what it brought in (Offer results).
- Refunds that did not complete come back. When Von Payments cancels or fails a refund you made in Medusa, or has not finished it after two days, the payment comes back on Held payments (Refunds that did not complete).
- ReorderJS 1.1.1. Use ReorderJS 1.1.1 or later. In 1.1.0, a retry of a failed renewal never reached the payment provider (Subscription renewals).
1.2.1
When you update:
- Run
npx medusa db:migratein the Medusa server project. It adds the table for the background job's heartbeat. Ifmedusa-config.tsdoes not list the plugin underplugins:, also add its job module (Apply an update). - Run the setup check once: Check Vonpay setup under Orders › Held payments, or
npx vonpay-medusa-check. It lists each paid checkout an earlier version left without an order (Check the setup). - If your storefront was set up with 1.2.0 or earlier, run
npx vonpay-medusa setup-storefrontagain. It moves the card form into the Payment step. If you changed your checkout, make the step by hand (Add the card step to your storefront).
What changed:
- Card form in the Payment step. Card entry appears directly above Place order, with no separate Review step.
- Paid checkouts without an order. The setup check's
paid_without_orderline lists them, and Move to Held payments puts each one where you can refund it or mark it resolved. - The background job proves it runs. Held payments shows a banner when the job is late or its table is missing (Held payments on Medusa).
1.2.0
- The charge must equal the cart's total before the order is placed.
- The typed card is kept when the cart's total changes.
1.1.1
- "No thanks" keeps the offer pass. After a shopper says "No thanks" to a one-click offer, the downsell and the next offer still show.
1.1.0
- Offers in the Medusa admin. You manage one-click offers in the Medusa admin.
1.0.4
- The offer pass is issued at Pay.
1.0.3
- No second, late refund after an unclear refund answer.
1.0.2
- Money fixes, a signed shopper address, and offer rules.
1.0.1
- The update notice. This release turns on the update notice in the Medusa admin.
1.0.0
- First public release.