- How do I install BD-Courier-Fraud-Checker in my Laravel project?
- Use Composer to install the package with `composer require programmertowheed/bd-courier-fraud-checker`. The package is Laravel-native, so it integrates via service providers and facades. Check the README for specific Laravel version requirements (PHP 8.x+).
- Does this package work with Laravel 10 or 11?
- The package supports Laravel 9+ and PHP 8.x+. While Laravel 10/11 may not be explicitly tested, the core Laravel dependencies (e.g., HTTP clients, service container) are backward-compatible. Verify the latest release notes for updates.
- What kind of data does the fraud checker validate (addresses, phones, etc.)?
- The package checks Bangladeshi courier data, including fake addresses, blacklisted customers, and suspicious patterns like mismatched phone-area codes. Inputs typically include customer addresses, phone numbers, and order details. Exact fields depend on the dataset.
- Can I use this package without storing local fraud datasets?
- Yes, if the package supports API-based checks, you can avoid local storage. However, the README doesn’t explicitly confirm API access—review the codebase or contact the maintainer to confirm. Local DB syncs may require manual updates.
- How often is the fraud dataset updated, and who maintains it?
- The package relies on external Bangladeshi courier data, but the update frequency isn’t specified in the README. Check the GitHub issues or contact the maintainer for SLAs. If crowdsourced, updates may be irregular; government-backed data could be more reliable.
- What happens if the fraud-check service is down during an order?
- The package likely defaults to a fail-open or fail-closed strategy, but this isn’t documented. Implement retry logic or a fallback (e.g., cache results or log errors) in your Laravel middleware. Test edge cases during integration.
- Can I customize fraud rules (e.g., add new courier patterns)?
- The package appears modular, but customization depends on its architecture. If it uses a local DB, you can extend tables. For API-based checks, verify if the service supports custom rules. Review the source code for hooks or configuration options.
- Is there a rate limit or cost for API usage if I use this package?
- The README doesn’t mention API rate limits or costs. If the package relies on external APIs, check the provider’s terms. For local DB usage, costs are minimal (just server resources). Always confirm before production deployment.
- How do I handle false positives (e.g., legitimate customers flagged as fraud)?
- The package may not include whitelisting tools, but you can override results in Laravel by extending its logic. Log false positives and adjust thresholds or add manual review workflows in your app.
- Are there alternatives for fraud detection in Laravel if this package doesn’t fit?
- For Bangladeshi-specific fraud, consider local APIs like **bKash** or **Nagad** fraud tools. Globally, packages like **spatie/laravel-fraud-detection** or **laravel-fraudster** offer broader coverage. Evaluate based on dataset reliability and integration effort.