Gateway Charges & Webhooks

This page explains, in plain language, how SubscriptionFlow charges renewals across payment gateways and why webhooks make the whole process reliable.

What this does

“Gateway charges” is the engine behind automatic renewals. When a subscription is due, SubscriptionFlow looks at how the customer originally paid and charges the matching saved payment method — PayPal (vault) or Stripe — off‑session, without needing the customer.

Webhooks are messages a payment provider sends to your site to confirm what happened (for example, “this payment was captured”). SubscriptionFlow listens for these so payments are recorded correctly even if a customer’s browser never returns to your site.

How renewal charging works

On a recurring schedule, SubscriptionFlow gathers subscriptions that are due.
For each, it picks the correct gateway based on the original payment (SubscriptionFlow PayPal, Stripe, etc.).
It attempts an off‑session charge on the saved payment method.
Success → the subscription renews and the license term extends automatically.
Failure → the subscription enters the grace period, and the customer can be prompted to pay before it expires.

This all happens quietly in the background — you only need it configured once.

Why webhooks matter

Without webhooks, a payment is confirmed only when the customer returns to your site after paying. If they close the tab first, the order could be left unconfirmed.

With webhooks configured, the payment provider tells your site directly:

The payment is complete → the order is marked paid automatically.
An order was approved → SubscriptionFlow can capture it server‑side.

The result: no lost or stuck payments, even when customers wander off mid‑checkout.

Setting up the PayPal webhook

The SubscriptionFlow PayPal gateway includes a webhook URL and a Webhook ID field. Add the webhook in your PayPal app for “Checkout order approved” and “Payment capture completed”, then paste the Webhook ID into the gateway settings. Full steps are on the SubscriptionFlow PayPal Gateway page.

Tips & Best Practices

Always configure the webhook. It’s the single most important step for reliable payments.
Test end‑to‑end in sandbox/test mode. Confirm both a first payment and a renewal charge succeed.
Keep a grace period so a failed charge has a chance to recover before access is cut.
Match gateway to renewal method. Customers renew via the method they paid with — make sure that method saves reusable payment details.
Monitor renewals using the Dashboard’s Active/Grace/Expired cards.

Frequently Asked Questions

Do I have to understand webhooks to use this?

No. You just paste a URL and a Webhook ID into your payment provider once. SubscriptionFlow handles the rest.

What happens if I don’t set up the webhook?

Payments still work in most cases, but you risk occasional stuck orders if a customer abandons the return step. Setting the webhook prevents that.

Which gateways can charge renewals?

SubscriptionFlow PayPal (vault) and Stripe, using saved off‑session payment methods.

Is any of this available on the Free plan?

No. Automatic gateway charging is a Pro feature.

Are renewals charged instantly on the due date?

They’re processed on SubscriptionFlow’s recurring schedule around the due time — not necessarily to the exact second.

What if a charge fails repeatedly?

The subscription stays in grace for the configured days, then expires if unresolved. The customer can renew manually in the meantime.