> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/ja/i/credit-card-on-file.md).

# 登録済みクレジットカード

将来の請求のために、お客様のクレジットカードをファイルに保存または保持したいですか？SesamiとShopifyでこれを処理する方法はこちらです。

## Sesamiでの支払いの仕組み

Sesamiは支払いを直接処理しません。支払いはShopifyのチェックアウトシステムを通じて処理されます。ShopifyはPCI準拠を維持しているため、販売者はShopify管理画面でクレジットカード番号を手動で保存することはできません。

## 推奨：Downpay

[Downpay](https://apps.shopify.com/downpay) はSesamiと相性の良いShopifyアプリで、以下の機能を提供します：

* **カード情報の保存** ShopifyのAPI経由で
* **デポジットと一部支払い**
* 注文ページまたはPOSから残額を請求する

## 代替アプローチ

* **請求書を送る** 残額をお客様に
* **デポジットを請求する** 予約時に、残りは来店時に回収する（参照 [デポジット](https://help.sesami.co/ja/i/deposits.md))

## 関連項目

* [デポジット](https://help.sesami.co/ja/i/deposits.md) — 予約時に一部支払いを回収
* [ヒント](https://help.sesami.co/ja/i/tips.md) — チェックアウトにチップを追加


---

# 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.sesami.co/ja/i/credit-card-on-file.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.
