Integration

BlueSnap integration

BlueSnap is a payment gateway for online merchants. Charge or authorize a card through a vaulted shopper or a Hosted Payment Fields token, capture or void an authorization, read transactions, issue and cancel refunds, manage vaulted shoppers, billing plans and subscriptions (with their charges and switch pricing), run merchant-managed subscription charges, and read available funds. On a production (ws) connection every charge, capture, refund and subscription call moves real money; use a sandbox connection to test. Raw card numbers, CVV and bank account numbers are never accepted (PCI), and alternative payment methods, batch transactions, marketplace vendor management, wallets and reporting are not exposed. Authentication is HTTP Basic with the API username and password from the Merchant Portal (Settings > API Settings), whose authorized IP list must include the calling servers unless IP checking is disabled there. The environment field takes ws for production or sandbox for the sandbox.

Connect BlueSnap How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with BlueSnap

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.

Plan, 4 operations

create_planCreate planPOSTCreates a subscription billing plan: charge frequency, recurring amount and currency, plus an optional trial, initial charge, maximum number of charges and grace period. An account can have up to 40,000 plans.
get_planGet planGETReturns one billing plan: name, status, frequency, amounts, currency, trial and limits.
list_plansList plansGETLists the billing plans of the account, 10 per page by default, optionally only ACTIVE or INACTIVE ones.
update_planUpdate planPUTUpdates a plan's name, status, initial charge, trial days, grace period, maximum charges or charge-on-switch setting. The frequency, recurring amount and currency cannot change but must be sent with their current values.

Subscription, 4 operations

create_subscriptionCreate subscriptionPOSTSubscribes a vaulted shopper to a billing plan, whose stored card BlueSnap then charges on the plan's terms, with optional quantity and overrides of the plan's amounts or trial. Returns the subscription and its first charge.
get_subscriptionGet subscriptionGETReturns one subscription: plan, shopper, status, next charge date, amounts, quantity, auto-renew setting and payment source.
list_subscriptionsList subscriptionsGETLists the subscriptions of the account, 10 per page by default, optionally for one plan or one shopper, or by status.
update_subscriptionUpdate subscriptionPUTChanges a subscription's plan, quantity (with planId), recurring amount override, auto-renew, next charge date, stored card or status (ACTIVE or CANCELED). A switch to a plan with chargeOnPlanSwitch charges the shopper at once.

Vaulted shopper, 4 operations

create_vaulted_shopperCreate vaulted shopperPOSTCreates a vaulted shopper (a stored customer) with contact details, optionally adding the payment method held by a Hosted Payment Fields token (pfToken). Returns the shopper and its vaultedShopperId.
delete_vaulted_shopperDelete vaulted shopperDELETERequests the deletion of a vaulted shopper; BlueSnap processes it within 7 days and answers with a confirmation message.
get_vaulted_shopperGet vaulted shopperGETReturns a vaulted shopper: contact details, stored cards (last four digits, brand, expiry) and the payment method of the last purchase.
update_vaulted_shopperUpdate vaulted shopperPUTUpdates a vaulted shopper (firstName and lastName are required): contact details, a payment method added from a Hosted Payment Fields token (pfToken), or the default payment method.

Transaction, 3 operations

create_card_transactionCreate card transactionPOSTCharges or authorizes a card. AUTH_CAPTURE authorizes and submits for settlement in one request; AUTH_ONLY only authorizes (finish later with update_card_transaction).
get_card_transactionGet card transactionGETReturns a past card transaction: type, amount, currency, cardholder or vaulted shopper, card (last four digits), processing result, refunds and metadata.
update_card_transactionUpdate card transactionPUTCaptures a previously authorized (AUTH_ONLY) transaction for settlement, in full or in part (CAPTURE), or voids an authorization that was not captured, within 8 days of it (AUTH_REVERSAL).

Ondemand, 2 operations

create_merchant_managed_subscriptionCreate merchant managed subscriptionPOSTCharges a vaulted shopper's stored card now and starts a subscription whose later charges you trigger yourself with create_merchant_managed_subscription_charge. Returns the charge with the new subscriptionId.
create_merchant_managed_subscription_chargeCreate merchant managed subscription chargePOSTCharges a merchant-managed subscription again (amount and currency required), with an optional description and period in chargeInfo. Returns the charge.

Available fund, 1 operation

get_available_fundsGet available fundsGETReturns the current balance of the merchant (or of one marketplace vendor) per legal entity region and currency, with pending refunds.

Charge, 1 operation

list_subscription_chargesList subscription chargesGETLists the charges processed for one subscription, 10 per page by default: amount, currency, date, period, processing result and refunds.

Pending refund, 1 operation

cancel_pending_refundCancel pending refundDELETECancels a refund still pending (waiting for funds), given the transaction ID it belongs to. Returns no content.

Refund, 1 operation

refund_transactionRefund transactionPOSTRefunds a transaction in full, or in part with amount, in its original currency; transactions older than 2 years cannot be refunded. By default it also cancels the related subscription.

Switch charge amount, 1 operation

get_subscription_switch_charge_amountGet subscription switch charge amountGETReturns what the shopper would be charged if the subscription switched to another plan, quantity or amount (0.00 when the switch leaves a negative balance). Changes nothing.

Use BlueSnap from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect BlueSnap once
Add your BlueSnap 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.