Integration

Shift4 integration

Shift4 (formerly SecurionPay) is a card payment gateway. Create, capture and refund charges, store customers with their cards and payment methods, run plans and subscriptions, issue credits, manage blacklist rules, follow disputes and fraud warnings, upload dispute evidence files, read events and payouts, and create checkout sessions and payment links. Raw card numbers are never sent through these tools: card tokenization and the browser 3D Secure step belong to Shift4's client-side libraries. Authentication is HTTP Basic with your secret key (sk_test_ or sk_live_) as username and an empty password.

Connect Shift4 How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Shift4

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.

Charge, 7 operations

create_chargeCreate chargePOSTMoves real money: charges a card or other payment method (a live key bills the customer). Pass customerId for their default card, card for a token or saved card, or paymentMethod. captured=false only authorizes; see capture_charge.
get_chargeGet chargeGETRetrieves the details of a charge that has previously been created.
list_chargesList chargesGETReturns a list of charges you've previously created. The charges are returned in sorted order, with the most recent charges appearing first.
list_payment_link_chargesList payment link chargesGETLists the charges made through a given payment link. Results are sorted by creation date, with the most recent objects first.
list_subscription_chargesList subscription chargesGETLists the charge attempts made by a subscription, including automatic renewals (rebills) and failed attempts. Results are sorted with the most recent records first.
resolve_charge_statusResolve charge statusPOSTTest helper: sets a pending charge to successful or failed without the real payment flow (Blik, Swish, MB WAY and redirect methods; not cards). Address the charge by its clientObjectId (client_char_...), not its id.
update_chargeUpdate chargePOSTUpdates the specified charge by setting the values of the parameters passed. Any parameters not provided are left unchanged.

Card, 5 operations

create_cardCreate cardPOSTSaves a card to an existing customer from a card token (made by Shift4's client-side libraries) or from a successful charge id. Raw card numbers are not accepted by this tool.
delete_cardDelete cardDELETEDeletes an existing card object. If you delete the card that is the current default card, the most recently added card is used as the new default card.
get_cardGet cardGETRetrieves the details of a card that belongs to a customer.
list_cardsList cardsGETReturns a list of cards belonging to a customer. The cards are returned in sorted order, with the most recently created appearing first.
update_cardUpdate cardPOSTUpdates the specified card. Any parameters not provided are left unchanged.

Customer, 5 operations

create_customerCreate customerPOSTCreates a new customer object. You can attach a card to the customer so it can be reused for recurring charges.
delete_customerDelete customerDELETEDeletes an existing customer object.
get_customerGet customerGETRetrieves the details of an existing customer.
list_customersList customersGETReturns a list of customers. The customers are returned in sorted order, with the most recently created appearing first.
update_customerUpdate customerPOSTUpdates the specified customer by setting the values of the parameters passed. Any parameters not provided are left unchanged.

Plan, 5 operations

create_planCreate planPOSTCreates a new plan object.
delete_planDelete planDELETEDeletes an existing plan object. Note that when you delete a plan, the existing subscriptions will continue to be charged until they are canceled.
get_planGet planGETRetrieves an existing plan object.
list_plansList plansGETLists plan objects. Results are sorted by creation date, with the most recent objects first.
update_planUpdate planPOSTUpdates an existing plan object. Any parameters not provided are left unchanged.

Subscription, 5 operations

cancel_subscriptionCancel subscriptionDELETECancels an existing subscription.
create_subscriptionCreate subscriptionPOSTMoves real money on a schedule: subscribes a customer to a plan, and the customer's current default card is billed the plan amount times quantity each billing period (at once unless a trial applies).
get_subscriptionGet subscriptionGETRetrieves an existing subscription object.
list_subscriptionsList subscriptionsGETLists subscription objects. Results are sorted by creation date, with the most recent objects first.
update_subscriptionUpdate subscriptionPOSTUpdates an existing subscription object. Any parameters not provided are left unchanged.

Blacklist, 4 operations

create_blacklist_ruleCreate blacklist rulePOSTCreates a new blacklist rule object.
delete_blacklist_ruleDelete blacklist ruleDELETEDeletes an existing blacklist rule object.
get_blacklist_ruleGet blacklist ruleGETRetrieves an existing blacklist rule object.
list_blacklist_rulesList blacklist rulesGETLists blacklist rule objects. Results are sorted by creation date, with the most recent objects first.

Credit, 4 operations

create_creditCreate creditPOSTMoves real money: transfers funds to a card (a credit, not a refund of an earlier charge). Provide customerId (its default card is credited) or card. With a test key the card receives no funds. Available for selected business models only.
get_creditGet creditGETRetrieves an existing credit object. This feature is available for selected business models only. Please contact [email protected] to find out more.
list_creditsList creditsGETList credit objects. Results are sorted by creation date, with the most recent objects first. This feature is available for selected business models only.
update_creditUpdate creditPOSTUpdates an existing credit object. Any parameters not provided are left unchanged. This feature is available for selected business models only.

Payment link, 4 operations

create_payment_linkCreate payment linkPOSTCreates a new payment link. Every new payment link is active by default. An optional failed-payment limit can be set only at creation.
get_payment_linkGet payment linkGETRetrieves an existing payment link object.
list_payment_linksList payment linksGETLists payment link objects. Results are sorted by creation date, with the most recent objects first.
update_payment_linkUpdate payment linkPOSTUpdates an existing payment link. Attributes not provided in the request are left unchanged.

Payment method, 4 operations

create_payment_methodCreate payment methodPOSTCreates a new payment method for alternative payment types.
delete_payment_methodDelete payment methodDELETEDeletes a payment method by its id; it can no longer be used for charges.
get_payment_methodGet payment methodGETReturns one payment method by its id, with its type, status, customer and billing details.
list_payment_methodsList payment methodsGETLists the payment methods (alternative payment types such as ACH, iDEAL or wallets) saved for one customer; customerId is required.

Refund, 4 operations

create_refundCreate refundPOSTMoves real money: refunds a charge, returning funds to the card or payment method charged. Leave out amount to refund the full remaining amount. Partial refunds need a captured charge and can repeat until fully refunded.
get_refundGet refundGETRetrieves an existing refund object.
list_refundsList refundsGETList refund objects for a given charge. Results are sorted by creation date, with the most recent objects first.
update_refundUpdate refundPOSTUpdates an existing refund object. Any parameters not provided are left unchanged.

Checkout session, 3 operations

create_checkout_sessionCreate checkout sessionPOSTCreates a new checkout session. Sessions must be created using a secret API key.
get_checkout_sessionGet checkout sessionGETRetrieves an existing checkout session object.
list_checkout_sessionsList checkout sessionsGETLists checkout session objects. Results are sorted by creation date, with the most recent objects first.

Dispute, 3 operations

get_disputeGet disputeGETRetrieves an existing dispute object.
list_disputesList disputesGETLists dispute objects. Results are sorted by creation date, with the most recent objects first.
update_disputeUpdate disputePOSTUpdates an existing dispute object. Any parameters not provided are left unchanged.

File, 3 operations

create_file_uploadCreate file uploadPOSTCreates a new file upload object. A successful request returns a file upload object that represents the uploaded file.
get_file_uploadGet file uploadGETRetrieves an existing file upload object.
list_file_uploadsList file uploadsGETLists file upload objects. Results are sorted by creation date, with the most recent objects first.

Payout, 3 operations

create_test_payoutCreate test payoutPOSTTest mode only, moves no real money: creates a test payout from test mode charges, refunds, chargebacks and credits. Takes no parameters and works only with a test API key.
get_payoutGet payoutGETRetrieves an existing payout object.
list_payoutsList payoutsGETLists payout objects. Results are sorted by payout date, with the most recent objects first.

Event, 2 operations

get_eventGet eventGETRetrieves an existing event object.
list_eventsList eventsGETList event objects. Results are sorted by creation date, with the most recent objects first.

Fraud warning, 2 operations

get_fraud_warningGet fraud warningGETRetrieves an existing fraud warning object.
list_fraud_warningsList fraud warningsGETLists fraud warning objects. Results are sorted by creation date, with the most recent objects first.

Capture, 1 operation

capture_chargeCapture chargePOSTMoves real money: captures a previously authorized (uncaptured) charge, which bills the customer. This is the second step of a two-step payment flow (authorize then capture). Charges must be captured within 5 days of authorization.

Close, 1 operation

close_disputeClose disputePOSTClosing the dispute indicates that you do not want to submit any further evidence and acknowledge it as lost.

Deactivate, 1 operation

deactivate_payment_linkDeactivate payment linkPOSTDeactivates an existing payment link. Every new payment link is active by default.

Incremental authorization, 1 operation

incremental_authorizationIncremental authorizationPOSTMoves real money: raises the authorized amount of a pre-authorized charge by the given amount. The charge must have been created with captured=false and options.authorizationType=pre.

Payout transaction, 1 operation

list_payout_transactionsList payout transactionsGETLists payout transaction objects. Results are sorted by creation date, with the most recent objects first. Either the `payout` or the `source` parameter must be provided.

Reactivate, 1 operation

reactivate_payment_linkReactivate payment linkPOSTReactivates a deactivated payment link. A payment link cannot be reactivated once its limit of successful charges or failed payment attempts has been reached.

Token, 1 operation

get_tokenGet tokenGETRetrieves an existing token object.

Use Shift4 from Claude Code, Cursor or Codex

Connect Shift4 in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Shift4 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 Shift4

Create your workspace
Sign up free. Nothing to install.
Connect Shift4 once
Add your Shift4 connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.