-
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
feat(#1): adds reference for createPayment #2
base: master
Are you sure you want to change the base?
Conversation
…nd introduces apiKey instead of access token
@@ -128,41 +227,40 @@ private function constructHeaders() | |||
{ | |||
return [ | |||
'Content-Type: application/json', | |||
'Authorization: '.$this->access_token, | |||
'Authorization: ' . (!is_null($this->apiKey) ? $this->apiKey : $this->accessToken) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mixing apiKey and accessToken doesn't make it easier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The thing that I deprecated the accessToken but to be backwards compatible this mix is temporarily needed until a new major version is released and the accessToken is removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi guys,
We will be bringing back Payconiq payments in the future to our platform and will check the updates you did on this. Let me get back to you asap!
This adds the reference parameter when creating a payment (#1). I also took the liberty to fix the naming of transaction_id to payment_id to make it consistent with the actual Payconiq API and did some refactoring as well to make the code more consistent overall.