Setting up your payment methods

Payment methods live under Settings → System settings → Payments, and only owners and admins can open that tab. You configure what exists; your team chooses from what you make available to them.

What is supported

This is a fixed list rather than an open one. Each of these needs its own credentials and its own charging code behind it, so an open-ended list would only defer the moment somebody configures something that nothing can actually charge against.

Turning one on and off

Each method is a switch. Turning one on asks for its configuration; turning it off stops anyone selecting it, but keeps everything you entered. Switching a processor back on is one click, not an afternoon of finding the keys again — which is the whole point, because the usual reason to switch one off is that you are trialling another.

Secret fields — transaction keys, security keys, Stripe secret keys — are encrypted before they are stored and are never shown back to you, in the same way a password is not. You can replace one at any time. Non-secret fields like a publishable key or a merchant ID stay visible, because you will want to check them against your processor's dashboard.

Deciding who may use which

Every method carries its own Available to team leads switch, off until you turn it on. Admins can always use every enabled method. That is how you keep a house account, a dealer-only merchant, or a processor you are still testing off the list an agent sees when they raise an invoice.

Withholding a method is enforced, not just hidden. An invoice raised against a method that is not available to the person raising it is refused outright, so the rule holds even for someone working around the screen.