Integrate our products into your software. Let's make payment happen together!
Look at all the possibilitiesThe API uses HTTP as the transport protocol and JSON as the message format.
Non-secure connections are not allowed. Using http://
instead of https://
results in a redirect:
301
text/html
Example of a curl request to the non-secure URL
curl -v http://api.psp.ccv.eu/api/v1/status
* Trying 18.158.216.138:80...
* Connected to api.psp.ccv.eu (18.158.216.138) port 80 (#0)
> GET /api/v1/status HTTP/1.1
> Host: api.psp.ccv.eu
> User-Agent: curl/7.79.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Server: awselb/2.0
< Date: Sun, 19 Dec 2021 10:29:32 GMT
< Content-Type: text/html
< Content-Length: 134
< Connection: keep-alive
< Location: https://api.psp.ccv.eu:443/api/v1/status
<
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
</body>
</html>
* Connection #0 to host api.psp.ccv.eu left intact
You must provide an indication of the request content length.
Use the Content-Length
or Transfer-Encoding
headers to do so.
If you do not, the request will be blocked and result in a non-API HTTP error.
Content-Length
: If you know the length of the request upfront, you can provide this header.
The header is usually present implicitly ( using curl or Postman ).Transfer-Encoding
: If you need to use chunked transfer encoding,
you can provide this header for each chunked request.403
text/html; charset=iso-8859-1