How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

xdata-kr Billing Payment Methods API

The Billing Payment Methods API from xdata-kr — 8 operation(s) for billing payment methods.

xdata-kr Billing Payment Methods API is one of 31 APIs that xdata-kr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Billing Payment Methods. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 8 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

10 operations 8 paths 13 schemas 1 DELETE4 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Authentication
HTTP Basic, OAuth 2.0
Resource Areas
1

Authentication & Security 2

xdata-kr Billing Payment Methods API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicClientCredential). It supports OAuth 2.0 (mcpOAuth2) using the authorizationCode flow. By default, every request must be authenticated.

  • basicClientCredential — Console-issued client credential. Send Authorization: Basic base64(clientid:clientsecret).
  • mcpOAuth2 — For MCP clients. OAuth 2.0 authorization code flow with PKCE (S256) for public clients. The clientid is the HTTPS URL of an OAuth Client ID Metadata Document t…

Paths & Operations 10

Across 8 paths, the API surfaces 10 operations — 1 DELETE, 4 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Billing Payment Methods 10
GET
/v1/payment-methods/capabilities
Get Payment Method Capabilities
get_payment_method_capabilities_v1_payment_methods_capabilities_get 3 params → 200422
POST
/v1/payment-methods/payup-hub/registrations
Start a card registration
start_card_registration_v1_payment_methods_payup_hub_registrations_post 4 params body → 201422
GET
/v1/payment-methods/payup-hub/registrations/{registration_id}
Get Card Registration
get_card_registration_v1_payment_methods_payup_hub_registrations__registration_id__get 4 params → 200422
POST
/v1/payment-methods/payup-hub/registrations/{registration_id}/cancel
Cancel Card Registration
cancel_card_registration_v1_payment_methods_payup_hub_registrations__registration_id__cancel_post 4 params → 200422
POST
/v1/payment-methods/billing-auth/session
Create Billing Auth Session
create_billing_auth_session_v1_payment_methods_billing_auth_session_post 3 params → 200422
POST
/v1/payment-methods/from-billing-auth
Register Payment Method From Billing Auth
register_payment_method_from_billing_auth_v1_payment_methods_from_billing_auth_post 4 params body → 201422
POST
/v1/payment-methods
Register Payment Method
register_payment_method_v1_payment_methods_post 4 params body → 201422
GET
/v1/payment-methods
List Payment Methods
list_payment_methods_v1_payment_methods_get 4 params → 200422
GET
/v1/payment-methods/{payment_method_id}
Get Payment Method
get_payment_method_v1_payment_methods__payment_method_id__get 4 params → 200422
DELETE
/v1/payment-methods/{payment_method_id}
Revoke Payment Method
revoke_payment_method_v1_payment_methods__payment_method_id__delete 5 params → 204422

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are PaymentMethodResponse (11 properties), PaymentMethodRegisterRequest (8 properties), PayupHubCardRegistrationResponse (7 properties), PaymentMethodRegisterFromBillingAuthRequest (7 properties). Each schema is shown below with its type and property counts.

ValidationError
object
5 properties 3 required
PayupHubCardRegistrationResponse
object
등록의 현재 상태(조회 · 취소 응답).
7 properties 3 required
PaymentMethodListQuery
object
결제수단 목록 조회 쿼리. 자동 필터(라우트/서비스 강제 적용, 쿼리 미노출): - organizationid = principal.organizationid - envscope = X-Env-Scope - status != 'REVOKED' (REVOKED는 명시적 옵션으로만 포함)
3 properties
PayupHubCardRegistrationStartRequest
object
카드 등록 시작 요청. 카드 칸이 없다.
4 properties 3 required
BillingAuthSessionResponse
object
Toss billing-auth session response.
3 properties 3 required
PaymentMethodRegisterRequest
object
결제수단 등록 요청. 클라이언트는 PG SDK로 카드 토큰화를 마친 뒤 billingkey만 본 API로 전달한다. 평문 카드정보(PAN/CVV/유효기간)는 절대 전송되지 않으며, 위반 시 422 VALIDATION + 보안 사고로 분류된다. organizationid는 요청 주체의…
8 properties 4 required
PageEnvelope_PaymentMethodResponse_
object
3 properties
PaymentMethodRegisterFromBillingAuthRequest
object
Toss from-billing-auth register request.
7 properties 4 required
PaymentMethodCapabilitiesResponse
object
결제수단 기능 켜짐 여부 (GET /v1/payment-methods/capabilities, U3-H).
1 property 1 required
HTTPValidationError
object
1 property
PaymentMethodResponse
object
결제수단 단일 객체 응답. billingkey 필드 부재가 본 응답 모델의 가장 중요한 정합 강제 — 응답 직렬화 시 평문 PG 토큰이 절대 외부로 노출되지 않는다 - 전송 금지와 저장 금지를 함께 지킨다. SCHEMA → DTO 매핑: - paymentmethods.id → paym…
11 properties 7 required
PayupHubCardRegistrationStartResponse
object
카드 등록 시작 응답 - 호스팅창을 여는 데 필요한 값.
5 properties 5 required
RegistrationConsent
object
카드로 구독 요금이 주기마다 자동 결제되는 것에 동의했다는 표시. 고객이 본 고지(문안 판 2026-10-27-a)의 내용: 월정액 플랜은 매월, 연 결제 플랜은 매년 1회 자동 청구된다. 구독 해지와 결제 수단 삭제는 결제 관리 화면에서 언제든지 할 수 있고, 해지 시 회사의 환불…
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xdata-kr-billing-payment-methods-api-openapi.yml Raw ↑

Other APIs xdata-kr publishes across the network.

xdata-kr App Credential API
xdata-kr Auth API
xdata-kr Auth Handoff API
xdata-kr Billing Invoices API
xdata-kr Billing Payments API
xdata-kr Billing Plans API
xdata-kr Billing Refunds API
xdata-kr Billing Standard Checkout API
xdata-kr Billing Subscriptions API
xdata-kr Billing Webhooks API
xdata-kr Composite Pack API
xdata-kr Console Self Service API
Where this information came from

This is an independent, third-party profile of xdata-kr Billing Payment Methods API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.