Payment Gateway v6.2.2

Release Date: August 27, 2026 Tags: LANDING-PAGE, RENDERING, SEO, BUG-FIXES

Overview

A public-page rendering release. The gateway's marketing page was assembled entirely in the visitor's browser, so the HTML the server actually sent had none of the page's numbers in it — and that is all a crawler or a link-preview bot ever saw. The page is now built on the server.

One consequence is worth knowing: the page now waits on an internal call while it is being built, so while the backend is wedged the public page can be slow to start rendering rather than quick to show placeholders. It never fails outright.

Requires Core v6.7.3.

Update Instructions

pnpm updator

Ship the frontend build. There is no backend change, no database change and no configuration.

Fixed

The public gateway page arrived with none of its numbers in it

Every figure on the page was fetched by the visitor's browser after the page had already painted. The HTML the server sent carried no merchant count, no transaction count, no processed-volume figure and no success rate anywhere on it, and the fee rate, the supported-currencies grid and the activity feed were grey placeholder bars. That was the whole of what any crawler or link-preview bot that does not run JavaScript ever saw. A visitor got it too for the first beat, and then the four-figure statistics row appeared out of nowhere and pushed every section beneath it down the page by its own height, while the three figures under the headline landed the same way and jolted the headline, subtitle and both buttons with them.

• Fixed the public gateway page rendering without its statistics row and with skeleton fee, currency and activity sections. The page is assembled on the server, so the real numbers are present and settled in the first paint.
• If the platform's own backend cannot be reached while the page is being built, nothing errors and no failure text reaches the visitor — the page falls back to filling itself in from the browser, exactly as it did before.
• Building the page waits on that internal call, which gives up after ten seconds.