quickpay / quickpay-python-client Goto Github PK

Hi guys,

Since quickpay is dropping the TLS 1.0 support, it would be a bright choice to remove it from being the default setting in this code.

https://github.com/QuickPay/quickpay-python-client/blob/master/quickpay_api_client/api.py#L18

Looks like this isn't really available on pip even though the readme file states so.

pip install quickpay-python-client

Collecting quickpay-python-client
  Could not find any downloads that satisfy the requirement quickpay-python-client
  No distributions at all found for quickpay-python-client

Also the readme file says to add "quickpay" to the requirements file, but says that the package name is quickpay-python-client

And neither of them works.

Hi, for start, we use QuickPay for transactions.
Few days ago our client, complaint that he can't make payments.
This is snippet from the error:

Request Method: | POST-- | -- 1.8.3 SSLError
EOF occurred in violation of protocol (_ssl.c:581)
********/local/lib/python2.7/site-packages/requests/adapters.py in send, line 431
/usr/bin/uwsgi-core
Python Versin: 2.7.9

requirements.txt contains:

Django==1.11
requests==2.13.0
git+https://github.com/QuickPay/quickpay-python-client.git

Thanks for any reply.

It seems like mocking https endpoints are not working and tests are failing because of it. Worth to use responses for mocking requests.

With the new status_code added to the ApiError exception. Could somebody update the version and push to PyPi please? I am happy to update the version in a pull request, but it seems a bit unnecessary.

See https://github.com/QuickPay/quickpay-ruby-client/blob/master/.travis.yml.

Also, add build status graphics to README.

So I'm trying to follow one of your examples but it throws the error "404- not found".

I have checked if the login is valid, and it is, so it's not a typo.

Can you maybe spot what's wrong or help me further in any way?
I'm using python 3.10, and this is the code:

secret= f"{USERNAME}:{PASSWORD}"
client = QPClient(secret)
for payment in client.get('/payments'):
    print(payment)

Having upgraded the version of the QuickPay client in a hurry to handle the TLS 1.0 switch off we have noticed an issue with the callback on payments not being called.

In commit 77dc7ba the client has been changed to add the parameter callback_url as a header Quickpay-Callback-Url.

This is not working for us currently. The callback URL is not being called and payments are not registering in our system.

I notice that the header is not capitalised in the same way as in the documentation where the p is upper case:

https://learn.quickpay.net/tech-talk/api/callback/

But when I have changed this to match the documentation the callback is still not called.

Because the parameter callback_url is popped from the kwargs it is not longer passed in the JSON sent in the API call. This is what has caused the callback to stop working for us.

Please can you advise on the best course of action? Should QuickPay-Callback-Url header be working on the V10 API?

It is not possible to change the header QuickPay-Callback-Url using this client.

This would be useful when it is not accepted in the body, e.g.
POST /subscriptions/{id}/recurring