- What is digitickets/omnipay-barclays-epdq?
- It is a Composer package that adds Barclays ePDQ Essential as an Omnipay payment gateway driver. It lets Laravel or any PHP application use Omnipay's common API for ePDQ payment requests and responses. It does not replace Omnipay/common, so both are typically installed.
- How do I install digitickets/omnipay-barclays-epdq in Laravel?
- Install it with Composer using composer require digitickets/omnipay-barclays-epdq. Make sure omnipay/common is available if your application does not already include it. Then create the gateway through Omnipay or your preferred Laravel Omnipay bridge and pass your Barclays ePDQ credentials.
- Which Laravel versions does this Barclays ePDQ Omnipay package support?
- The driver is framework-agnostic, so Laravel compatibility depends mainly on omnipay/common and your Laravel version's PHP and Composer constraints. Check the package composer.json on Packagist and test it in your application before relying on it in production. It is not Laravel-specific, so there is usually no service provider to register.
- How do I configure the Barclays ePDQ Essential gateway in Omnipay?
- Pass the gateway parameters required by ePDQ Essential, such as your PSPID or client identifier, user, password, and signature or passphrase settings. Store these values in environment variables or Laravel config rather than committing them to source control. Confirm the exact parameter names against the package README and your Barclays ePDQ account documentation.
- How do I create a purchase request with this package?
- Use the Omnipay gateway object's purchase method with fields such as amount, currency, transactionId, returnUrl, and any customer or card fields required by ePDQ Essential. Send the request and handle either the redirect or the response according to the integration flow. Field names and required values depend on the ePDQ Essential request type, so check the README for examples.
- How do I handle the ePDQ return URL or callback in Laravel?
- Set the returnUrl to a Laravel route that receives the customer after ePDQ processing. In that route, call Omnipay's completePurchase with the incoming request data and inspect the response using methods such as isSuccessful. Persist the order state before redirecting and make the callback idempotent so repeated requests do not duplicate payments.
- Does this driver support refunds, captures, and voids?
- The driver exposes the Omnipay operations that Barclays ePDQ Essential supports, which commonly include purchase, authorize, capture, refund, and void. Not every operation is guaranteed for every merchant account or ePDQ setup, so verify the gateway class and README. Use the standard Omnipay request and response objects for each operation.
- Can I test Barclays ePDQ payments without a live account?
- Barclays ePDQ provides test credentials and a test PSPID environment for integration testing. Configure the driver for the test environment if it supports a test mode flag, and use the test cards or procedures supplied by Barclays. Switch to live credentials only after confirming the full redirect, callback, and failure flows.
- Does this package support 3D Secure and is it PCI compliant?
- ePDQ Essential typically uses a hosted or redirect payment flow, so card details are entered on Barclays pages and your PCI scope is reduced. 3D Secure and SCA handling are part of the ePDQ flow where enabled on your merchant account. The package itself does not store card numbers, but you should confirm the exact behavior in the README and Barclays documentation.
- Is digitickets/omnipay-barclays-epdq maintained, and what are the alternatives?
- Check the digitickets repository and Packagist release history for recent commits, issues, and compatible Omnipay versions. Alternatives include other Omnipay ePDQ drivers or a direct integration with the Barclays ePDQ API. For new projects, compare maintenance status, supported operations, and Laravel compatibility before choosing.