- How do I install 3neti/hyperverge in a Laravel application?
- Install it with Composer by running composer require 3neti/hyperverge in your Laravel project. Then publish the package config and add your HyperVerge credentials and environment settings. Once the config is in place you can call the facade from controllers, jobs, or service classes.
- What HyperVerge checks does this Laravel package support?
- The package wraps HyperVerge's KYC REST APIs and exposes identity verification, face match, and document OCR through a Laravel facade. The package description also lists Aadhaar and PAN checks, so you can add those Indian identity verifications without writing raw HTTP calls. Exact endpoint coverage depends on the methods shipped in the package.
- How do I configure HyperVerge API credentials in Laravel?
- Publish the package config and set your HyperVerge credentials there or, preferably, through environment variables referenced by the config. Keep API keys and secrets out of version control and separate sandbox values from production ones. The config also holds the endpoint and environment settings the wrapper uses for requests.
- How do I call HyperVerge verification endpoints with the facade?
- Access is facade-based: resolve the HyperVerge facade and call the method corresponding to the verification you need, such as an identity check, face match, or document OCR request. Credentials and endpoints come from the published config, so API keys and base URLs are not hard-coded in your controllers. Responses are returned in a consistent, Laravel-friendly format you can validate, log, and act on.
- Which Laravel versions does 3neti/hyperverge support?
- The package targets Laravel and is installed through Composer, so its composer.json constraints define the exact framework and PHP versions it supports. Check those constraints or let Composer resolve them for your application before upgrading Laravel. If you are on an older Laravel release, confirm compatibility first.
- How should I handle HyperVerge API errors and responses in Laravel?
- The package normalizes HyperVerge responses into a consistent, Laravel-friendly format, so you can validate fields and branch on results instead of parsing raw JSON in every controller. Wrap calls in try/catch for transport or API errors and log only the response details you need for auditing. Keep sensitive identity data out of general application logs.
- Can I test the HyperVerge integration without hitting the live API?
- Because the package is a wrapper around HyperVerge's REST endpoints, the usual Laravel testing approaches apply: override the published config with test values and mock the facade or the underlying HTTP layer in your tests. That keeps your test suite from making real KYC calls and incurring costs. Validate the response shape your code depends on using a fixture or a single sandbox call.
- How do I publish the config file for 3neti/hyperverge?
- Run php artisan vendor:publish and choose the 3neti/hyperverge service provider or its config tag from the prompt. The package's configuration file is then copied into your application's config directory, where you can set credentials and environment values. Commit the config structure but keep real secrets in your .env file.
- Is 3neti/hyperverge suitable for production KYC with Aadhaar and PAN data?
- Yes, it is designed for Laravel applications that need identity verification, but production use means treating Aadhaar, PAN, and face data as sensitive personal information. Keep API credentials in environment variables, avoid logging raw identity payloads, and make sure your consent and retention practices meet the regulations that apply to you. Handle HyperVerge errors and timeouts explicitly so failed verifications do not silently pass users through.
- What are the alternatives to 3neti/hyperverge for KYC in Laravel?
- Alternatives include calling HyperVerge's REST API directly with Laravel's HTTP client, using an official HyperVerge SDK where one exists, or choosing another KYC provider with its own Laravel integration. This package mainly saves you boilerplate around config, credentials, and consistent responses. If you only need one endpoint, a small custom wrapper may be simpler.