Integration

Qualpay integration

Qualpay is a US payment processor. Charge, authorize, capture, void, refund and verify card payments through the Payment Gateway and tokenize cards; keep customers, saved cards and shipping addresses in the Customer Vault; run recurring billing plans and subscriptions; create, send and track invoices and hosted checkout links; read settled transactions, batches, deposits and statements; manage disputes, Account Updater requests, payees and webhooks. Partner onboarding, integrator key management, browser-side embedded field keys, sandbox-only helpers and routes carrying full card numbers are left out. Authentication is HTTP Basic: your merchant ID as the username and an API security key (from Qualpay Manager) as the password.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Qualpay.Built from the 115 Qualpay tools below, on the connection you add once.

What you can do with Qualpay

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Payment, 6 operations

  • add_invoice_paymentAdd invoice paymentPOSTAdds a payment to a `SAVED` or `OUTSTANDING` invoice. Note: This operation requires special permissions for vendor account use. Contact Qualpay Support to enable it.
  • list_invoice_paymentsList invoice paymentsGETGets and filters all invoice payments for one merchant account. Optional query parameters determine the size and sort order of the returned array.
  • list_payments_of_invoiceList payments of invoiceGETGets and filters all payments made on an invoice. Optional query parameters determine the size and sort order of the returned array.
  • pay_payeePay payeePOSTInitiates a payment to the specified payee saved in Payee Vault. Payee relationship will be validated.
  • remove_invoice_paymentRemove invoice paymentDELETERemoves a payment from a `SAVED` or `OUTSTANDING` invoice. Payments made by credit card cannot be removed.
  • update_invoice_paymentUpdate invoice paymentPUTUpdates a payment on a `SAVED` or `OUTSTANDING` invoice. You cannot update credit card payments made through the invoice’s 'Pay Now' button.

Customer, 5 operations

  • create_customerCreate customerPOSTAdds a customer to the Customer Vault and generates or saves a `customer_id`, which is required to create invoice and subscription payments.
  • delete_customerDelete customerDELETEDeletes a customer profile from Customer Vault. Deleting a customer profile will delete all the subscriptions associated with the profile. This operation cannot be reversed.
  • get_customerGet customerGETGets a specified profile in Customer Vault.
  • list_customersList customersGETGets and filters all customer profiles saved in one merchant account’s Customer Vault. Optional query parameters determine the size and sort order of the returned array.
  • update_customerUpdate customerPUTUpdates a Customer Vault profile. You can send the entire resource or just the fields that need updating.

Payee, 5 operations

  • create_payeeCreate payeePOSTCreates a payee profile in the Payee Vault. Returns a `payee_id`, which you can use to manage the profile.
  • delete_payeeDelete payeeDELETEDeletes a payee profile from Payee Vault. This operation cannot be reversed.
  • get_payeeGet payeeGETGets a specified profile in Payee Vault. Note: The Payee Vault API resource is intended for a very specific use case and requires special permissions.
  • list_payeesList payeesGETGets and filters all profiles in the Payee Vault of one merchant account. Optional query parameters determine the size and sort order of the returned array.
  • update_payeeUpdate payeePUTUpdates a specified profile in Payee Vault. You can send all fields or just the fields that need updating.

Cancel, 4 operations

  • cancel_account_updater_requestCancel account updater requestPOSTCancels a submitted Account Updater request whose status is `INPROGRESS`. Note: This operation is intended for merchant account use, and it requires special permissions.
  • cancel_checkout_linkCancel checkout linkDELETEExpires the checkout link of a dynamic checkout. Expired checkout links are no longer accessible to customers to make payments.
  • cancel_invoiceCancel invoiceDELETECancels an invoice. A canceled invoice cannot be edited. If an invoice has been canceled and your customer selects 'Pay Now' in the sent invoice, an error message will appear.
  • cancel_subscriptionCancel subscriptionPOSTCancels an active, suspended, or paused subscription. A canceled subscription cannot be resumed.

Delete, 4 operations

  • delete_dispute_fileDelete dispute filePOSTRemoves one of the files previously uploaded as supporting documentation for a dispute.
  • delete_payment_methodDelete payment methodPUTDeletes a specified payment method from a profile in Customer Vault. A payment method with active subscriptions cannot be deleted.
  • delete_planDelete planDELETEDeletes a plan. You can delete any plan, whether it is active or not. All subscriptions related to the plan are canceled.
  • delete_subscription_custom_fieldDelete subscription custom fieldPOSTRemoves a custom field assigned to a subscription.

Plan, 4 operations

  • create_planCreate planPOSTCreates a new recurring plan. Generates a unique `plan_id`, which you can use to interact with or delete the plan.
  • get_planGet planGETReturns a list of recurring plans for a specified `plan_code`. The search results include active, archived, and deleted plans.
  • list_plansList plansGETGets a paginated list of all recurring plans. Optional query parameters determine the size and sort order of the returned array.
  • update_planUpdate planPUTUpdates an active recurring plan. Only the fields sent in the request body are updated.

Shipping, 4 operations

  • add_shipping_addressAdd shipping addressPOSTAdds a shipping address to a profile in Customer Vault. The response includes a unique `shipping_id`, which can be used to manage the `shipping_address`.
  • delete_shipping_addressDelete shipping addressDELETEDeletes a specified shipping address from a profile in Customer Vault.
  • list_shipping_addressesList shipping addressesGETGets all shipping addresses for a specified profile in Customer Vault. The response includes an array of shipping addresses.
  • update_shipping_addressUpdate shipping addressPUTUpdates a specified shipping address for a profile in Customer Vault.

Subscription, 4 operations

  • create_subscriptionCreate subscriptionPOSTCreates a new subscription with a specific start date, subscribing a customer to a recurring plan or a one-off off-plan.
  • get_subscriptionGet subscriptionGETGets the details of the specified subscription.
  • list_subscriptionsList subscriptionsGETGets an array of subscription objects. Optional query parameters determine the size and sort order of the returned array.
  • update_subscriptionUpdate subscriptionPUTUpdates an existing subscription. The start date can only be updated for subscriptions that have not yet started.

Webhook, 4 operations

  • create_webhookCreate webhookPOSTCreate a webhook that posts the chosen events to your URL. Returns the webhook_id; the secret that signs the posts is not passed back here.
  • get_webhookGet webhookGETGets data on a specified webhook.
  • list_webhooksList webhooksGETGets and filters an array of all webhooks associated with your account. Optional query parameters determine the size and sort order of the returned array.
  • update_webhookUpdate webhookPUTUpdates a webhook’s configurations. You can send just the fields that need updating.

Billing, 3 operations

  • add_payment_methodAdd payment methodPOSTTokenizes and adds a payment method to a customer profile in Customer Vault. This returns the tokenized card number (or card ID) in the `card_id` field.
  • list_payment_methodsList payment methodsGETGets a list of all payment methods associated with a `customer_id`. The response contains an array of billing cards.
  • update_payment_methodUpdate payment methodPUTUpdates a specified payment method for a profile in Customer Vault. Include the complete billing record in the request.

Detail, 3 operations

  • get_account_updater_request_resultsGet account updater request resultsGETRetrieves and filters information on all cards sent in one specified Account Updater request, including responses for each.
  • get_invoiceGet invoiceGETGets information on a specified invoice. Note: This operation requires special permissions for vendor account use. Contact Qualpay Support to enable it.
  • list_account_updater_resultsList account updater resultsGETGets and filters data on all payment cards that were sent to the Account Updater engine and the responses received.

Event, 3 operations

  • add_webhook_eventAdd webhook eventPOSTSubscribe a webhook to one more event.
  • list_webhook_eventsList webhook eventsGETList the events a webhook is subscribed to.
  • remove_webhook_eventRemove webhook eventDELETEUnsubscribe a webhook from one event.

Summary, 3 operations

  • get_account_updater_request_summaryGet account updater request summaryGETGets summary information on one specified Account Updater request. Note: This operation is intended for merchant account use, and it requires special permissions.
  • list_account_updater_summariesList account updater summariesGETGets and filters the summarized result information for all Account Updater requests. Optional query parameters determine the size and sort order of the returned array.
  • list_statement_summariesList statement summariesGETList statement summary data for the merchant, one record per statement, with paging, sorting and filters.

Transaction, 3 operations

  • list_settled_transactionsList settled transactionsGETGets and filters a paginated list of settled transactions. Optional query parameters determine the size and sort order of the returned array.
  • list_subscription_transactionsList subscription transactionsGETGets all subscription transactions. Optional query parameters determine the size and sort order of the returned array.
  • list_transactions_of_subscriptionList transactions of subscriptionGETGets all transactions for a specified subscription. Optional query parameters help filter and restrict the result.

Browse, 2 operations

  • list_disputesList disputesGETGets dispute details associated with one vendor or node. By default, this returns anything with a status change date of the previous day or same day as the request.
  • list_subscription_custom_fieldsList subscription custom fieldsGETGets all of the custom fields assigned to a subscription. Optional parameters will help filter and restrict the result.

Checkout, 2 operations

  • create_checkout_linkCreate checkout linkPOSTGenerates a link to a hosted page that either allows the user to make payments or add and edit payment methods saved in Customer Vault.
  • get_checkout_paymentGet checkout paymentGETGets information about a transaction that used a specified Checkout link.

Invoice, 2 operations

  • create_invoiceCreate invoicePOSTCreate a draft invoice for a customer, to send later with send_invoice. Returns the invoice_id.
  • list_invoicesList invoicesGETGets and filters all invoices associated with your account. Optional query parameters determine the size and sort order of the returned array.

Primary, 2 operations

  • set_primary_payment_methodSet primary payment methodPUTSets a specified payment method as the primary payment method for a profile in Customer Vault. The system uses the primary payment method for subscription payments.
  • set_primary_shipping_addressSet primary shipping addressPUTSets a specified shipping address as the primary shipping address for a profile in Customer Vault.

Accept, 1 operation

  • accept_disputeAccept disputeGETAccept a first-time chargeback, or withdraw from arbitration at the pre-arbitration stage. The Dispute Management API must be enabled for the account by Qualpay Support.

Account, 1 operation

  • update_payee_accountUpdate payee accountPOSTUpdates the payment account details of a profile in Payee Vault. Note: The Payee Vault API resource is intended for a very specific use case and requires special permissions.

Action, 1 operation

  • submit_dispute_actionSubmit dispute actionPOSTSubmit dispute responses with supporting documentation.

Add, 1 operation

  • add_subscription_custom_fieldAdd subscription custom fieldPOSTAdds a new custom field to a subscription.

Archive, 1 operation

  • archive_planArchive planPOSTArchives an active plan. All subscriptions to the plan remain active. You cannot update an archived plan or add new subscribers to it.

Ardef, 1 operation

  • get_card_type_infoGet card type infoPOSTGets Card type information for Visa, Mastercard, or Discover cards. This is useful if you prohibit or allow certain activity based on card type.

Auth, 1 operation

  • authorize_transactionAuthorize transactionPOSTAuthorize a card payment to capture later with capture_transaction. The authorization stays open until it is captured or expires. Pay with card_number and exp_date, a saved card_id, or a customer_id.

Balance, 1 operation

  • request_fbo_balanceRequest fbo balancePOSTRequests a balance for the specified 'For Benefit Of' merchant account. FBO relationship will be validated.

Batch close, 1 operation

  • close_batchClose batchPOSTImmediately closes the open batch of transactions. Use this request to control the timing of the batch close. By default, the once-daily automatic batch close is at 9 p.m.

Batche, 1 operation

  • list_batchesList batchesGETList the merchant's settled batches (whole batches settled from a point-of-sale device, software or the gateway), with paging, sorting and filters.

Bounced, 1 operation

  • list_undelivered_invoicesList undelivered invoicesGETGets and filters all undelivered invoices for one merchant account. Optional query parameters determine the size and sort order of the returned array.

Bypgid, 1 operation

  • get_transaction_by_pg_idGet transaction by pg idGETGets information on a Payment Gateway transaction specified by its Payment Gateway ID.

Capture, 1 operation

  • capture_transactionCapture transactionPOSTCaptures an authorized transaction for any amount up to the amount originally authorized. An authorized transaction can only be captured once.

Copy, 1 operation

  • copy_invoiceCopy invoicePOSTMakes a copy of an invoice. The invoice date will be set to today's date, and the due date will be adjusted based on the invoice date and the payment terms.

Create, 1 operation

  • create_account_updater_requestCreate account updater requestPOSTUses the IDs of saved payment cards to create and submit an Account Updater request. Returns a unique `request_id` that you can use to check the status of the request.

Credit, 1 operation

  • issue_creditIssue creditPOSTIssue an unlinked credit to a cardholder: money is returned to a card without reference to an earlier transaction, so the card data must be in the request. Prefer refund_transaction to return money for an earlier sale.

Creditedtran, 1 operation

  • list_dispute_credited_transactionsList dispute credited transactionsGETReturns credited transactions from the last 90 days that are related to a dispute case.

Deposit, 1 operation

  • list_depositsList depositsGETGets and filters a paginated list of bank deposits and withdrawals. Optional query parameters determine the size and sort order of the returned array.

Disable, 1 operation

  • disable_webhookDisable webhookPUTDisables a webhook, holding all existing requests from triggering until the webhook is enabled again.

Dispute, 1 operation

  • get_disputeGet disputeGETGet one dispute (chargeback) case by its control number, with its status, reason, amounts and deadlines.

Dispute adjustment, 1 operation

  • list_statement_dispute_adjustmentsList statement dispute adjustmentsGETGets and filters a paginated list of dispute adjustments that appear in statements sent to the merchant.

Draft, 1 operation

  • update_draft_invoiceUpdate draft invoicePUTUpdates a draft invoice. Only the fields sent in the request body are updated. If updating JSON object fields, you should send the complete JSON in the request body.

Edit, 1 operation

  • update_subscription_custom_fieldUpdate subscription custom fieldPOSTEdits a custom field assigned to a subscription.

Email receipt, 1 operation

  • email_transaction_receiptEmail transaction receiptPOSTSends a transaction receipt to multiple email addresses. Receipts can be sent only for successful transactions.

Enable, 1 operation

  • enable_webhookEnable webhookPUTEnables a webhook, making it active. Events are triggered and requests are posted only for active webhooks.

Expire token, 1 operation

  • expire_card_tokenExpire card tokenPOSTExpires the token (`card_id`), rendering it no longer valid for use in future transactions. The token is not deleted until 30 days after expiration.

Fee, 1 operation

  • list_statement_feesList statement feesGETGets and filters a paginated list of fees deducted in each statement sent to the merchant. Optional query parameters determine the size and sort order of the returned array.

Force, 1 operation

  • force_transactionForce transactionPOSTForce a transaction that was declined, typically with an approval code obtained from the issuer by phone, into the system.

Hold, 1 operation

  • hold_from_account_updaterHold from account updaterPOSTPuts one card ID or all payment cards belonging to a customer ID on an Account Updater harvest hold. Held cards are not included in your Account Updater harvest.

List, 1 operation

  • list_dispute_filesList dispute filesGETLists all the existing files uploaded as supporting documentation for a dispute.

Nondisputedtran, 1 operation

  • list_dispute_non_disputed_transactionsList dispute non disputed transactionsGETReturns debits that occurred in the last 90 days and are related to a dispute case.

Outstanding, 1 operation

  • update_outstanding_invoiceUpdate outstanding invoicePUTUpdates an outstanding invoice. Only the fields sent in the request body are updated. If updating JSON object fields, send the complete JSON in the request body.

Pause, 1 operation

  • pause_subscriptionPause subscriptionPOSTPauses an active subscription. Recurring payments are skipped when a subscription is paused.

Plan type, 1 operation

  • list_statement_plan_typesList statement plan typesGETGets and filters a paginated list of data on each payment instrument type that appears in statements sent to the merchant.

Recharge, 1 operation

  • recharge_transactionRecharge transactionPOSTCreates a new sale transaction using cardholder data from a previous successful transaction. Note: This operation is only available to merchant accounts.

Refund, 1 operation

  • refund_transactionRefund transactionPOSTReturns money to the cardholder from a previously captured payment card transaction.

Refund non pg, 1 operation

  • refund_third_party_transactionRefund third party transactionPOSTRefund a purchase that was processed by a third-party gateway rather than the Qualpay Payment Gateway, using the transaction's rec_id from list_settled_transactions.

Release, 1 operation

  • release_from_account_updaterRelease from account updaterPOSTReleases one card ID or all payment methods belonging to a customer ID from an Account Updater harvest hold.

Remedyundisputedtran, 1 operation

  • list_dispute_remedy_transactionsList dispute remedy transactionsGETRequests the undisputed transactions associated with a Visa dispute that qualify for use in a Remedy response. Note: The Dispute Management API resource is not enabled by default.

Resend, 1 operation

  • resend_invoiceResend invoicePOSTResends an outstanding or paid invoice to a customer. Note: This operation requires special permissions for vendor account use. Contact Qualpay Support to enable it.

Reserve, 1 operation

  • list_statement_reservesList statement reservesGETGets and filters a paginated list of data on the merchant account reserves that appear in statements sent to the merchant.

Respond, 1 operation

  • submit_dispute_responseSubmit dispute responsePOSTSubmits a dispute response with supporting documentation. Response options are dynamic and are based on the response reason code.

Response, 1 operation

  • get_dispute_responseGet dispute responseGETGets a dispute response you previously submitted. Note: The Dispute Management API resource is not enabled by default. Contact Qualpay Support for permissions.

Resume, 1 operation

  • resume_subscriptionResume subscriptionPOSTResumes a subscription that you have paused or that the system has suspended.

Sale, 1 operation

  • create_saleCreate salePOSTCharge a card: requests authorization and, if approved, captures the transaction for the next batch close. Pay with card_number and exp_date, a saved card_id, or a customer_id from the Customer Vault.

Send, 1 operation

  • send_invoiceSend invoicePOSTSends a saved invoice to a customer. This changes the invoice’s status to outstanding. After sending, you can only update the invoice’s `from_contact` and `billing_contact`.

Settlement, 1 operation

  • list_statement_settlementsList statement settlementsGETGets and filters a paginated list of the settlement data for each statement we settled with the merchant.

Tokenize, 1 operation

  • tokenize_cardTokenize cardPOSTSave a card (or bank account) securely and get back a card_id to use instead of the card number in later transactions. A card_id of your choice can be sent to store new data under it.

Transaction request, 1 operation

  • list_transaction_requestsList transaction requestsGETGets and filters a paginated list of all transaction requests. Optional query parameters determine the size and sort order of the returned array.

Upload, 1 operation

  • upload_dispute_fileUpload dispute filePOSTAdds a new dispute file to any existing files as supporting documentation for a dispute.

Verify, 1 operation

  • verify_cardVerify cardPOSTA Verify request returns success if the cardholder information was verified by the issuer.

Void, 1 operation

  • void_transactionVoid transactionPOSTVoid an authorized transaction (until it is automatically voided after 28 days) or a captured one before its batch is closed.

Use Qualpay from Claude Code, Cursor or Codex

Connect Qualpay in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Qualpay operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Qualpay

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Qualpay once

    Add your Qualpay connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Qualpay integration FAQ

What can you do with the Qualpay integration?

LiveContext exposes 115 operations on Qualpay, covering payment, customer, payee and cancel.

Popular integrations

Browse the whole catalog