> For the complete documentation index, see [llms.txt](https://developer.tokeninc.com/token-developer-portal-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.tokeninc.com/token-developer-portal-1/payment-service/payment-solutions/in-car-pay-integration.md).

# In Car Pay Integration

## 1.In Car Pay Flow

<figure><img src="/files/FQ4KK7cjiPBrlI3GTpAr" alt=""><figcaption><p>In car pay flow</p></figcaption></figure>

## 2.Bank App Protocol

{% content-ref url="/pages/wkkoYfhTR7oCHd9CUvC2" %}
[Bank App Protocol](/token-developer-portal-1/payment-service/payment-services/bank-app-protocol.md)
{% endcontent-ref %}

### **2.1 Sale**

Add below datas and use them in your In Car Pay flow.

**plate** :  String: Plate number of the refueled vehicle. Ex:   "34AA111"

### **2.2 Parameter**&#x20;

Add CarPayAllowed into **Allowed Operations** as Parameter Action Response Data if In Car Pay supported.&#x20;

**Allowed Operations**

Allowed Operations will be added with the "AllowedOperations" tag. The allowed transactions will be added as JSON Object, whether the terminal allows payment with QR or not and whether it allows Key In transactions. It will be indicated with “1” if the operation is allowed, “0” if not.

Allowed Operations Bundle Example

```java
AllowedOperations={"QrAllowed":1,"KeyInAllowed":0, "DovizPOSAllowed":1, "CarPayAllowed":1}
```

## **3.Card Service**

{% content-ref url="/pages/Qsoan0HeKU22qZpHiBmg" %}
[Card Service](/token-developer-portal-1/payment-service/payment-services/card-service.md)
{% endcontent-ref %}

### **getCard(...) API Details**

```java
.
.
.
"carPay": 1
```

<mark style="color:red;">Note</mark>: carPay should be set  for **getCard.**

**Returns getCard(...) API**&#x20;

<pre class="language-java"><code class="lang-java">"mCardReadType": 7
"resultCode":0
<strong>"mTranAmount1":2000
</strong></code></pre>

## 4.Example Videos

### 4.1.Sale Flow

{% file src="/files/27TbYuxvfO7V0OgGvNPp" %}


---

# 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://developer.tokeninc.com/token-developer-portal-1/payment-service/payment-solutions/in-car-pay-integration.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.