> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/ja/testing-your-app/publishing-to-the-apple-app-store/setup-annual-payment-for-your-apple-developer-account.md).

# Apple Developerアカウントの年間支払い設定

Apple Developer アカウントにサインアップする際に考慮すべき重要な情報

{% hint style="info" %}
**\*\*\* Apple は、開発者アカウントを維持するために年間$99の支払いを求めています**

1. Apple Developer アカウントが承認されると、メール内のリンクをクリックしてログインできます（またはこちらに移動: <https://developer.apple.com/account>）
2. サービス利用規約に同意します
3. 年間$99の料金の支払い情報を入力します（また、毎年自動的に料金が再発生するオプションを選択します）
   1. この支払いには48時間かかります
      {% endhint %}

## ヘルプ

この記事に関する追加のヘルプが必要な場合は、いつでも[コミュニティフォーラム](https://forum.adalo.com/)で質問できます！投稿時にこの記事へのリンクも貼り付けてください！


---

# 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://help.adalo.com/ja/testing-your-app/publishing-to-the-apple-app-store/setup-annual-payment-for-your-apple-developer-account.md?ask=<question>&goal=<user_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.