Connectors

External systems NextWave links to from inside your WordPress site — payments, wallets, NFC, email, and campaigns.

A connector is an external system NextWave links to from inside your WordPress site — Stripe, a wallet provider, your NFC card stock, your email platform. You configure each one site-wide in WP admin, and NextWave surfaces its state and actions through the nwp/v1 API. A connector that isn't configured, or is gated off by your license tier, returns a typed error rather than silently doing nothing.

Configure a connector

Connectors are set up by an administrator in WordPress, not through the CLI. In WP admin, open NextWave and pick the relevant page:

Connector	WP admin page
Stripe payments / subscriptions	NextWave → Payment Integrations
Email platform	NextWave → Email Integration
Wallets, NFC, campaigns, renewals	NextWave → Settings

Credentials and webhook secrets are stored server-side on your WordPress install — they never pass through the CLI, the MCP server, or your shell history.

Supported connectors

Connector	Surface	Used for
Stripe	Payment Integrations	Payments, subscriptions, renewal billing, and inbound webhooks
Email integration	Email Integration	Syncing members to your email platform for lifecycle messaging
Apple Wallet	Settings	Membership passes tied to a member and their tier
Google Wallet	Settings	Membership passes tied to a member and their tier
NFC cards	Settings	Mapping a physical card UID to a member for tap-to-identify
Renewal automation	Settings	Scheduled renewal-reminder messaging as memberships approach expiry
Signup / QR campaigns	Settings	QR-driven signup flows and hosted landing pages

How connectors surface in the API

Once configured, a connector shows up as ordinary nwp/v1 resources. An NFC card, for example, is just a UID you can resolve to a member — the connector is what keeps that mapping current:

$ nwp nfc-cards lookup 04A2B3C4 --output json

If the connector isn't set up, or your tier doesn't include it, the same call returns a typed failure (nwp_feature_disabled or a 404) you can branch on. See Troubleshooting for the full code map.

Check readiness

Confirm which connectors are wired up before you depend on them. Reading settings requires nwp_manage_settings:

$ nwp settings get --output json

And see which license-gated features are actually enabled on this site:

$ nwp feature-flags list --output json

Some connectors are tier-gated

License tiers (Free / Surf / Pipeline) gate some connectors. A call against a connector your tier doesn't include returns nwp_feature_disabled — upgrade the tier or enable the feature in WP admin to unlock it.