Toss Payments API
✓ Official Vendor SpecPaymentsPayment Processingbasic4 EndpointsREST
For Agents
Programmatically confirm payment (결제 승인), query payment by paymentkey (paymentkey로 결제 조회). Covers 4 operations with basic authentication.
Use for: I need to confirm payment (결제 승인), I want to query payment by paymentkey (paymentkey로 결제 조회), Search for query payment by orderid (orderid로 결제 조회), Find all cancel payment (결제 취소)
Not supported: Does not handle communications, crm, or developer tools — use for payments only.
Toss Payments (토스페이먼츠) is a major Korean payment gateway. The API supports payment confirmation, payment inquiry, and payment cancellation. Authentication uses Basic auth with the secret key. Payments are initiated via the client SDK and confirmed server-side. The API exposes 4 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Toss Payments API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Toss Payments API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Toss Payments API.
Confirm Payment (결제 승인)
Query Payment by paymentKey (paymentKey로 결제 조회)
Cancel Payment (결제 취소)
Query and filter Toss Payments API records by parameters
Monitor Toss Payments API operational status and events
Use Cases
Patterns agents use Toss Payments API for, with concrete tasks.
★ Payments Operations
Use the Toss Payments API to perform payments operations programmatically. The API provides 4 endpoints covering core functionality including confirm payment (결제 승인), query payment by paymentkey (paymentkey로 결제 조회), query payment by orderid (orderid로 결제 조회).
Call POST /v1/payments/confirm to confirm payment (결제 승인)
Automated Payments Management
Automate payments operations by combining multiple Toss Payments API endpoints. Agents can query payment by paymentkey (paymentkey로 결제 조회) and then query payment by orderid (orderid로 결제 조회) in a single workflow.
Call GET /v1/payments/{paymentKey} to query payment by paymentkey (paymentkey로 결제 조회), then verify the result
AI Agent Integration via Jentic
AI agents discover and call Toss Payments API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.
Search Jentic for 'confirm payment (결제 승인)', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — toss payments (토스페이먼츠) is a major korean payment gateway.
METHOD
PATH
DESCRIPTION
POST
/v1/payments/confirm
Confirm Payment (결제 승인)
GET
/v1/payments/{paymentKey}
Query Payment by paymentKey (paymentKey로 결제 조회)
GET
/v1/payments/orders/{orderId}
Query Payment by orderId (orderId로 결제 조회)
POST
/v1/payments/{paymentKey}/cancel
Cancel Payment (결제 취소)
POST
/v1/payments/confirm
Confirm Payment (결제 승인)
GET
/v1/payments/{paymentKey}
Query Payment by paymentKey (paymentKey로 결제 조회)
GET
/v1/payments/orders/{orderId}
Query Payment by orderId (orderId로 결제 조회)
POST
/v1/payments/{paymentKey}/cancel
Cancel Payment (결제 취소)
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Toss Payments API basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'confirm payment (결제 승인)') and Jentic returns the matching Toss Payments API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Toss Payments API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Toss Payments API through Jentic.
What authentication does the Toss Payments API use?
The Toss Payments API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I confirm payment (결제 승인) with the Toss Payments API?
Yes. Use the POST /v1/payments/confirm endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Toss Payments API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I confirm payment (결제 승인) through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'confirm payment (결제 승인)'. Jentic returns the matching Toss Payments API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Toss Payments API have?
The Toss Payments API exposes 4 endpoints covering payments operations.
GET STARTED