Weave Code
Billplz Laravel Package
jomweb/billplz
A Laravel package for integrating Billplz, the Malaysian payment gateway. Create and manage bills, redirect customers to secure payment pages, and handle callbacks/webhooks through a clean, configurable API. Supports sandbox and production environments for fast checkout flows.
PHP framework agnostic library for working with BillPlz API v3 and beyond...
Frequently asked questions about Billplz
- Is jomweb/billplz a Laravel package or a framework-agnostic PHP client?
- The TPM assessment classifies jomweb/billplz as a framework-agnostic PHP client, not a Laravel package. It has no ServiceProvider, facade, publishable config, migration stubs, or Laravel-native testing helpers. In Laravel you should add a small integration layer: config/billplz.php, a singleton binding in AppServiceProvider, and a domain-level PaymentGateway adapter.
- How do I install and configure jomweb/billplz in a Laravel application?
- Install it with Composer and supply the Billplz API key, collection ID, sandbox toggle, and callback/redirect base URLs through environment variables. Because the package does not publish Laravel config or bind itself, create config/billplz.php and register a configured singleton client in AppServiceProvider. Keep the client behind an adapter rather than injecting it directly into controllers.
- Does jomweb/billplz support Laravel 10, 11, and 12?
- Because jomweb/billplz imposes no framework coupling, it should not pull Laravel into a version conflict. Confirm its Composer PHP minimum matches your runtime, such as PHP 8.1+ for Laravel 10/11/12. You still need to build the Laravel wiring yourself, since there are no framework helpers.
- Which Billplz endpoints and features does jomweb/billplz cover?
- The expected integration surface is creating a bill with collection ID, amount in cents, customer details, callback URL, redirect URL, and optional reference fields, plus retrieving and deleting bills. It should also generate payment URLs or redirect responses and verify callback x_signature values. Before committing, confirm which endpoints are wrapped, whether bill retrieval returns paid, paid_at, state, and paid_amount, and whether newer payment-order flows require raw calls.
- How should Laravel handle Billplz callbacks and webhooks with jomweb/billplz?
- Treat Billplz callbacks as untrusted, form-encoded POSTs that may be retried. Verify the x_signature, enforce idempotency, and re-fetch the bill server-side before marking an order paid. The package can help verify signatures but cannot enforce these application-level safeguards or fix a misconfigured callback URL.
- Can jomweb/billplz be used safely in production?
- It can be a reasonable production dependency because it is MIT licensed, low churn, and thin enough to fork or vendor if maintenance stalls. The main risks are a small maintainer base, possible Billplz API version drift, and security correctness living in your application. Budget for a sandbox spike and explicit acceptance criteria around signature verification, idempotency, and server-side reconciliation.
- How do I test a jomweb/billplz integration without live Billplz keys?
- Start with the Billplz sandbox and separate sandbox keys for a one-day spike. Check whether the package's test suite mocks the HTTP transport or requires live sandbox credentials. Abstract the client behind a PaymentGateway interface so you can fake bill creation, payment redirects, and callback verification in Laravel tests.
- Does jomweb/billplz conflict with Laravel's Guzzle version?
- The TPM assessment flags HTTP transport as a key question: confirm whether jomweb/billplz accepts an injectable PSR-18 or HTTPlug client. If the transport is swappable, you can avoid fighting Laravel's bundled Guzzle and your PHP version matrix. If it is hard-wired, test the dependency resolution before adopting it.
- What are alternatives to jomweb/billplz for Billplz payments?
- The provided context does not name direct alternatives, so evaluate other maintained Billplz SDKs and the official Billplz API directly. Because jomweb/billplz is a thin client, calling Billplz yourself with Laravel's HTTP client and wrapping it in a PaymentGateway adapter is a viable alternative. Compare maintenance activity, signature verification support, and Billplz endpoint coverage before choosing.
- Who maintains jomweb/billplz and is it actively maintained?
- The context describes a small maintainer base and around 77 GitHub stars, which means community-grade support rather than vendor-backed SLAs. A recent release is reassuring, and the low opportunity delta suggests a stable, low-churn package. Ask about historical issue response times, and remember the MIT license lets you fork and vendor the code if needed.
Weaver
How can I help you explore Laravel packages today?