Payments & Compliance.
Evidence-backed comparisons and operating guides for subscription gateways, tokens, SCA, webhooks, tax, Merchant-of-Record choices, and payment compliance.
- Choose the renewal and Merchant-of-Record architecture first
- Test tokens, authentication, webhooks, refunds, and recovery
- Assign operational, tax, and compliance ownership explicitly
About this topic
A subscription payment system is more than a checkout form. It decides who initiates each renewal, where the reusable payment authority lives, how an off-session charge is authenticated, which events update WooCommerce, how customers replace a failed method, and who owns tax, refunds, disputes, and compliance. These guides make those responsibilities explicit before a merchant commits to a gateway or migration.
Start with the gateway comparison, then use the focused Stripe, PayPal, Paddle, manual-billing, SCA, token, webhook, and tax guides to test the exact architecture. Product behavior is verified against current ArraySubs releases and provider documentation, operational limitations are visible, and legal or tax questions are clearly separated from software behavior so engineering, finance, support, and leadership can make one defensible decision together.
Browse the library
Payments & Compliance guides
Showing 7–8 of 8 articles
SCA and 3D Secure for Subscription Renewals
Understand how authenticated setup, off-session renewal, issuer challenges, pending recovery, webhook evidence, and gateway ownership fit together.
Subscription Payment Tokens and Card Updates Explained
Understand provider-vault references, subscription-specific payment context, customer and network updates, portability limits, and renewal verification.