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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
ADRO

ADRO Payments API

The payments API from ADRO — 12 operation(s) for payments.

Documentation Provider Profile APIs.io OpenAPI GitHub

ADRO Payments API is one of 32 APIs that ADRO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 13 operations across 12 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against the base URL https://api.aoxlabs.com.

13 operations 12 paths 15 schemas 6 GET6 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.aoxlabs.com
Resource Areas
1

Paths & Operations 13

Across 12 paths, the API surfaces 13 operations — 6 GET, 6 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Payments 13
POST
/billing-keys/
빌링키 등록 (프론트가 SDK 콜백에서 받은 billingKey 를 팀에 묶어 저장)
billing_keys_create body → 201
GET
/billing-keys/bypass-hint/
빌링키 발급 SDK 호출에 필요한 PG 별 bypass 페이로드 + channelkey.
billing_keys_bypass_hint_retrieve 1 param → 200
GET
/billing-keys/current/
현재 활성(ISSUED) 결제수단 1건 조회.
billing_keys_current_retrieve 1 param → 200
POST
/billing-keys/payletter/register-and-charge/
PayLetter requestIssueBillingKeyAndPay 콜백 처리 (빌링키 발급 + 첫결제 동시).
billing_keys_payletter_register_and_charge_create body → 201
POST
/billing-keys/swap/
PG 인증 성공 뒤, 서버 트랜잭션에서 청구 프로필과 새 빌링키를 함께 등록한다.
billing_keys_swap_create body → 201
GET
/payments/
Payments retrieve
payments_retrieve → 200
GET
/payments/{payment_id}/
Payments retrieve 2
payments_retrieve_2 1 param → 200
POST
/payments/{payment_id}/checkout-cancel/
결제창 취소/실패 마킹.
payments_checkout_cancel_create 1 param body → 200
POST
/payments/{payment_id}/verify/
결제 검증 (포트원 GET /payments 로 재조회 후 동기화)
payments_verify_create 1 param → 200
GET
/payments/billing-profile/
Read or update the Team billing profile
payments_billing_profile_retrieve 1 param → 200
PUT
/payments/billing-profile/
Read or update the Team billing profile
payments_billing_profile_update 1 param body → 200
GET
/payments/checkout-options/
Team checkout options derived from a saved or temporary billing country
payments_checkout_options_retrieve 2 params → 200
POST
/payments/prepare/
단건결제 준비 (paymentId 채번). 팀 단위 결제
payments_prepare_create body → 201

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are OneTimePrepareResponse (27 properties), Payment (26 properties), BillingKey (16 properties), BillingMethodSwap (13 properties). Each schema is shown below with its type and property counts.

BillingKeyBypassResponse
object
빌링키 발급 SDK 호출 전 프론트가 가져갈 bypass 페이로드. 별도 prepare 단계가 없는 PG 가 SDK 호출에 추가 파라미터를 요구할 때 사용한다.
2 properties 2 required
ProviderCheckoutOption
object
2 properties 2 required
BillingKeyRegisterAndChargePayletterRequest
object
PayLetter requestIssueBillingKeyAndPay 콜백 처리용. 프론트는 사전에 /payments/prepare/?provider=payletter 로 paymentId 를 채번해 SDK 호출에 사용하고, 콜백에서 받은 billingKey + paymentId 를…
3 properties 3 required
OneTimePrepareRequest
object
7 properties 3 required
BillingKey
object
16 properties 5 required
CheckoutOptions
object
4 properties 4 required
BillingKeySwapRequest
object
결제수단 변경(swap) 요청. 프론트 흐름: - PayLetter : /payments/prepare/?provider=payletter 로 소액 paymentId 채번 → requestIssueBillingKeyAndPay 로 발급+소액결제 → 콜백 billingKey + paym…
9 properties 5 required
PaymentCancellation
object
5 properties 3 required
TeamBillingProfile
object
7 properties 1 required
BillingKeyRegisterRequest
object
4 properties 2 required
Payment
object
26 properties 14 required
OneTimePrepareResponse
object
단건결제 준비 응답. PaymentSerializer 의 모든 필드 + bypass. bypass: PG 별로 프론트 SDK 호출에 필요한 추가 페이로드 (예: Galaxia ITEMCODE). Galaxia/PayLetter/PayPal 각각 백엔드가 채워 보내므로 프론트는 그대로…
27 properties 15 required
CheckoutCancelRequest
object
결제창 취소/실패 마킹 요청. FE SDK 의 취소·실패 콜백에서 받은 메시지를 그대로 전달. PG/SDK 별 문구(Galaxia '[1111, 00] 사용자 결제취소', PayLetter/PayPal '사용자가 결제를 취소하였습니다.' 등)는 FE 가 원문을 그대로 넣고, 백엔드는…
1 property
BillingMethodSwap
object
결제수단 변경(swap) 결과. 새 빌링키 + 후속(환불/폐기) 결과 플래그. refundfailed / olddeletefailed 가 true 면 발급은 성공했으나 후속이 일부 실패한 것 (status=COMPLETEDWITHWARNINGS) — note 에 사유. CS/재시도 대…
13 properties 8 required
CurrentBillingMethod
object
현재 활성 결제수단 — 표시용 메타만 노출. 보안: raw billingkey 는 PortOne 결제 호출용 credential 이므로 브라우저에 절대 내려주지 않는다 (노출 시 결제 abuse 표면 증가). 구독/결제/교체 호출은 서버가 팀의 활성 빌링키를 직접 resolve 하므로…
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

adro1b33-payments-api-openapi.yml Raw ↑

Other APIs ADRO publishes across the network.

ADRO US Store Agent Commerce (UCP / MCP)
AE Profile APIs.io
ADRO Accounts API
AE Profile APIs.io
ADRO AI API
AE Profile APIs.io
ADRO Announcements API
AE Profile APIs.io
ADRO Artifacts API
AE Profile APIs.io
ADRO Asset Notifications API
AE Profile APIs.io
ADRO Assets API
AE Profile APIs.io
ADRO Board API
AE Profile APIs.io
ADRO Book Demo API
AE Profile APIs.io
ADRO Credits API
AE Profile APIs.io
ADRO Deletion Executions API
AE Profile APIs.io
ADRO Error Feedback API
AE Profile APIs.io
#Payments
← Back to A APIs
API Details
ID
adro1b33:adro1b33-payments-api
Base URL
https://api.aoxlabs.com
Docs
https://api.aoxlabs.com/swagger/
Provider
ADRO
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=adro1b33-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/adro1b33-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of ADRO Payments 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.