Weave Code
Simplepay Laravel Package
netipar/simplepay
Laravel/PHP integration for the SimplePay payment gateway. It helps you initiate payments, handle callbacks and IPN notifications, and manage transactions through SimplePay's API, making it easier to add SimplePay checkout to your application.
Modern Laravel package for SimplePay online payments — start transactions, handle IPN webhooks, manage card storage, process refunds, Apple Pay, RTP, and more.
Frequently asked questions about Simplepay
- What is netipar/simplepay used for in Laravel?
- netipar/simplepay is a Laravel/PHP integration for the SimplePay payment gateway. It helps you initiate payments, handle callbacks and IPN notifications, and manage transactions through SimplePay's API. It also covers card storage, refunds, Apple Pay, and RTP, so you can add SimplePay checkout without building the API layer from scratch.
- How do I install netipar/simplepay in Laravel?
- Install the package with Composer by running composer require netipar/simplepay. Laravel package discovery should register the service provider automatically; if the package includes config or migration files, publish them as described in the README. Then add your SimplePay merchant credentials to your environment or config before making API calls.
- Which Laravel versions does netipar/simplepay support?
- The package is built for Laravel applications, but the exact Laravel and PHP version constraints are defined in its composer.json. Check that file and the README before installing to confirm compatibility with your app. If you are on an older Laravel release, verify support before using it in production.
- How do I start a SimplePay transaction with netipar/simplepay?
- Use the package's transaction API to create a payment request with the amount, currency, and order details required by SimplePay. The package then helps you redirect or hand off the customer to the SimplePay checkout flow. Persist your own order or transaction reference first so you can reconcile the IPN callback reliably.
- How do I handle SimplePay IPN webhooks in Laravel?
- Register a route in your Laravel application and let the package's IPN handling process SimplePay notifications. Verify the notification, update your order state idempotently, and return the response SimplePay expects. Log payloads for debugging, but avoid storing sensitive card data in your logs.
- Does netipar/simplepay support card storage?
- Yes, the package includes card storage management so you can save and reuse tokenized card references where SimplePay supports it. You should still avoid storing raw card numbers and follow PCI guidance for your application. Check the README for the exact card storage API and configuration options.
- Can I process refunds with netipar/simplepay?
- Yes, the package covers refund processing through SimplePay's API. You will typically call a refund method with the original transaction identifier and refund amount, then handle the API response and any related notifications. Confirm partial versus full refund behavior in the package documentation.
- Does netipar/simplepay support Apple Pay and RTP?
- The package advertises Apple Pay and RTP support alongside standard SimplePay payment flows. Actual availability depends on your SimplePay merchant configuration and the payment methods enabled for your account. Review the README for any extra setup or frontend requirements.
- How do I test netipar/simplepay before going live?
- Check the README for SimplePay sandbox or test credential configuration before using live merchant details. You can exercise IPN handling with simulated webhook requests in Laravel feature tests and assert that your order state updates correctly. Keep live credentials out of automated test environments and log test payloads only in non-production systems.
- What should I check before using netipar/simplepay in production?
- Review the repository's README, release history, and issue activity to confirm current maintenance and Laravel compatibility. For payment-critical code, verify webhook authenticity, idempotent order updates, secure credential storage, HTTPS, and logging or retry behavior for failed IPNs. Pin a known version and have a rollback plan before deploying to production.
Weaver
How can I help you explore Laravel packages today?