What ships where
Three questions that get confused with each other, and the answer to all three is on this page: what PageBlocks has to provide, what is inside pbShop, and what arrives as a separate free package.
PageBlocks is required
pbShop is not a standalone application. Without PageBlocks installed it logs an error and switches itself off — there is no degraded mode. Tables and the field constructor, routing, controllers, file templates, migrations, the template engine, the mailer, image resizing through Glide and the file storage all come from there.
The package declares the dependency and the installer enforces it:
php >= 8.2
MODX >= 3.0.0
PageBlocks >= 3.0Install PageBlocks first, and install it as a package
The dependency check looks for an installed transport package. PageBlocks unpacked into directories by hand does not pass it, however many files are on disk — both products are meant to be installed through the package manager.
Order matters in the other direction too: install pbShop against a PageBlocks older than it expects, and the storefront answers 500 while the manager stays alive, which reads as "the shop is fine, the site is broken". That is not hypothetical — on 2026-10-03 a staging install gave exactly that, a Trait ResolvesGuest not found on the storefront with a working manager. Put the new PageBlocks on first, then the shop.
A pre-release version does not get in the way: pageblocks-3.0.0-alfa7 is split on the hyphen, 3.0.0 goes into the comparison and alfa7 does not.
One feature needs more than the minimum
The product gallery is a galleryfield in the product constructor, and the pictures live in PageBlocks' own pb_files. The shop carries no table of its own for them — see Catalogue. Two consequences worth stating plainly rather than discovering:
galleryfieldis a paid PageBlocks field type. On the free edition the field is not drawn in the form, so there is nowhere to upload to. The storefront is built for that: with an empty gallery it prints the single product image exactly as it did before the field existed.- The field itself arrived with PageBlocks
alfa36, which was released to make it work. On an older platform the gallery has nowhere to live.
What is in the shop itself
Everything that is a shop function rather than somebody else's API: the catalogue, variants and options, the cart, checkout, orders and subscriptions, stock, prices per currency, promo codes, the document layer, the manager grids, the events, and the payment, delivery and cash-register driver layers with the drivers listed below.
What arrives as a free package
Two packages, free, and the rule that puts things in them is one sentence: the home market gets everything, other regions get a couple, and whatever we cannot verify goes into a package.
| Package | What is in it |
|---|---|
pbShopPay | YooKassa, T‑Bank (Tinkoff), CloudPayments, YooMoney, PayAnyWay |
pbShopShip | CDEK, Russian Post |
So YooKassa does exist — just not in the box
This is the question this page exists to answer. The five Russian gateways were moved out on 2026-10-16, and the reason is not code quality: four of the five are written and covered by tests. The reason is that they will never see a live gateway — there will be no Russian merchant account on our side, by the owner's decision. That used to be a debt that would close one day; for these five it is a permanent condition.
Unverifiable code in a paid core is a guarantee we cannot give. The same code in a free package with an honest status table is an ordinary best-effort delivery with expectations set in advance. The second reason is the everyday one: YooKassa changes its API on its own schedule, and in the core every such change would be a release of the whole shop for people who do not use it.
A package registers its drivers from its own bootstrap.php, which MODX executes itself. The core knows nothing about them — not the class, not the key. Neither package carries tables of its own: a payment method and a delivery method are core entities, and a driver only serves them.
Removing a package does not delete the method rows, it disables them. Deleting would lose the merchant keys typed into them; leaving them enabled would give the buyer Unknown payment driver at checkout.
Documentation for the two packages is their own; this site is about the core.
What went down into PageBlocks
- Favourites are
pbFavorites. The shop keeps a 90-line product provider for it and nothing more. The dependency is soft: with no pbFavorites installed, the heart simply is not printed. - Login and registration are pbAuth or the site itself. The shop prints "Log in" / "Account" / "Log out" in the storefront header, taking the address from settings and failing that from pbAuth's named routes. With neither, no link is shown at all — a "Log in" that leads to a 404 is worse than no link.
- Reviews and ratings are not ours and are not here. They belong to a component at the PageBlocks level, because a blog needs them too.
Honest status of the drivers
A driver in the box is a promise to keep it working. It is not a promise that money or a parcel has ever gone through it on our side, and conflating those two is how support tickets get written. So, with the same legend the internal inventory uses:
- ✅ — passed by hand against a live counterparty;
- 🟢 — the code is there and the protocol is implemented from the documentation; we have never seen the live service.
🟢 is the normal state here, and it is not an apology
We hold no carrier contract at all, no cash-register contract, and of the payment gateways exactly one has a real payment behind it. You cannot sign a carrier contract in order to test a driver, and a fiscal operator will not issue a sandbox without one.
What 🟢 does mean: the signature, the request format and the callback parsing were written against the gateway's own reference material and are covered by a test, not by a retelling of the documentation. What it does not mean: that the first live transaction will work. Budget for a test transaction of your own before you open the shop.
Payment drivers in the core
| Key | Gateway | Status | Recurring |
|---|---|---|---|
manual | Offline, the manager confirms | ✅ | — |
bill | Invoice for a legal entity, PDF | ✅ | — |
maib | maib (Moldova) | ✅ the only one with a real payment behind it; signature covered by a test | ✅ |
liqpay | LiqPay / PrivatBank | 🟢 signature checked against their SDK's reference | ⛔ by design — the gateway owns the schedule |
monobank | Monobank Acquiring | 🟢 callback is ECDSA-signed; key rotation covered | ✅ card token |
wayforpay | WayForPay | 🟢 HMAC‑MD5; the concatenation order is what the test pins | ✅ |
fondy | Fondy | 🟢 the reference is genuine — their documentation prints both the string and the hash | ✅ |
portmone | Portmone | 🟢 the notification is not signed at all; the verdict comes from a second read | ⛔ by design |
stripe | Stripe | 🟢 Checkout Session; "complete ≠ paid" covered | ✅ |
paypal | PayPal | 🟢 Orders v2, payment in two steps | ⛔ needs vault and separate consent |
Five of the ten can take a recurring charge, which is what makes subscriptions work: see Subscriptions and cron.
Delivery drivers in the core
| Key | Carrier | Status |
|---|---|---|
| — | Flat table: price per currency, weight tiers, free above a threshold | ✅ covers pickup and a city courier, needs no API |
novaposhta | Nova Poshta | 🟢 pricing, branch directory, waybill and tracking |
ukrposhta | Ukrposhta | 🟢 pricing, address classifier, waybill and tracking |
Both issue waybills. Note what the ✅ on the first row does and does not claim: the shop's own abilities — the driver layer, the registry, pickup-point selection, the order snapshot, the fallback to the table — are passed by hand without a live carrier. The 🟢 on the two drivers is about the contracts, and we have none.
Cash registers
| Key | Register | Status |
|---|---|---|
atol | ATOL Online v4 (54‑ФЗ, Russia) | 🟢 written from a working ATOL client, not from a retelling |
checkbox | Checkbox (ПРРО, Ukraine) | 🟢 no ПРРО account on our side |
See Receipts.
Next
- Settings — every system setting with its default
- Subscriptions and cron — the most expensive default in the shop