Skip to content
30% offPricing Plans

Keep the money flowing — gateway health

A broken webhook can silently stop renewals — monitor every gateway’s status and webhook activity from one screen.

  • Gateway status
  • Webhook event log
  • Catch silent failures
Start Trial
No credit card required
ProMeasure & grow

Automatic revenue depends on healthy gateways and working webhooks — and a broken webhook fails silently. The Gateway Health Dashboard (Pro) shows each gateway’s connection status, per-gateway subscription counts, last-webhook timestamp, capabilities, and a webhook event log. This recipe helps you catch a gateway problem before renewals quietly stop.

What you get
  • Confirm each gateway is connected and receiving webhooks.
  • See per-gateway active subscription counts.
  • Catch a stale ‘last webhook’ before renewals fail.
  • Diagnose missing-renewal incidents fast.
Copy these settings

The exact configuration

Enter these values and you have the setup live. Every field maps to a real ArraySubs setting.

SettingValue
WhereAdminArraySubs → Settings → Payment Gateways (Pro)
Per-gateway cardGateway HealthStatus · subscription count · last webhook · capabilities · webhook URL
StatusesGateway cardConnected · Connected (Test) · Needs Setup · Disabled · Unavailable
Webhook event logGateway HealthGateway · event ID · type · processed-at (filterable)
Best for

When to use this setup

Stores on automatic payments (Stripe/PayPal/Paddle)
After a site migration or URL/SSL change
Diagnosing missing or failed renewals
Set up

Set it up in 2 steps

A step-by-step guide drawn from the ArraySubs user manual. Open the linked page for the full walkthrough and screenshots.

  1. Open Gateway Health

    Go to ArraySubs → Settings → Payment Gateways (Pro) to see a status card per gateway.

    Gateway Health

  2. Verify status and webhooks

    Confirm each gateway shows Connected, expand for the webhook URL and capabilities, and check the event log and ‘last webhook’ timestamp.

    Gateway Health
From the manual

This recipe is built from these ArraySubs user-manual guides:

Good to know

Notes & edge cases

A ‘last webhook = Never’ or a long-stale timestamp often means a webhook config problem — a common silent cause of missed renewals.
Webhook events are retained ~30 days; the log can’t be cleared manually.
Check after any migration, URL change, SSL update, or gateway config change.
Built with

Modules behind this recipe

The ArraySubs modules this setup relies on.

Pro

Gateway Health

Monitor gateway connections, subscription counts, webhook URLs, capabilities, and webhook event logs. Pro only.

Free + Pro

Billing and Renewals

How ArraySubs creates, schedules, communicates, and collects recurring payments from first invoice to final renewal.

More recipes

Related setups to explore

Other configurations you can build with the same modules.

Pro

Monitor background jobs

Watch renewals, trial conversions, and reminders run — catch a failed job before it costs you revenue.

Pro

Activity audit trail

Know who changed what — a searchable log of every subscription, settings, payment, and access change. Protect the business as you scale.

Free + Pro

Automatic Stripe billing (SCA)

Collect every renewal automatically and off-session with Stripe, fully SCA / 3D Secure compliant.

FAQ

Questions, answered

Often a broken webhook after a migration or URL change. Gateway Health shows a stale ‘last webhook’ and the event log so you can spot and fix it.

All registered gateways (Stripe, PayPal, Paddle), including disabled ones, with per-gateway status, capabilities, and webhook history.
Paid Pro plans

Unlock the complete Pro stack

Start on the free-forever core today, then choose a paid Pro plan when you need the advanced Pro feature set.

Start Trial

No credit card required · Annual and lifetime options available