Qualpay

Qualpay Payment Gateway API

This document describes the Qualpay Payment Gateway API.

E-commerce#openapi#ecommerce

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

This document describes the Qualpay Payment Gateway API.

Endpoints 14

payment-gateway

  • POSTGet Card type Information for Visa, Mastercard, and Discover/ardefGets Card type information for Visa, Mastercard, and Discover. Useful if you prohibit or allow certain activity based on card type. For example, you may not…
  • POSTAuthorize Transaction/authAuthorizes a credit card for capture at a later time. An authorized transaction will continue to be open until it expires or a capture message is received.…
  • POSTClose Batch/batchCloseCloses a batch. Use this request when the timing of the batch close needs to be controlled rather than relying on the once-daily automatic batch close which…
  • POSTCapture an Authorized Transaction/capture/:pgIdOrigCaptures an authorized transaction for any amount up to the amount originally authorized. An authorized transaction can only be captured once.
  • POSTIssue Credit to Cardholder/creditIssues an unlinked credit. Credit requests require that the cardholder data is provided in the request. Credits are only available during the first 30 days of…
  • POSTSend Transaction Receipt Email/emailReceipt/:pgIdSends the transaction receipt to multiple email addresses. Receipts can be sent only for successful transactions.
  • POSTExpire Token/expireTokenOnce expired, the token (card_id) is no longer valid for use in future transactions.
  • POSTForce Transaction Approval/forceForces an approval, used when an online authorization request received a 'declined' reason code and you have received an authorization from a voice or…
  • POSTRecharge Previously Settled Transaction/recharge/:pgIdOrigCreates a new sale transaction using the cardholder data from a previous successful transaction.
  • POSTRefund Previously Captured Transaction/refund/:pgIdOrigReturns money to the cardholder from a previously captured transaction. Multiple refunds are allowed per captured transaction, provided that the sum of all…
  • POSTSale (Auth + Capture)/saleRequests authorization, and, if approved, will immediately capture the transaction to be included in the next batch close. This transaction type is used in…
  • POSTTokenize Card/tokenizeOnce stored, a unique card_id is returned for use in future transactions. Optionally, tokenization can be requested in an authorization, verify, force,…
  • POSTVerify Card/verifyA verify request will return success if the cardholder information was verified by the issuer. If AVS or CVV data is included in the message, then the AVS or…
  • POSTVoid a Previously Authorized Transaction/void/:pgIdOrigAuthorizations can be voided at any time until Qualpay automatically voids them at 28 days. Captured transactions can be voided until the batch is closed. If…

API details

Base URL
https://api-test.qualpay.com/pg
Authentication
HTTP Basic authentication (username and password)
Operations
14 operations on 14 pathsPOST 14
Main resources
payment-gateway 14
Description format
Swagger 2.0, API version 1.7.0
Listed from
APIs.guru OpenAPI Directory (CC0-1.0)
Source updated

How to test the Qualpay Payment Gateway API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Qualpay Payment Gateway API collection, without the publisher's secrets.
  3. Add your credentialsThis API uses HTTP Basic authentication (username and password). Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Get Card type Information for Visa, Mastercard, and Discover” (POST /ardef), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Qualpay Payment Gateway API?

This document describes the Qualpay Payment Gateway API. It is listed under E-commerce and has 14 endpoints.

Who publishes the Qualpay Payment Gateway API?

It is listed from Qualpay's public API description (an OpenAPI document), not published by Qualpay on Swastik Codes. Anyone who controls qualpay.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Qualpay Payment Gateway API?

Requests go to https://api-test.qualpay.com/pg. Endpoint paths are added to this base URL.

How do I authenticate with the Qualpay Payment Gateway API?

With HTTP Basic authentication (username and password).

How many endpoints does the Qualpay Payment Gateway API have?

14 operations on 14 paths (14 POST). The largest groups are payment-gateway.

Is forking the Qualpay Payment Gateway API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.