- How do I install 3neti/emi-netbank in a Laravel application?
- Install it with Composer by running composer require 3neti/emi-netbank. Laravel's package auto-discovery registers the bundled service provider, so you normally do not need to add anything to config/app.php manually. After installation, publish the package configuration file and add your EMI Netbank credentials.
- Which Laravel and PHP versions does 3neti/emi-netbank support?
- The package is built as a conventional Laravel package with a service provider and publishable config, so it follows standard framework conventions. The exact Laravel and PHP constraints live in the package's composer.json, so check that before installing. If you are on an older Laravel release, confirm compatibility first, since explicit version support is not stated in the available metadata.
- How do I configure EMI Netbank credentials in Laravel?
- Publish the configuration file with php artisan vendor:publish and set your EMI Netbank credentials there. Back those values with environment variables so secrets never sit in version control and each environment can use its own account. Because credentials and endpoints are configurable, staging and production can be kept fully separate.
- How do I initiate a payment with the EMI Netbank package?
- Resolve the package's payment class or facade in your controller and pass the required payment details, such as amount, order reference, and return or callback URLs. The package builds the request against the configured EMI Netbank endpoint and returns the bank's response for you to act on. Check the package source and README for the exact method signatures, since they are specific to this integration.
- How do I handle EMI Netbank callback responses in Laravel?
- Define a route in your application that EMI Netbank can call after the payment attempt, and pass the incoming request data into the package's response handling. The package parses the bank response so you can update your order status and show the customer a result page. Always verify the reported status server-side before marking an order as paid.
- Can I use different EMI Netbank endpoints for sandbox and production?
- Yes, endpoints are configurable alongside credentials, so you can point the package at test or production EMI Netbank URLs per environment. The usual setup is to drive these values from environment variables so staging and production never share endpoints or credentials. That also makes it easy to switch to a sandbox account for end-to-end checks.
- Is 3neti/emi-netbank safe to use in production?
- The package is a thin wrapper around the bank's API, so production safety depends largely on how you handle verification, logging, and failure cases in your own code. Keep credentials in environment variables, verify callback payloads before trusting them, and log request and response data for reconciliation. Since the available repository metadata is limited, review the source and pin a version you have tested.
- How do I test EMI Netbank payments without calling the real bank API?
- Because the package talks to a remote endpoint, the practical approach is to fake or mock the payment class in your feature tests so no real HTTP request is made. Then simulate callback payloads against your own route to confirm order status logic and error handling. For genuine end-to-end checks, use EMI Netbank's sandbox environment with test credentials.
- Can I map EMI Netbank payment statuses to my own order states?
- Callback and response handling is part of the package's scope, so you can translate the bank's status values into your application's order states. Store the raw response for auditing and treat anything other than a confirmed success as unpaid until you verify it. Consult the package source for the exact status fields and values returned by EMI Netbank.
- What are the alternatives to 3neti/emi-netbank?
- Alternatives include calling the EMI Netbank API directly, using another Laravel payment wrapper, or adopting a broader multi-gateway package. This package's strength is a small, focused wrapper with a Laravel service provider and publishable configuration, which keeps the integration lightweight. If you need several payment providers behind one interface, a larger abstraction layer may suit you better.