Payment connectorMixed MCP + CDP

Commerce-specific execution without leaking payment tools everywhere

Payment is Scout's commerce connector: a dedicated surface for balances, challenge flows, payment execution, and money-moving workflows.

balancechallengeauthorizesettle

See connector reference Browse connectors

The settlement rail

Ledger lines, authorization gates, settlement bands, and warm gold accents that make money movement feel deliberate rather than casual.

A guarded commerce rail: balances, challenges, pay flows, transfers, and confirmations moving through explicit checkpoints instead of ambient permission.

Identity

Payment makes monetary capability explicit, narrow, and visible.

Payment tools should never feel like ordinary utility functions. They represent value movement, account state, commerce flows, and decisions that deserve their own boundary.

This connector turns commerce into a deliberate rail: every capability is named, every flow is scoped, and every money-moving action belongs to a visible surface.

State

balance and intent

Signal

challenge gates

Loop

quote, confirm, settle

Best for

Balance checks, commerce flows, challenge handling, and payment execution.

Agent workflows that need commerce-specific tools without broad browser or system access.

Operational tasks where payment state is part of the workflow boundary, not an afterthought.

Runtime model

Keeps balances, checkout flows, challenge handling, and transfers inside a dedicated commerce connector.

Avoids pushing payment-specific behavior into unrelated browser or orchestration surfaces.

Makes monetary actions an explicit capability boundary with a narrower operational surface.

Auth model

Authenticate through the normal Scout account boundary before exposing payment tools to an MCP client.

Keep payment access isolated so checkout, balances, and challenge flows are not mixed into unrelated connector setups.

Expose this connector only to workflows that genuinely need commerce-specific execution.

Capability atlas

A compact map of what this connector can do.

Payment exposes 5 commands across 1 capability groups. The full reference stays close, while this page keeps the connector's runtime shape easy to understand.

Payment

Read balances, stage challenges, run pay flows, and move funds through the payment connector.

payment-balancepayment-challengepayment-commercepayment-paypayment-transfer

Connection

Add the connector deliberately.

Add the hosted connector endpoint your MCP client needs. Each public connector stays separate so agent permissions and runtime boundaries remain explicit.

SnippetJSON

{
  "mcpServers": {
    "scout-payment": {
      "type": "http",
      "url": "https://mcp.scout.i.ng/payment"
    }
  }
}

Keep connector boundaries intentional

Dedicated connector pages should make capability boundaries memorable before the agent ever receives tools.

Browse all connectors Back to docs reference