- How do I install glennraya/xendivel in a Laravel application?
- Install it with Composer using composer require glennraya/xendivel. The package registers a standard Laravel service provider and facade, and you publish its config file so you can add your Xendit API key and related settings. After publishing, set your credentials in the environment file and you can call the facade directly from your application code.
- Which Laravel and PHP versions does Xendivel support?
- Xendivel is built as a standard Laravel package with a service provider, facade, and publishable config, so it follows normal Laravel package conventions. The exact PHP and Laravel version constraints are defined in the package composer.json, so check that file or the repository before upgrading. Version 3.2.0 is the release that adds QR payment support through Xendit's Payments API.
- How do I configure Xendivel for QR code payments?
- Publish the package config and set the QR-related keys, including qr_webhook_url, qr_channel_code which defaults to QRPH, and qr_currency which defaults to PHP. These defaults target the Philippine market but can be overridden per request when you need a different channel or currency. You create QR codes through the facade using calls such as Xendivel::createQrCode.
- Does Xendivel support static and dynamic QR codes?
- Yes, QR payments are created through Xendit's Payments API, and the package supports the static QR mode that maps to MULTIPLE_USE. With static QR the payer supplies the amount, so the amount and payer identity are not known when you create the code. Your order matching therefore has to reconcile from the webhook payload rather than from your own initiation record.
- How does Xendivel handle Xendit webhooks?
- Xendivel ships publishable event and listener stubs plus webhook URL configuration so you can wire Xendit callbacks into your Laravel app. Because QR confirmation is asynchronous, the webhook is the source of truth and you should treat signature verification, replay idempotency, and event ordering as load-bearing. Confirm that the shipped listener verifies the Xendit callback token rather than relying only on CSRF exclusion before going live.
- What does the xendivel upgrade command do and is it safe to run?
- The upgrade command uses --force on the xendivel tag, which will overwrite published config, templates, and event or listener stubs that you may have customized. Treat it as destructive and avoid running it blindly in an existing project. The safer path is to diff the published files against your committed copies and merge new keys by hand.
- How can I test Xendivel QR payments without hitting Xendit?
- The package includes a simulateQrPayment helper that automatically resolves pr- payment request IDs versus raw QR strings, which removes a common source of test-harness bugs. This is useful for exercising your listener and order-matching logic locally. Treat getQrCode polling as a convenience rather than a production fallback, and check Xendit's rate limits before relying on it.
- Is Xendivel suitable for production payment reconciliation?
- Xendivel is a stateless wrapper and does not own payment state, which keeps it out of your domain model but means reconciliation is your responsibility. For asynchronous methods such as QR, the webhook is the source of truth, so you must implement signature verification, idempotency on replay, and correct event ordering. It fits well where payments support your product rather than being the core domain.
- Can I use Xendivel for payouts and disbursements?
- Yes, Xendivel offers a fluent API covering invoices, virtual accounts, e-wallets, retail outlets, QR codes, and disbursements. That means you can handle both collections and payouts through the same Laravel wrapper without adding a separate SDK for each flow. Check the repository for the exact methods available for your release.
- What are the alternatives to Xendivel for Xendit in Laravel?
- The main alternative is using Xendit's official SDK directly and wrapping it in your own service classes, which gives you full control but more boilerplate. Xendivel's value is the Laravel-friendly facade, publishable config, and webhook stubs. Evaluate the maintenance activity and open issues before committing, since payment integrations depend on timely updates.