## Problem/Motivation Two things a site owner meets on the administration screens, both left over from how the module grew rather than from a decision. **The pages are filed under Web services.** `/admin/config/services` is where REST, JSON:API and the RSS feed are configured. *Payment settings* and the list of provider accounts sit there beside them, and someone looking for what a payer was charged has no reason to open that section. The four listings (payments, claims, refunds, reversals) hang off the settings form rather than off a section of their own, which is why the accounts link reads as a stray sibling of the settings it is not part of. **"Gateway instance" is not a name a site owner has for anything.** It describes the plugin system rather than the thing being named: an account this site holds at a payment provider. The module's own prose already says *account* everywhere -- the delete form, the runtime requirements, the field descriptions on the account form itself -- and only the symbols still say gateway instance, so the code and the screen disagree about what the entity is. ## Proposed resolution **A `Payments` section of its own, at `/admin/payments`**, the shape core gives every administrative section: a page listing what is under it, and under it *Accounts*, the four listings, and *Settings*. Nothing of this module is left under Configuration. **Rename the config entity to `payment_account`**, all the way through: the entity type id, the config prefix, the five classes, the `@api` interface, the entity labels, the exception text and the French catalogue. The word *gateway* is kept for what it correctly names, the plugin that says how to talk to a provider; an account is one configured use of one gateway, and the two words then mean two different things consistently. The module is pre-1.0 with no released version naming these, so the old names are removed rather than deprecated. Two consequences worth stating: - A site that already holds accounts has them under `kessai.gateway_instance.*` and needs them moved to `kessai.payment_account.*`. There is no release to write an update path from. - `yoyaku` names the route `entity.kessai_gateway_instance.collection` in a help text, and the interface in a test. It gets a companion issue. ## Also fixed here Auditing the branch turned up a crash next door, in a file it touches. The Worldline account form built the locale map's description with a link to the language module's languages page, unconditionally. Building a link to a route the site does not have raises rather than rendering nothing, so on a site with one language -- which does not install that module, and is the ordinary case -- adding or editing a Worldline account answered **500**, and the account could not be configured at all. It has been that way since before the account form existed. Nothing caught it because the only test of that form installs the language module. The link is now made only when there is a page to link to, with the same words either way so there is one sentence rather than two, and a test opens the form on a site without the module. ## User interface changes Administration gains a **Payments** section. `/admin/config/services/kessai` becomes `/admin/payments/settings`, the accounts collection becomes `/admin/payments/accounts`, and the four listings move alongside them. *Gateway instances* reads *Accounts* in the menu, and the entity is labelled *Payment account* wherever it is named. AI-Generated: Yes (Claude Code was used to help draft this issue summary and to write the code and tests on the merge request. I reviewed and ran the work myself before posting it.)