Integration

Worldline NA Payments integration

Card payment processing for North American merchants of Worldline (formerly Bambora North America and Beanstream). Charge a card, a single-use token from Worldline's client-side tokenization, or a stored payment profile, or record a cash or cheque payment; pre-authorize and later complete (capture) a payment, return (refund) part or all of it, or void it. Look a transaction up by id, with its refunds, completions and adjustments. Searching transactions and the settlement and statement reports belong to the Worldline NA Reporting integration and stored cards to Worldline NA Payment Profiles; 3-D Secure, Apple Pay, Google Pay and processor-token payments, card tokenization and partner sub-merchant calls are not exposed. Authentication is the Authorization header 'Passcode <key>': the key to store is the Base64 encoding of merchant_id:passcode, made from your Worldline merchant ID and the Payment API passcode set in the back office (the vendor docs offer an encoder).

Connect Worldline NA Payments How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Worldline NA Payments.Built from the 5 Worldline NA Payments tools below, on the connection you add once.

What you can do with Worldline NA Payments

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, 2 operations

get_transactionGet transactionGETReturns one transaction by id: amount, type, approval, message, card result, billing and shipping, custom fields, total refunds and completions, and the transactions that adjusted it (returns, voids, completions).
make_paymentMake paymentPOSTCharges or pre-authorizes a payment by card, single-use token or stored payment profile, or records a cash or cheque payment. Set complete false in the card, token or payment_profile object to pre-authorize only.

Completion, 1 operation

complete_preauthorizationComplete preauthorizationPOSTCompletes (captures) a pre-authorized payment for an amount less than or equal to the pre-authorized amount. The answer is a new transaction with its own id.

Return, 1 operation

return_paymentReturn paymentPOSTReturns (refunds) all or part of a completed payment to the customer. The amount must be at most the original purchase amount; the answer is a new return transaction.

Void, 1 operation

void_paymentVoid paymentPOSTVoids (cancels) a payment, a return or a pre-authorization completion. The amount must equal the original transaction amount.

Use Worldline NA Payments from Claude Code, Cursor or Codex

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

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