Skip to content
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

Default params aren't the same as on the Worldpay merchant area. #3

Open
NoelDavies opened this issue May 19, 2015 · 17 comments
Open

Comments

@NoelDavies
Copy link

When I log into the merchant gateway I'm provided with a service key and a client key, but in this repo, the default params are installationId, accountId, secretWord and callbackPassword.. None of which I have..

@NoelDavies
Copy link
Author

I soon realised this package uses the old Worldpay API. I'm writing up a new version for the new API and I'll submit it as a pull request soon.

@maclof
Copy link

maclof commented Jun 8, 2015

I think this will be dependant on the age of the WorldPay account as I have access to 3 WorldPay accounts, none of which have a "service key" or "client key".

@NoelDavies
Copy link
Author

@maclof I'm using the new API they have, I've written gateway for it, but due to the multiple gateways they have going, not sure how I should proceed with it contributing it back to Omnipay?

@maclof
Copy link

maclof commented Jun 8, 2015

@NoelDavies Maybe this package should expose multiple gateways, one of them being the current one and the other being the new API? Similarly to how the PayPal package exposes 3 gateways, PayPal_Express, PayPal_Pro & PayPal_Rest - https://github.com/thephpleague/omnipay-paypal

@NoelDavies
Copy link
Author

Yeah I've seen, but they haven't got different names for them... We could just name it Worldpay_Rest similarly to the paypal one?

@harrywebdev
Copy link

@NoelDavies have you got round to writing the new gateway?

@NoelDavies
Copy link
Author

I have! But it's not fully tested! I'll update it on git later today and then post a link to it. I wrote it for an old client and they wouldn't let me write tests.. Yes.. one of those companies..

@andy1547
Copy link

@noeldavis Any updates on this?

@JasonMortonNZ
Copy link

@NoelDavies - any progress on writing up the new gateway?

@bweston92
Copy link
Contributor

Updates?

@JoSquiders
Copy link

I'd be interested in an update on this too please.

@lukeholder
Copy link
Contributor

@NoelDavies please commit your work to github so we can contribute, otherwise I am starting on the new API gateway from scratch this week.

@dpfaffenbauer
Copy link
Contributor

Updates?

@lukeholder
Copy link
Contributor

@dpfaffenbauer I have made a pull request for the new api.

@lukeholder
Copy link
Contributor

@JoSquiders @bweston92 @JasonMortonNZ @andy1547 @NoelDavies

Please test my pull request and leave a comment on it if it's working for you.

Thanks.

@lukeholder
Copy link
Contributor

This can also be closed @delatbabel

@jasegw
Copy link

jasegw commented Oct 7, 2020

Hi All. This been fixed ?
If so, how do I fix please ?

My WorldPay details are...
Service key
Client key
WebHooks

OmniPay wants...
Installation Id
Account Id
Secret Word
Callback Password

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants