Token Developer Portal
OKC Platform
OKC Platform
  • Architecture
  • Quick Start Guide
  • Template Banking App
  • Payment Services
    • UI Components
    • Card Service
    • Bank App Protocol
    • SDK Integrations
    • 🆕Doviz POS Integration
    • In Car Pay Integration
  • System and Security Services
    • KMS Library
    • Device Library
    • RKL CA service
    • TMS Service
    • Printer Service
    • TokenUSDK
  • Versions
    • Platform Versions
Powered by GitBook
On this page
  • 1.In Car Pay Flow
  • 2.Bank App Protocol
  • 2.1 Sale
  • 2.2 Parameter
  • 3.Card Service
  • getCard(...) API Details
  • 4.Example Videos
  • 4.1.Sale Flow
  1. Payment Services

In Car Pay Integration

This project is designed specifically for 1000tr to enable customers to make fuel payments without leaving their vehicles.

PreviousDoviz POS IntegrationNextKMS Library

Last updated 24 days ago

1.In Car Pay Flow

2.Bank App Protocol

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

Add CarPayAllowed into Allowed Operations as Parameter Action Response Data if In Car Pay supported.

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

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

3.Card Service

getCard(...) API Details

.
.
.
"carPay": 1

Note: carPay should be set for getCard.

Returns getCard(...) API

"mCardReadType": 7
"resultCode":0
"mTranAmount1":2000

4.Example Videos

4.1.Sale Flow

Bank App Protocol
Card Service
8MB
inCarPaySale.mov
In car pay flow