Plenix 2026.09.6 — Payment errors that tell you how to fix them

Release 2026.09.6 makes payment-provider problems easy to fix, and puts company payment settings under their own permission.

New features

Test your GoCardless connection

• Accounting → Settings → GoCardless has a new Test connection button. It shows whether you are connected to Sandbox or Live and the name of your GoCardless account, or tells you exactly what to fix.

Company Payment Settings is its own permission

• Company Payment Settings (default payment terms, payment method, credit limit and credit hold on a company) now appears in Settings → Roles under Billing, so you can choose who can view or change it.
• By default, Finance and HR Manager can change it and Director cannot see it. Administrators always have access.
• People who can view it but not change it see the settings read-only.

Improvements

Payment errors say how to fix them

• When setting up a Direct Debit mandate or taking a payment fails because of a GoCardless or Stripe setting, Plenix now explains the problem in plain language. The error includes a link to the setting to change and a How to fix this guide.
• Common problems are caught before anything is sent to the provider: a key that isn't a GoCardless token, a Sandbox token with the environment set to Live (or the other way round), a read-only token, or an account GoCardless hasn't verified yet.
• The Direct Debit tab on a company warns you about a setup problem as soon as you open it, not only when you click Set Up Mandate.
• GoCardless and Stripe keys are checked when you save them, so a wrong key is rejected straight away.

Fixes

• Browsers and password managers no longer fill saved passwords into the GoCardless and Stripe key fields.
• After you save Accounting settings, the form keeps showing your saved keys masked instead of the text you typed.

Security

• Payment provider links on a company can only be set by the Stripe and GoCardless setup flows, not by editing the company directly.