> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/merchant-tokenization/ja/pcitkun/implement-pci-tokenization/process-a-transaction.md).

# トランザクションを処理する

支払い時にPCIトークンのデトークン化を行うにはこのフローを使用します。

## フロー

<figure><img src="https://726786440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9XBN1F9dv7Dl1ggilGWC%2Fuploads%2FuipXZxPWBszJbnHOeZtj%2FFlow%20-%20Process%20a%20transaction.svg?alt=media&amp;token=f969fb82-be9d-4155-9154-9ff91e308f0b" alt=""><figcaption><p>PCIトークナイゼーショントランザクションフロー</p></figcaption></figure>

<table><thead><tr><th width="100">ステップ</th><th>説明</th></tr></thead><tbody><tr><td>1</td><td>エンドユーザーが加盟店のウェブサイトまたはアプリでチェックアウトします。</td></tr><tr><td>2</td><td>加盟店またはPSPが呼び出します <code>createTransaction</code> および提供します <code>tokenId</code>.</td></tr><tr><td>3</td><td>Thalesのバックエンドがデトークン化を実行し、PANと有効期限を返します。</td></tr><tr><td>4</td><td>加盟店またはPSPはPANと有効期限を使用して承認を送信します。</td></tr></tbody></table>

## API

PCIトークナイゼーションでは、 `tokenId` および `transactionType` が必須です。

同じ `createTransaction` 操作をPCIトークナイゼーションと決済ネットワークのトークナイゼーションで使用します。

* API参照： [トランザクションの作成](broken://pages/aa59e31deefcb7087369eeed5322fc0609c32f30#post-v2-transactions)


---

# 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://docs.payments.thalescloud.io/merchant-tokenization/ja/pcitkun/implement-pci-tokenization/process-a-transaction.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.