> For the complete documentation index, see [llms.txt](https://developers.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.doku.com/accept-payments/direct-api/non-snap/card.md).

# Card

DOKU provides various payment channels. One of the most used is Credit Card. By using this payment channel, your customers can pay their order with their credit card or any online transaction capable debit card. DOKU has partenered with various banks and principals (Visa, MasterCard, JCB, Amex) to provide a secure and seamless payment experience for your customers.

***

#### Integration Option

You can integrate credit card payments into your platform through 3 different paths based on your PCI DSS scope and compliance level:

* 1\. Zero SAQ Scope (DOKU Checkout & DOKU Payment Page): If you are non-PCI DSS certified and want zero reporting overhead, integrate using DOKU Checkout or DOKU Payment Page. DOKU handles the card capture entirely on hosted environments, eliminating the need for merchants to submit an SAQ.
* 2\. Partial Scope — SAQ A-EP (DOKU JS): If you are non-PCI DSS certified but want to host the payment form on your own website, integrate using DOKU JS. DOKU securely processes card details via client-side JavaScript, requiring only a simplified SAQ A-EP self-assessment and quarterly ASV scans.
* 3\. Full Scope — SAQ D / QSA Audit (Host-to-Host API): If you are PCI DSS certified, you can integrate directly via our Host-to-Host (H2H) API. Because raw card details pass through your server, this integration requires maintaining full SAQ D compliance along with annual validation signed by a Qualified Security Assessor (QSA).

{% hint style="info" %}
Learn more about PCI DSS [here.](https://docs.doku.com/security/licenses/pci-dss-compliance)
{% endhint %}

#### **Supported Payment Type**

| Payment Type      | Description                                                                                                                                                                                                                                                                                                                                                                       |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SALE              | This is a single transaction where the authorization (approval of funds) and capture (deduction from the card) happen at the same time. It’s common for retail purchases where funds are immediately processed.                                                                                                                                                                   |
| Authorize Capture | This involves two steps. First, the **authorization** checks if funds are available and reserves them but doesn’t immediately deduct them. Later, a **capture** request completes the transaction and deducts the funds. Often used for services where a final amount might not be determined upfront, like hotels or rentals.                                                    |
| Installment       | Allows cardholders to split the payment over a series of periodic payments (e.g., monthly) instead of paying the entire amount upfront. It’s a way to make larger purchases more manageable and is generally arranged in collaboration with the acquiring bank.                                                                                                                   |
| MOTO              | <p>This is a type of transaction where the card is not physically present, typically used in orders taken over the phone or by mail. Merchants manually enter the card details into the system. each MOTO transaction is generally independent </p><p><code>Only available with Host-To-Host Integration</code> </p>                                                              |
| Recurring         | <p>Designed for ongoing services (like subscriptions), where the card is automatically charged at regular intervals (e.g., monthly). It requires the cardholder’s consent for ongoing billing and doesn’t need their card information every time. each recurring transaction is identified by the billing number<br><code>Only available with Host-To-Host Integration</code></p> |

***

Learn more how to start accept payments with Credit Card:

* [Payment Page Integration (for Non PCI DSS compliance)](/accept-payments/direct-api/non-snap/card/payment-page-integration-guide.md)