In a GET request, the response will contain an entity corresponding to the requested resource. The actual response will depend on the request method used. Standard response for successful HTTP requests. The following status codes are defined in the QuickPay API: HTTP Status
QUICKPAY LIMIT CODE
If indeed something went wrong in processing of the request, the status code will also tell something about the type of error. This code is used to identify wether the request went well or if an error occurred. The HTTP response status line contains a status code. The QuickPay API recognizes five HTTP request methods: MethodĪuthorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ= Request methods defines the action we wish to perform on a resource. See the complete list over resources in the sidebar to the left. The request URI identifies the resource we want to handle. It is possible to create a seperate and restricted user account for API usage - in fact, we do not only encourage you to do so… your new merchant account automatically comes with a restricted user “Payment Window”. With this user you can create multiple merchant accounts or be connected to existing merchant accounts.Īuthentication is done by using HTTP Basic Auth, leave Username emty like this ’:apikey’ and you will need valid credentials from your account at QuickPay. To interact with our API you will need to create a user. This example demostrates the versions and their lifecycle:Īny and all communication is encrypted using a TLS. In addition a be beta/preview version might also be available.
![quickpay limit quickpay limit](http://travelwithgrant.boardingarea.com/wp-content/uploads/2017/07/Zelle-Payment-from-US-Bank-to-Chase-10.png)
![quickpay limit quickpay limit](https://www.uponarriving.com/wp-content/uploads/2018/12/Chase-QuickPay-Mobile-473x410.png)
There is however a limit in terms of backward compability and at any time only the two newest versions will be available.
![quickpay limit quickpay limit](http://travelwithgrant.boardingarea.com/wp-content/uploads/2017/07/Zelle-Payment-from-US-Bank-to-Chase-7.png)
QUICKPAY LIMIT HOW TO
How to specify the desired version in the HTTP request is explained in detail later on. To foresee and avoid potential compatibility issues, the API handles this by having multiple versions available at the same time. Over time new features will come along and others will be removed. The QuickPay API is purposely the service upon which everything else in QuickPay is built ( we eat our own dog food). The QuickPay API is based on the principles of Representational State Transfer (REST) allowing clients to create, view, modify and delete resources using standard HTTP request methods.