fzengin19/laravel-subscription-guard

This is my package laravel-subscription-guard

V1.0.2 2026-04-07 12:59 UTC

Requires

• php: ^8.4
• illuminate/contracts: ^11.0||^12.0||^13.0
• iyzico/iyzipay-php: ^2.0
• spatie/laravel-package-tools: ^1.16
• spatie/laravel-pdf: 1.5||^2.0

Requires (Dev)

• larastan/larastan: ^3.0
• laravel/pint: ^1.14
• nunomaduro/collision: ^8.8
• orchestra/testbench: ^10.0.0||^9.0.0
• pestphp/pest: ^4.0
• pestphp/pest-plugin-arch: ^4.0
• pestphp/pest-plugin-laravel: ^4.0
• phpstan/extension-installer: ^1.4
• phpstan/phpstan-deprecation-rules: ^2.0
• phpstan/phpstan-phpunit: ^2.0

MIT

• fzengin19

• laravel
• fzengin19
• laravel-subscription-guard

README

Laravel Subscription Guard is a Laravel package for subscription billing, payment-provider integration, and license lifecycle management.

It combines:

• iyzico and PayTR provider adapters
• centralized billing orchestration
• webhook and callback intake
• license generation and validation
• feature and limit gating
• operational commands for renewals, dunning, plan changes, and license sync

What The Package Covers

The current package surface includes:

• provider-managed and self-managed billing paths
• subscription creation, renewal, cancellation, and scheduled plan changes
• webhook persistence, idempotency, and async finalization
• 3DS and checkout callback intake
• license activation, revocation, heartbeat, and online validation
• seat-based and metered billing support
• invoice and notification pipeline hooks
• isolated iyzico live sandbox validation

Provider Model

The package supports two billing ownership models:

• iyzico: provider-managed recurring billing, with local state updated from webhook and callback results
• paytr: package-managed recurring billing, with the package running renewal and retry orchestration

See Providers for the current provider overview.

Provider-specific integration docs:

• iyzico Provider
• PayTR Provider

Install And Start

Install the package:

composer require fzengin19/laravel-subscription-guard
php artisan vendor:publish --tag="laravel-subscription-guard-config"
php artisan vendor:publish --tag="laravel-subscription-guard-migrations"
php artisan migrate

Then continue with:

• Installation Guide
• Quickstart
• Configuration Reference

Core Commands

The package currently exposes these core operational commands:

php artisan subguard:process-renewals
php artisan subguard:process-dunning
php artisan subguard:suspend-overdue
php artisan subguard:process-plan-changes
php artisan subguard:process-metered-billing
php artisan subguard:simulate-webhook paytr payment.success
php artisan subguard:simulate-webhook iyzico payment.success
php artisan subguard:sync-license-revocations
php artisan subguard:sync-license-heartbeats
php artisan subguard:generate-license 1 1
php artisan subguard:check-license <signed-license-key>

Route and command surface summary lives in API.

Queue Topology

Default queues are isolated by concern:

• billing jobs: subguard-billing
• webhook finalization jobs: subguard-webhooks
• notifications: subguard-notifications

Queue names are configurable under subscription-guard.queue.

First Local Validation Path

For a safe local first-success path, start with install + migrate and then use simulated webhook intake:

php artisan subguard:simulate-webhook paytr payment.success
php artisan subguard:simulate-webhook iyzico payment.success

That validates the local webhook intake and finalization path without requiring real provider credentials.

Testing

composer test
composer test-live
composer analyse
composer format -- --test

• composer test runs the deterministic suite.
• composer test-live runs the isolated iyzico sandbox suite under tests/Live.

Documentation

Getting Started

• Installation
• Quickstart
• Configuration
• FAQ

System Reference

• Architecture
• Domain Billing
• Domain Licensing
• Domain Providers
• Data Model
• Events And Jobs

Providers and Integration

• Providers
• iyzico Provider
• PayTR Provider
• Custom Provider
• API
• Webhooks
• Callbacks
• Licensing

Billing and Licensing Flows

• Dunning And Retries
• Metered Billing
• Seat-Based Billing
• Invoicing

Runtime and Operations

• Commands
• Queues And Jobs
• Security
• Troubleshooting

Testing

• Testing
• Live Sandbox

Guides and Contributor

• Recipes
• Use Cases
• Contributing

Internal planning docs live under docs/plans/.

Safety Notes

Bank installment flags and application-level recurring collection are not the same thing.

If you need true multi-period manual collection, model it as your own scheduled billing flow instead of assuming provider installment settings create that behavior automatically.

Do not put real credentials into repository docs or example files.

License

MIT