Integration

Worldline NA Reporting integration

Reporting APIs of Worldline North America (formerly Bambora North America and Beanstream): search transactions by date range and by criteria on 24 fields (amount, order number, card owner, billing email, reference fields...), get card settlement reports (amounts, fees, chargebacks and reserves per settlement day) and monthly statement fee reports. Channel partners can also read their sub-merchant report and FlexCommissions payouts. Reading one transaction by id is get_transaction in the Worldline NA Payments integration, which takes the Payment API passcode. 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 Reporting API access passcode (back office: administration, account settings, order settings).

Connect Worldline NA Reporting How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Worldline NA Reporting

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.

Merchant, 2 operations

get_sub_merchantGet sub merchantGETChannel partners only: returns the merchant report of one sub-merchant: boarding status, address, processor, batch and settlement settings, enabled card brands and features.
list_sub_merchantsList sub merchantsGETChannel partners only: lists the merchant and its sub-merchants with their boarding status, address, processor, batch and settlement settings, enabled card brands and features.

Commission, 1 operation

get_commissions_reportGet commissions reportGETChannel partners only: returns FlexCommissions payouts (amount, payout period, expected settlement date, statement id, status), for a date range or a number of past days.

Report, 1 operation

search_transactionsSearch transactionsPOSTSearches transactions between two dates, optionally filtered by criteria (all ANDed), and returns them a page at a time (at most 500 rows per call). An empty records list means nothing matched.

Settlement, 1 operation

get_settlement_reportGet settlement reportGETReturns card settlement records between two dates (at most three months apart, today excluded): per settlement day, the net amount, state, expected funding date, sales, returns, chargebacks, fees and reserves.

Statement, 1 operation

get_statement_reportGet statement reportGETReturns the fees charged on the monthly statements between two months: fee type, volume, rate and amount per statement. For partner accounts it also gives each sub-merchant's fees and the commission earned.

Use Worldline NA Reporting from Claude Code, Cursor or Codex

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

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