Open documentation ↗Overview
This document describes the Qualpay Payment Gateway API.
Qualpay Payment Gateway API is a shopping API from qualpay.com. Requests are authenticated with HTTP Basic auth. It is served over HTTPS. Its OpenAPI description documents 14 endpoints.
At a glance
- Authentication
- HTTP Basic
- HTTPS
- Yes
- CORS
- Unknown
- Category
- Shopping
- Base URL
https://api-test.qualpay.com/pg- Version
- 1.7.0
- Endpoints
- 14
- OpenAPI
- Specification ↗
- Spec updated
- 2021-08-23
Make a first request
Replace the placeholders; the documentation says exactly where credentials go.
curl -X POST "https://api-test.qualpay.com/pg/ardef" \
-H "Accept: application/json" \
-H "Authorization: Basic BASE64_USER_PASSWORD"const response = await fetch("https://api-test.qualpay.com/pg/ardef", {
method: "POST",
headers: {
"Accept": "application/json",
"Authorization": "Basic BASE64_USER_PASSWORD",
},
});
const data = await response.json();
console.log(data);import requests
response = requests.request(
"POST",
"https://api-test.qualpay.com/pg/ardef",
headers={
"Accept": "application/json",
"Authorization": "Basic BASE64_USER_PASSWORD",
},
timeout=30,
)
print(response.json())Endpoints
| Method | Path | What it does |
|---|---|---|
| POST | /ardef | Get Card type Information for Visa, Mastercard, and Discover |
| POST | /auth | Authorize Transaction |
| POST | /batchClose | Close Batch |
| POST | /capture/{pgIdOrig} | Capture an Authorized Transaction |
| POST | /credit | Issue Credit to Cardholder |
| POST | /emailReceipt/{pgId} | Send Transaction Receipt Email |
| POST | /expireToken | Expire Token |
| POST | /force | Force Transaction Approval |
| POST | /recharge/{pgIdOrig} | Recharge Previously Settled Transaction |
| POST | /refund/{pgIdOrig} | Refund Previously Captured Transaction |
| POST | /sale | Sale (Auth + Capture) |
| POST | /tokenize | Tokenize Card |
| POST | /verify | Verify Card |
| POST | /void/{pgIdOrig} | Void a Previously Authorized Transaction |
Questions
Does the Qualpay Payment Gateway API API need an API key?
Yes. The Qualpay Payment Gateway API API uses HTTP Basic authentication; the documentation explains how to get credentials.
Does the Qualpay Payment Gateway API API support HTTPS?
Yes, the Qualpay Payment Gateway API API is served over HTTPS.
How many endpoints does the Qualpay Payment Gateway API API have?
Its OpenAPI description lists 14 endpoints in version 1.7.0. All of them are shown on this page.
What are alternatives to the Qualpay Payment Gateway API API?
Other Shopping APIs include Etsy, eBay, Flipkart Marketplace, Inventory Management, Intel Product Catalogue Service.
Similar shopping APIs
Compare alternatives →Etsy
ShoppingManage shop and interact with listings
eBay
ShoppingSell and Buy on eBay
Flipkart Marketplace
ShoppingProduct listing management, Order Fulfilment in the Flipkart Marketplace
Inventory Management
ShoppingMaintaining up-to-date inventory for your items on Walmart.com ensures a great experience for your customers and greater sales opportunities for you.
Intel Product Catalogue Service
ShoppingThis is the documentation for PIM Micro services. In order to use this tool you need to have Basic Auth credentials and a client id. If you dont have one, please make sure to request one by sending an email to the PIM MS team: [[email protected]](mailto:[email protected]?subject=PIMServices)
Item API
ShoppingPlease make sure you use the correct version of the APIs for your use case. To find out the appropriate version, go to the API Docs drop down on the menu.
Listed from APIs.guru (CC0).