> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/userguide/plan/payment.md).
# 결제 수단
## 신용카드
회원가입 시, 등록한 '신용카드' 정보로 매 월 플랜 구독이 자동 연장됩니다. 결제 정보 수신 이메일을 입력해 주시면 결제 성공 또는 실패 결과를 메일로 보내드립니다. [\[->결제 정보 수신 이메일 등록하기\]](/userguide/plan/plan.md#undefined-3)
## 결제카드 변경
1. \[상단 프로필] > \[결제 관리] > \[결제 수단]으로 이동합니다.
2. \[결제 수단] > \[변경] 버튼을 클릭합니다.
3. \[결제 카드 등록 팝업]에서 변경할 카드 정보를 입력하고 **\[재등록]** 버튼을 클릭하면, 다음 결제일부터 변경된 카드로 결제됩니다.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.charlla.io/userguide/plan/payment.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
