-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatible with Omnipay 3? #5
Comments
Sorry I meant compatible with "omnipay/common": "~3". |
I haven't done any work with OmniPay since they launched v3 in May. If you can write a PR that contributes some tests to establish compatibility, I'd be happy to merge it and push out a new release. |
I actually just realized that there's one issue. BluePay's refund functionality is a joke. You don't pass json data or a string to their refund function. You have to pass an array like this [1000045345,43.00]. No indexes or anything. So with Omnipay this results in a server error. The only work around will be to include the margules/bplib package and run the refund through that. Not sure of any other way to fix it. |
I'm working on getting Blue Pay to work with a Laravel app that's using Omnipay. Your package looks like it's perfect, but the application is using Omnipay 3 according to the composer file. Is your package not compatible with this? If it is, can you adjust your composer.json to reflect it?
Thanks!
The text was updated successfully, but these errors were encountered: