Payment gateways
Storing card-payment provider credentials — Stripe, PayPal, Square, Afterpay or a custom gateway.
Settings → Payment Gateways (/operations/settings/payment-gateways). Credentials for a card-payment provider.
⚠️ No screen takes an online payment through these yet. Invoice payments are recorded by hand on Payments. This screen stores the configuration for when one does.
Adding a gateway
Section titled “Adding a gateway”Add Payment Gateway:
| Field | |
|---|---|
| Gateway Type | Stripe, PayPal, Square, Afterpay, or Custom Gateway. |
| Display Name | What staff will see. |
| Environment | Sandbox / Test or Production / Live. |
| Status | Enabled or not. |
| API Key / Publishable Key, API Secret / Secret Key, Webhook Secret | The provider’s credentials. When editing, leave a field blank to keep the stored value. |
| Supported Currencies | e.g. AUD, USD, NZD. |
| Webhook URL | Where the provider should call back. |
Secrets are stored encrypted and never shown again — the card only says Configured or Not Set.
Testing
Section titled “Testing”Test checks the credentials. For Stripe and PayPal it calls the provider; for the others it only confirms that a key and secret are both present. The card shows the last result, or Not yet tested.
Deleting a gateway cannot be undone.