> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.runpayments.io/release-notes/2026/9/30/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.runpayments.io/_mcp/server.

## Terminal API

The Terminal API is now available in the Run Developer! Connect your software to P2PE-validated, card-present acceptance solutions via Run Developer. Your customers can swipe, dip, or tap on an integrated card reader, and your POS will receive a tokenized card or a completed charge without card data ever touching your systems. Read more in our [Terminal API Overview](/reference/terminal-api/overview).

To request a UAT device and credentials, please reach out to your Integration Delivery Lead or send a note to [integrations@runpayments.io](mailto:integrations@runpayments.io).

### Endpoints added

The following endpoints have been added to the Run Payments API Reference:

- ### Authentication: WebSocket
    - [`POST /api/ws-token`](/reference/terminal-api/authentication-web-socket/generate-ws-token): Generate a single-use WebSocket auth token.
- ### Terminals
    - [`GET /api/terminal`](/reference/terminal-api/terminals/list-terminals): List your terminals and their capabilities.
    - [`POST /api/terminal/{device_id}/connect`](/reference/terminal-api/terminals/connect-terminal): Connect a terminal session.
    - [`DELETE /api/terminal/{device_id}/disconnect`](/reference/terminal-api/terminals/disconnect-terminal): Disconnect a terminal session.
    - [`POST /api/terminal/{device_id}/ping`](/reference/terminal-api/terminals/ping-terminal): Ping a terminal.
- ### Card Read
    - [`POST /api/terminal/{device_id}/read-card`](/reference/terminal-api/card-read/read-card): Initiate a card read.
    - [`GET /api/terminal/{device_id}/read-card/{interaction_id}`](/reference/terminal-api/card-read/get-read-card-status): Get card read status.
    - [`DELETE /api/terminal/{device_id}/cancel/{interaction_id}`](/reference/terminal-api/card-read/cancel-read-card): Cancel a card read.
- ### Charge Card
    - [`POST /api/terminal/{device_id}/charge-card`](/reference/terminal-api/charge-card/initiate-charge): Read the card, optionally capture a signature, charge, and optionally deliver a receipt.
    - [`GET /api/terminal/{device_id}/charge-card/{interaction_id}`](/reference/terminal-api/charge-card/get-charge-card-status): Get charge status.
- ### Receipt
    - [`POST /api/terminal/{device_id}/print-receipt`](/reference/terminal-api/receipt/print-receipt): Print a receipt on the device.
    - [`POST /api/v1/send_receipt`](/reference/terminal-api/receipt/send-receipt): Email a receipt to your customer.

## Card Present Guides

The following guides have been added to the Run Developer site under **Guides > Payments > Card Present**:

- [Overview](/docs/guides/payments/card-present/overview): Choosing between the unified and two-step integration paths, supported devices, and the end-to-end flow
- [Getting Started](/docs/guides/payments/card-present/getting-started): Environment, authentication, and terminal capabilities
- [Interactions & Status](/docs/guides/payments/card-present/interactions-and-status): Polling, WebSockets, cancelling, and sessions
- [Unified Charge Workflow](/docs/guides/payments/card-present/unified-charge-workflow): Running `charge-card` and handling declines and `stage_errors`
- [Signatures & Receipts](/docs/guides/payments/card-present/signatures-and-receipts): Capturing signatures and printing or emailing receipts
- [Surcharging on Device](/docs/guides/payments/card-present/surcharging-on-device): Card-present surcharging for enrolled merchants
- [Endpoints & Errors](/docs/guides/payments/card-present/endpoints-and-errors): Endpoint summary, response codes, and error messages

## API Reference Navigation

We have reorganized the API Reference into two sections based on authentication method. Please note the updated locations below.

- **Processing** (Payments and Terminal APIs): Authenticate with your Payments API key as a bearer token. [Refresh API Keys](/reference/authentication/refresh-api-keys) has moved to its own **Authentication** section here.
- **Reporting & Boarding** (Reporting and Boarding APIs): Authenticate with OAuth 2.0 client credentials generated from Run Merchant or provided by your Run Integration Delivery rep.