# Kartu Kredit Indonesia Cepat Secure(KKI CPTS)

## Kartu Kredit Indonesia (KKI)

Kartu Kredit Indonesia is a new payment method initiated by Bank Indonesia & Asosiasi Sistem Pembayaran Indonesia(ASPI), instead of the usual credit card scheme transaction which uses PAN, Expiry Date, CVV, it instead requires CPAN (Customer PAN), and OTT(One Time Token) and Confirmation on Issuer's App so payment request can be security authenticated and authorized.

### Issuers Channels Supported

DOKU Is one of the first-mover Acquirer partnered with BI & ASPI with multiple issuers(Banks) to enable merchant to perform payment using KKI Channel

| Supported Issuers |
| ----------------- |
| BRI               |
| Mandiri           |
| BPD Bali          |
| BJB               |
| DKI Jakarta       |

With many more coming soon and will be automatically supported when available.

#### Integration Option

You can integrate credit card in two ways based on the PCI DSS compliance:

* Non-PCI DSS certified merchant is allowed to integrate using our [Checkout Page](/accept-payments/doku-checkout.md), where we will process customer's card information securely for you
* If you are  PCI DSS certified, you can integrate through [ H2H (Host to Host) API ](/accept-payments/direct-api/snap/integration-guide/kartu-kredit-indonesia-cepat-secure-kki-cpts/host-to-host-integration.md)

#### **What is PCI DSS?**

The Payment Card Industry Data Security Standard (PCI DSS) is an information security standard for organizations that handle branded credit cards from the major card schemes. The PCI Standard is mandated by the card brands but administered by the Payment Card Industry Security Standards Council.

### Payment Type

| Payment Type                   | Description                                                                                                                                                                                                                                                      |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Single Time Payment            | <p></p><p>A single transaction where the payment is processed only once using One Time Token(OTT) Generated by Issuer</p>                                                                                                                                        |
| Payment with Binding           | In a single transaction where the payment is processed only once using a time Token(OTT) Generated by the Issuer, the CPAN will be tokenized afterward for subsequent payment                                                                                    |
| Payment with Token             | In this type, a token (a secure digital representation of the card data) is generated and used for the transaction instead of the actual CPAN This token can be used securely for subsequent transactions, as the real card data is kept safe and isn’t exposed. |
| Payment without Authentication | This transaction type skips additional authentication steps, such as PIN or OTP (One-Time Password) on the issuer's application. This type of payment needs a token &  compatible for subscription-based transaction                                             |

## Interested in KKI ?

Do you think that might KKI might suits your project? Send your request [here](mailto:jokul@doku.com?subject=%5BRequest%5D%20Add%20New%20Plugin%3A%20Others)!


---

# Agent Instructions: 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:

```
GET https://developers.doku.com/accept-payments/direct-api/snap/integration-guide/kartu-kredit-indonesia-cepat-secure-kki-cpts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.