Updated to work with Payfast's latest API #1
Conversation
This was to reflect changes on Payfasts new API
|
Thanks, this worked for me. |
| { | ||
| return $this->getParameter('testMode'); | ||
| } | ||
|
|
There was a problem hiding this comment.
These methods already exist on the AbstractRequest class.
|
I see the advantage of mapping field names exactly to payfast's documentation if you want to write a separate library, but the whole point of Omnipay is that it abstracts the differences between various gateway APIs (so you can use in shopping cart etc where you need a consistent interface). |
|
I understand, also when I was trying to use the omnipay/payfast I had a tough time without some detailed documentation and some working examples. I would say that each extension of omnipay should each have some working examples on the readme. I will look at conforming the changes to omnipay standards, any suggestions on the new fields the payfast api supports. |
|
Sure thing, feel free to add some gateway-specific examples to the readme. I think that would be very useful. |
As per payfast documentation
Some bugs were encountered so I added a direct copy of payfasts php sample code they used to generate the signature.
|
With this branch being stale and the build failing, I'm going to close it for now. Feel free to reopen in the future. |
Added, missing fields, added support for notify_url.