Weave Code
Ti Ext Payregister Laravel Package
tastyigniter/ti-ext-payregister
PayRegister is a TastyIgniter payment extension supporting Cash On Delivery, Authorize Net AIM, PayPal Express, Stripe, Mollie, and Square, with saved payment profiles, refunds, seamless checkout, and easy gateway extensibility.
Payment system for TastyIgniter. Allows you to accept credit card payments using payment gateway supplied by this extension or others.
Frequently asked questions about Ti Ext Payregister
- What is tastyigniter/ti-ext-payregister and what does it do?
- It is the PayRegister payment extension for TastyIgniter, a Laravel-based platform for restaurants and online ordering. It provides a payment system with multiple gateways, payment profiles, refunds, and checkout flows. You install it as a Composer package and configure gateways through the TastyIgniter admin.
- How do I install tastyigniter/ti-ext-payregister with Composer?
- Install it with composer require tastyigniter/ti-ext-payregister, then enable the PayRegister extension in the TastyIgniter admin. Check the official TastyIgniter documentation for any publish or configuration steps. The current release requires PHP 8.1+ and a compatible TastyIgniter version.
- Which payment gateways does PayRegister support?
- PayRegister includes Cash On Delivery, Authorize Net AIM, PayPal Express, Stripe, Mollie, and Square. Stripe and Square support seamless on-site checkout, while other gateways may use offsite redirects. The extension is also designed so you can add your preferred payment gateway.
- Is ti-ext-payregister compatible with Laravel and which PHP version is required?
- It is a TastyIgniter extension, so it runs inside TastyIgniter's Laravel-based application rather than as a standalone Laravel package. The v4.1.2 assessment notes PHP 8.1+ and Stripe SDK v12+ for webhook validation. Check your TastyIgniter version constraints in composer.json before upgrading.
- How do I configure the Stripe webhook secret for PayRegister?
- Create a webhook endpoint in the Stripe Dashboard and copy its signing secret. Set STRIPE_WEBHOOK_SECRET in your .env file or configure stripe.webhook_secret in config/payregister.php. In v4.1.2 this secret is required, and missing secrets cause Stripe webhook validation to fail.
- Why are my Stripe webhooks failing after upgrading ti-ext-payregister?
- Version 4.1.2 enforces mandatory Stripe webhook signature validation, so requests without a valid secret are rejected. Confirm that STRIPE_WEBHOOK_SECRET matches the endpoint secret in Stripe and that the webhook URL is correct. If you use shared or multi-tenant webhook endpoints, review how secrets are managed and clear cached config after changes.
- Can I add a custom payment gateway to PayRegister?
- Yes, PayRegister is designed for extensibility, with each payment provider encapsulated separately. You can add a preferred gateway by following TastyIgniter's payment provider structure and registering it through the extension points. Review existing gateway implementations and the official docs, then test the integration in sandbox mode before production.
- Does PayRegister support refunds and saved payment profiles?
- Yes, the extension supports refunds for payment attempts and payment profiles that save customer payment information for future transactions. Gateway support may vary, so verify refund and tokenization capabilities for your chosen provider. Stripe and similar gateways typically support these features.
- How should I handle queues and webhooks in production with PayRegister?
- Payment webhooks and asynchronous processing may rely on Laravel queues, so run queue:work workers and monitor backlog. Implement retries, logging, and a circuit breaker for webhook routes to handle failed validations gracefully. Because missing Stripe secrets can crash webhook handling, preconfigure secrets and alert on failures.
- What are alternatives or maintenance considerations for ti-ext-payregister?
- Alternatives include building a custom TastyIgniter payment extension or using a Laravel billing approach if your app is not tightly coupled to TastyIgniter checkout. PayRegister is MIT-licensed and maintained in the TastyIgniter GitHub organization, but you should track releases for breaking changes such as the Stripe webhook secret requirement. For production, plan secret rotation and test upgrades against payment sandboxes.
Weaver
How can I help you explore Laravel packages today?