Integration

Worldline NA Payment Profiles integration

Secure payment profiles of Worldline North America (formerly Bambora North America and Beanstream): store a customer's card, bank account and billing details on Worldline's servers and charge them later without collecting them again. Create a profile from a single-use token, a card, a bank account or a past transaction, read, update and delete it, and add, list, update and delete the cards it holds (one card per profile unless the back office allows more). Charging a profile is done with make_payment in the Worldline NA Payments integration. 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 Profiles API passcode set in the back office (the vendor docs offer an encoder).

Connect Worldline NA Payment Profiles How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Worldline NA Payment Profiles

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.

Card, 5 operations

add_profile_cardAdd profile cardPOSTAdds a card to a payment profile, from a single-use token (recommended) or card details. A profile holds one card by default; the back office sets the limit.
delete_profile_cardDelete profile cardDELETEDeletes one stored card, by its card_id, from a payment profile.
get_profile_cardGet profile cardGETReturns one card stored on a payment profile: masked number, cardholder name, expiry, card type and whether it is the default.
list_profile_cardsList profile cardsGETLists the cards stored on a payment profile, each with its card_id, masked number, expiry, card type and whether it is the default (function DEF).
update_profile_cardUpdate profile cardPUTUpdates a stored card. When the account allows several cards per profile only the expiry can change; to replace the number, add a new card and delete the old one.

Profile, 4 operations

create_profileCreate profilePOSTCreates a payment profile from at least one source: token (recommended), card, bank_account or a past transaction (create_from_id); a card and a bank account may be stored together. Returns the profile id as customer_code.
delete_profileDelete profileDELETEDeletes the payment profile whose id (customer_code) is given, as returned by create_profile.
get_profileGet profileGETReturns a payment profile: status, billing address, default card (masked number, expiry, card type), language, custom fields and the dates of its last transaction and last change.
update_profileUpdate profilePUTUpdates a payment profile: billing details, comment, language, a bank account, or the card of a single-card profile (send token or card). On a multi-card profile change cards with the card tools instead.

Use Worldline NA Payment Profiles from Claude Code, Cursor or Codex

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

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