> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/soap-api-reference/soap-api-6.0.md).

# SOAP API 6.0

Before you start using the 2Checkout API to place orders with credit cards, check your **PCI DSS compliance status**. Find out more details about what PCI compliance means and what you should do to be PCI compliant [here](https://verifone.cloud/docs/2checkout/Onboarding/Merchant-PCI-Compliance/).  

{% hint style="info" %}
[See here](https://verifone.cloud/docs/2checkout/API-Integration/JSON-RPC_API_6.0/API-6.0-Error-Codes/Error-handling-for-API-6.0/) how to tackle the APIv6 errors that may arise when using the **placeOrder** call via 2Checkout API.
{% endhint %}

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>Authentication process in the 2Checkout system.</td><td><a href="/pages/TsRxGojcbLoOox5AELDG" class="button primary" data-icon="key">Authentication</a></td></tr><tr><td>Perform easy account management via API Requests.</td><td><a href="/pages/17OancFVYnhhZTmCuLLJ" class="button primary" data-icon="file-arrow-up">API Requests</a></td></tr><tr><td>Objects returned as API responses.<br><br></td><td><a href="/pages/f6EckSqlnDcZH4c8HFZq" class="button primary" data-icon="file-arrow-down">API Responses</a></td></tr><tr><td>Increase security of online card transactions by checking customer identities before allowing them to finalize purchase</td><td><a href="/pages/NMs8gP8nz6l2D0S0sMjd" class="button primary" data-icon="shield-check">3D Secure flow for API orders</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.2checkout.com/soap-api-reference/soap-api-6.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.