- How do I install fruitcakestudio/omnipay-sisow?
- Install it with Composer using composer require fruitcakestudio/omnipay-sisow, which pulls in the Omnipay core it depends on. There is no Laravel service provider to register, because it is a framework-agnostic Omnipay driver. You then create the gateway with Omnipay::create('Sisow') or by instantiating the Sisow gateway class directly. Check the README and composer.json for the exact PHP and omnipay/common versions required.
- Does this package work with Laravel, and which Laravel versions are supported?
- Yes. It is a plain Omnipay gateway, so it works inside any Laravel version that runs a PHP version supported by the underlying omnipay/common package. Rather than a Laravel-specific service provider, you usually resolve it through the Omnipay facade or bind it in a service provider or config file. Confirm the required PHP version in the package's composer.json before installing on older Laravel releases.
- Which payment methods does the Sisow Omnipay gateway support?
- Sisow is a Dutch payment provider, so the gateway is typically used for iDEAL, Bancontact, credit card and similar methods offered by your Sisow contract. Which methods are actually available depends on the products enabled on your merchant account. Pass the desired method through the gateway parameters when creating the purchase request, and check the gateway source for the exact accepted values.
- How do I configure my Sisow merchant ID and merchant key?
- Pass your Sisow merchant ID and merchant key as gateway parameters when you initialise the gateway, or set them on the gateway object before building a request. Store them in environment variables or a config file rather than hard-coding them in your checkout code. Never commit live credentials to version control, and use separate credentials for test and production.
- How do I start a payment and redirect the customer to Sisow?
- Build a purchase request through the gateway, supplying the amount, currency, return and cancel URLs, and any method-specific parameters. A successful response is a redirect response, so you send the customer to the returned redirect URL. Sisow then handles the payment page and sends the customer back to your return URL when finished. Always check the response for success before redirecting.
- How do I handle the return callback from Sisow and complete the purchase?
- On your return route, call completePurchase with the transaction reference Sisow sends back, then inspect isSuccessful() and the transaction status before marking an order as paid. Treat the return URL as user input: verify the status with Sisow rather than trusting query parameters alone. Persist the transaction reference and full gateway response so you can reconcile or debug later. Also provide a cancel URL that leaves the order in a pending state.
- Can I test Sisow payments without moving real money?
- Omnipay gateways generally expose a test mode, which on Sisow points the driver at the Sisow test environment instead of the live one. Enable it on the gateway in your local and staging configuration and use the test merchant credentials from your Sisow dashboard. Run through each payment method you plan to offer, including cancelled and failed payments, before switching to live credentials in production.
- How do I display iDEAL bank issuers in my checkout form?
- Many Omnipay gateways, including the Sisow driver, provide a fetchIssuers request that returns Issuer objects with an id and a name. Call it before rendering your checkout so customers can pick their bank, then pass the chosen issuer ID with the purchase request. Cache the issuer list where sensible, since it rarely changes and adds latency to page loads. Check the gateway source to confirm the exact method name and option keys.
- Does this gateway support refunds?
- Refund support depends on both the driver and what Sisow exposes for the payment method used, so check whether the gateway implements refund() and whether it reports support for the request. If it does, build a refund request with the original transaction reference and the amount to return. Log the full response, since partial refunds and provider-side errors are common sources of reconciliation issues.
- Is fruitcakestudio/omnipay-sisow still maintained, and what are the alternatives?
- It is maintained by Fruitcake Studio as a thin driver on top of the Omnipay library, so its release cadence generally follows Omnipay and Sisow API changes. Before adopting it, check the repository's recent commits, open issues and the latest tagged version on Packagist. Alternatives include other Omnipay drivers for Sisow, gateways such as Mollie or MultiSafepay if you want a broader European provider, or integrating the Sisow API directly if you need features the driver does not expose.