Settings

The dashboard’s Settings page is the master config surface. Everything from brand colour to webhook URLs to tracking-pixel IDs lives here. Heavy page — 40+ fields grouped into sections.

This is distinct from the WordPress plugin settings (in your WP admin at WooCommerce → Swft Checkout). See Plugin Settings for those.

Sections

Store identity

• Store name — shown in the checkout header.
• Store URL — the URL Swft redirects shoppers to on cancel / back navigation.
• Logo — uploaded to Swft’s R2 bucket; rendered in the checkout header. SVG preferred, PNG with transparent background fine.
• Brand colour — your primary accent. Sets button background, link colour, focus ring.
• Support email — shown in the footer and on error screens.
• Localisation — currency, timezone, language fallbacks.

Custom domain

If you want the checkout on checkout.yourstore.com instead of checkout.swft.co.uk:

1. Add the domain here.
2. Swft shows the DNS records you need: a CNAME pointing at checkout.swft.co.uk.
3. Add the records in your DNS provider.
4. Click Verify. Swft issues an SSL cert (free, via Let’s Encrypt) and the domain is live.

See Custom Domains for the deep dive.

Payments

Per-gateway credentials and toggles. See the Payment Gateways section for setup of each.

Recovery emails

When a shopper abandons their cart, Swft can send a series of recovery emails:

• Email 1 — 1 hour after abandonment (default).
• Email 2 — 24 hours.
• Email 3 — 3 days (final reminder, often with a discount code).

Each email has:

• Subject line with placeholder support (e.g. \{\{customer.firstName\}\}).
• Body (rich-text editor with placeholders for cart items, return URL, discount code).
• Live preview.

You can also configure a single transactional sender domain (must be verified with Resend / SendGrid / whoever you use) — recovery emails go out from [email protected] rather than Swft’s generic sender.

Webhooks

• Webhook URL — your endpoint. See Webhooks Reference.
• Webhook secret — used to sign every outgoing request. Click Regenerate to rotate.
• Subscriptions — optional event-specific filters. Leave empty to send every event.
• Test event — fires a synthetic order.completed to your URL. Use to confirm signature verification works.
• Failed deliveries — list of webhook attempts that didn’t return 2xx after retry. Inspect, resend, or mark resolved.

Tracking pixels

Server-side tracking pixels Swft fires on every order:

• Meta Conversions API (CAPI) — Facebook / Instagram. Paste your Pixel ID and access token.
• Google Analytics 4 — Measurement ID and API secret.
• TikTok — Pixel ID and access token.
• Google Ads — conversion ID and label.
• Reddit Pixel — advertiser ID.

Server-side pixels fire from Swft’s API, not from the browser, which means:

• They bypass ad blockers.
• They don’t require cookie consent (technically — verify with your DPO).
• They aren’t slowed by client-side load.

Custom fields

Define merchant-specific fields shown on the details step:

• Field name — internal name (e.g. business_size).
• Label — what the shopper sees.
• Type — text / email / phone / select / radio / textarea.
• Options (for select / radio) — comma-separated.
• Required — toggle.
• Section — details / shipping / payment — where the field renders.

Custom field values appear on the resulting WC order’s meta and on every webhook payload.

B2B mode

Toggle B2B mode for the entire store. When on:

• Company name and VAT number fields appear on the details step.
• VIES + HMRC VAT validation is enabled.
• PO number and Net payment terms can be requested.
• KYC settings become relevant.

Address autocomplete

Pick a provider:

• Google Places — paste your Maps API key. Best coverage globally.
• SmartyStreets — US-focused; better for US-heavy stores.
• None — disable address autocomplete; shoppers type addresses manually.

Tax automation

Configure tax calculation:

• None — your WooCommerce tax rules are honoured (default).
• Avalara — Avalara AvaTax integration; paste your account / licence key.
• TaxJar — TaxJar API key.

API keys

The Swft API key that the Swft Checkout WordPress plugin uses to authenticate session creation. Keep this secret; regenerate if compromised.

Saving

Each section has its own Save button. Saving is idempotent — re-saving an unchanged section is a no-op.

Some changes (logo upload, custom domain) take a few seconds to propagate. Other changes are instant.

Gotchas

• Webhook secret rotation is hard. When you regenerate, in-flight deliveries fail signature verification. Coordinate with your endpoint’s deployment.
• Custom field changes don’t migrate. Renaming a field doesn’t update past orders’ meta. Plan field schemas upfront.
• Tax automation is opinionated. Avalara / TaxJar override your WC tax rules entirely. Test thoroughly before relying.
• Logo upload doesn’t optimise. Upload a sensibly-sized SVG or compressed PNG. A 5MB photo will load 5MB on every checkout.