Configure Payment Processors
Payment processors are the gateway between your workshop and the card networks, bank transfer rails, and digital wallets your customers use to pay. Before you can accept card payments or send payment links, at least one processor must be activated and configured with valid credentials.
This guide covers activating processors, enrolling API keys, setting the default processor, enabling test mode, and copying webhook URLs.
Who can do this: Account Owners and Org Admins only. All other roles see a read-only view of processor status.
Understand the Processors screen
Navigate to Settings → Processors. You will see three processor cards arranged vertically:
| Processor | Supported methods | Credentials required |
|---|---|---|
| Mock | Card, Bank Transfer | None (built-in test processor) |
| Stripe | Card, Bank Transfer, Wallet | Yes (API key) |
| PayTabs | Card, Bank Transfer | Yes (API key) |
Each card displays:
- Active toggle — whether the processor is enabled for this location
- Default badge — which processor is used when no specific processor is selected at payment time
- Test Mode toggle — route transactions to the processor’s sandbox environment
- Credential status — green dot (enrolled) or yellow dot (not enrolled)
- Webhook URL — the endpoint your processor needs to call for payment status updates
- Supported payment methods — shown as badges (Card, Bank Transfer, Wallet)
The Mock processor requires no API credentials and is always available. Use it during initial setup, staff training, and integration testing. It simulates successful payments without touching any real payment network.
Activate a processor
Open Settings
From the main navigation, go to Settings → Processors.
Locate the processor card
Find the card for the processor you want to activate (Mock, Stripe, or PayTabs).
Toggle Active
Switch the Active toggle to the on position. The card border changes to indicate the processor is now enabled for this location.
If the processor requires credentials and none have been enrolled, the card will show a yellow dot next to the credential status. You can activate the processor first and add credentials afterward, but it will not process live payments until credentials are in place.
Save
Changes save automatically. A brief confirmation appears when the update is persisted.
Add API credentials
API keys connect BayWise to your processor account. Credentials are stored in the Vault — an encrypted store that never reveals the key after it has been saved. You will not be able to view or copy a key once enrolled; if you need to rotate it, you enroll a new one.
Confirm your role
Only Account Owner and Org Admin roles can enroll credentials. If you do not see the credential input field, check your role with your account owner.
Open the credential enrollment form
On the processor card, look for the API Key section. If no key is enrolled, you will see a password-type input field and an Enroll button.
Enter the API key
Paste the API key from your processor’s dashboard into the input field. The field masks the value as you type.
For Stripe, this is the secret key from your Stripe Dashboard (begins with sk_live_ or sk_test_). For PayTabs, this is the server key from your PayTabs merchant portal.
Click Enroll
Click Enroll. BayWise sends the key to the Vault for encrypted storage. On success, the credential status dot changes from yellow to green.
The API key is write-only. Once enrolled, the original value cannot be retrieved or displayed. If you need to change the key — for example, after rotating credentials in your processor’s dashboard — enroll the new key. It will replace the previous one.
Verify the status dot
After enrollment, the green dot confirms the key is stored. The processor is now ready to handle live transactions (or test transactions if Test Mode is on).
Set the default processor
The default processor is used whenever a payment is recorded without explicitly selecting a processor. Only one processor can be the default at any time.
Open Settings → Processors
Navigate to the Processors settings tab.
Toggle Default on the desired processor
Click the Default toggle on the processor you want to make the default.
BayWise performs an atomic swap: it sets your chosen processor as the default and unsets all others in a single operation. You do not need to manually turn off the previous default — it happens automatically.
Confirm the change
The Default badge moves to the newly selected processor card. The previous default processor remains active but is no longer the fallback.
Most workshops set Stripe or PayTabs as the default for production and keep Mock active only for test mode. You can have multiple processors active simultaneously — for example, Stripe for card payments and PayTabs for region-specific bank transfers — but only one can be the default.
Configure the webhook URL
When a customer completes a payment link or a processor sends an asynchronous status update (refund processed, dispute opened), the processor calls a webhook URL on your BayWise instance. This URL is auto-generated and read-only.
Find the Webhook URL field
On each processor card, the Webhook URL field displays the full endpoint. The format is:
https://<your-domain>/webhooks/<processor>/<location-id>Copy the URL
Click the copy icon next to the URL. The URL is copied to your clipboard.
Paste in your processor’s dashboard
Log in to your processor’s dashboard (Stripe Dashboard or PayTabs Merchant Portal) and navigate to the webhook configuration section. Paste the copied URL as the endpoint for payment events.
For Stripe, this is under Developers → Webhooks → Add endpoint. For PayTabs, this is under Developers → Transaction API → Webhook URL.
The webhook URL includes your location ID. If you manage multiple locations, each location has its own webhook URL. Copy the correct one for each location and configure it in your processor’s dashboard separately.
Enable test mode
Test mode routes all transactions through the processor’s sandbox environment. No real money moves, no real cards are charged.
Toggle Test Mode
On the processor card, switch the Test Mode toggle to on.
Use test credentials
When test mode is active, use the test API key from your processor (e.g., Stripe’s sk_test_ key). If you enrolled a live key, test mode still sends requests to the sandbox — but the processor may reject them if the key type does not match the environment.
Run test transactions
With test mode on, record payments as normal. They will appear in your transaction history with a test indicator. Test transactions do not affect your live financial reports.
Turn off test mode for production
When you are ready to accept real payments, switch Test Mode off. Ensure your live API key is enrolled and the webhook URL is configured in your processor’s production settings.
Multi-location template management
If your organisation uses template management for standardised configuration across locations, processor settings support the template workflow.
The template captures the active, default, and test mode state of each processor. Credentials are intentionally excluded from the template — API keys are location-specific secrets and must be enrolled individually at each location.
When a location’s processor configuration diverges from the published template, a Template Managed banner appears at the top of the Processors tab. From there, you can:
- Reset to template — restore the location’s active/default/test-mode settings to match the template. Credentials are not affected.
- Keep local changes — dismiss the banner and continue with the location’s custom configuration.
Template resets never touch API credentials. Even after a reset-to-template, each location retains whatever key was enrolled in its Vault. You only need to re-enroll credentials if you are rotating keys at the processor level.
Common questions
Can I have multiple processors active at the same time? Yes. You can activate all three processors simultaneously. The default processor is used when no specific processor is selected during payment recording. Staff can override the processor on a per-transaction basis if multiple are active.
What happens if I deactivate a processor that has pending payment links? Deactivating a processor does not cancel outstanding payment links. Links already sent will continue to work until they expire. New payments will not be routed to a deactivated processor.
How do I rotate an API key? Enroll the new key using the same credential input field. The new key replaces the old one in the Vault. There is no need to deactivate the processor during rotation — the swap is atomic.
Why is the Mock processor available in production? Mock is a development and training tool. It is safe to leave it active — it will only be used if explicitly selected or if it is set as the default. For production, set a real processor as the default.
Can location managers configure processors? No. Processor configuration is restricted to Account Owners and Org Admins. Location managers see a read-only view of processor status.
Related pages
- Configure Payment Preferences — set your default payment method and currency
- Record a Card Payment — use a configured processor to process a card payment
- Send a Payment Link — generate a link that uses your default processor
- Configure Surcharging — pass processing fees to the customer where permitted