Jenius Pay

DOKU has partenered with various Internet Banking and one of them is Jenius Pay. Learn more about how DOKU can help you integrate with Jenius Pay here.

---

Integration steps

Here is the overview of how to integrate with Jenius pay :

1. Generate request

2. Complete Payment in Jenius App

3. Acknowledge payment result

Jenius Pay

---

1. Generate request

To generate request, you will need to hit this API through your Backend:

API Request

Type	Value
HTTP Method	POST
API endpoint (Sandbox)	https://api-sandbox.doku.com/jenius-digital-banking/v2/ServiceRequestPayment
API endpoint (Production)	https://api.doku.com/jenius-digital-banking/v2/ServiceRequestPayment

Here is the sample of request header to generate order:

Client-Id: MCH-0001-10791114622547
Request-Id: baec7d95-f30a-4b78-b711-6ebe0ccdf50b
Request-Timestamp: 2021-07-07T08:45:42Z
Signature: HMACSHA256=vl9DBTX5KhEiXmnpOD0TSm8PYQknuHPdyHSTSc3W6Ps=

Request Header Explanation

Parameter	Description
Client-Id	Client ID retrieved from DOKU Back Office
Request-Id	Unique random string (max 128 characters) generated from merchant side to protect duplicate request
Request-Timestamp	Timestamp request on UTC time in ISO8601 UTC+0 format. It means to proceed transaction on UTC+7 (WIB), merchant need to subtract time with 7. Ex: to proceed transaction on September 22th 2020 at 08:51:00 WIB, the timestamp should be 2020-09-22T01:51:00Z
Signature	Security parameter that needs to be generated on merchant Backend and placed to the header request to ensure that the request is coming from valid merchant. Please refer to this section to generate the signature

Here is the sample request body to generate order:

{
"order": {
        "invoice_number": "DOKU202212345828",
        "amount": "50000",
        "line_items": [
            {
                "name": "Ayam",
                "price": 40000,
                "quantity": 1
            },
            {
                "name": "Roti",
                "price": 10000,
                "quantity": 1
            }
        ]
    },
    "additional_info": {
        "override_notification_url": "https://another.example.com/payments/notifications"
    },
    "customer": {
        "name": "Astari",
        "email": "[e-mail]",
        "phone": "081288910205"
    },
    "redirect_url": "https://test.com/redirect",
    "jenius_info": {
        "cash_tag": "$admin"
    }
}

Request Body Explanation

Parameter	Type	Mandatory	Description
order.invoice_number	string	Mandatory	Generated by merchant to identify the order and must unique per request. Must be same with Request-ID Allowed chars: alphabetic, numeric, special chars Max length: 64
order.amount	string	Mandatory	In IDR currency and without decimal Allowed chars: numeric Max length: 12
order.line_items.name	string	Mandatory	Name of the product item Allowed chars: alphabetic, numeric, special chars Max Length: 255
order.line_items.price	number	Mandatory	Price of the product item. Total price and quantity must match with the order.amount Allowed chars: numeric Max Length: 12
order.line_items.quantity	number	Mandatory	Quantity of the product item Allowed chars: numeric Max Length: 4
additional_info.override_notification_url	string	Optional	This parameter is intended to override the configured Notification URL with another URL. Click here for more information.
customer.name	string	Mandatory	Customer name that will be displayed on acquirer channel when do inquiry Allowed chars: alphabetic, numeric, special chars Max length: 64
customer.phone	string	Mandatory	Customer phone number. Format: {calling_code}{phone_number}. Example: 6281122334455 Allowed chars: numeric Max Length: 16
customer.email	string	Optional	Customer address Allowed chars: alphabetic, numeric, special chars Max Length: 400
redirect_url	string	Mandatory	Merchant URL that will redirected to after the order completed Allowed chars: alphabetic, numeric, special chars Max Length: 512
jenius_info.cash_tag	string	Mandatory	Unique identifier for customer to pay Allowed chars: alphabetic, numeric, special chars Max Length: 30

API Response

After hitting the above API request, DOKU will give the response.

Type	Value
HTTP Status	200
Result	SUCCESS

Client-Id: MCH-0001-10791114622547
Request-Id: baec7d95-f30a-4b78-b711-6ebe0ccdf50b
Response-Timestamp: 2021-07-07T08:45:42Z
Signature: HMACSHA256=9UPUFzOqJc47aJzD9ESOTcWg6TMsg3mqSP+DnUO8ENE=

Response Header Explanation

Parameter	Description
Client-Id	Same as the request
Request-Id	Same as the request
Response-Timestamp	Timestamp Response on UTC with format ISO8601 UTC+0 from DOKU
Signature	Signature generated by DOKU based on the response body

Here is the sample of response body:

{
    "order": {
        "invoice_number": "DOKU202212345828",
        "amount": "50000"
    },
    "internet_banking_payment": {
        "status": "SUCCESS"
    },
    "additional_info": {
        "override_notification_url": "https://another.example.com/payments/notifications"
    }
}

Response Body Explanation

Parameter	Type	Mandatory	Description
order.invoice_number	string	Mandatory	Same as the request
order.amount	string	Mandatory	Same as the request
internet_banking_payment.status	string	Mandatory	Transaction Status. Possible Value: Pending, Success, Failed, Refund
additional_info.override_notification_url	string	Optional	Same as the request

2. Complete Payment in Jenius App

After the customer completed the payment, they will be redirected to the defined redirect.url that you set on the API request.

---

3. Acknowledge payment result

After the payment is being made by your customer, DOKU will send HTTP Notification to your defined Notification URL. Learn how to handle the notification from DOKU:

• Handling DOKU HTTP Notification

---

Additional features

We provide various additional features to suited your needs. Learn more here.

Refund Order

If you wish to refund your order request, you can do that by hitting the API with POST method:

API Request

Type	Value
HTTP Method	POST
API endpoint (Sandbox)	https://api-sandbox.doku.com/jenius-digital-banking/v2/ServiceRequestRefund
API endpoint (Production)	https://api.doku.com/jenius-digital-banking/v2/ServiceRequestRefund

Here is the sample of request header to Refund Order:

Client-Id: MCH-0001-10791114622547
Request-Id: 2dc5985e-adaa-4f82-b126-b09e9006da14
Request-Timestamp: 2020-08-11T08:45:42Z
Signature: HMACSHA256=vl9DBTX5KhEiXmnpOD0TSm8PYQknuHPdyHSTSc3W6Ps=

Request Header Explanation

Parameter	Description
Client-Id	Client ID retrieved from DOKU Back Office
Request-Id	Unique random string (max 128 characters) generated from merchant side to protect duplicate request
Request-Timestamp	Timestamp request on UTC time in ISO8601 UTC+0 format. It means to proceed transaction on UTC+7 (WIB), merchant need to subtract time with 7. Ex: to proceed transaction on September 22th 2020 at 08:51:00 WIB, the timestamp should be 2020-09-22T01:51:00Z
Signature	Security parameter that needs to be generated on merchant Backend and placed to the header request to ensure that the request is coming from valid merchant. Please refer to this section to generate the signature

Here is the sample of request body to Refund Order:

{
    "order": {
        "invoice_number": "DOKU22022062000",
        "amount": "61000",
        "reason": "Cancel Order"
    }
}

Request Body Explanation

Parameter	Type	Mandatory	Description
order.invoice_number	string	Same as the generate request
order.amount	string	Same as the generate request
reason	string	Mandatory	Refund's Reason

API Response

After hitting the above API request, DOKU will give the response.

Type	Value
HTTP Status	200
Result	SUCCESS

Client-Id: MCH-0001-10791114622547
Request-Id: 09e0defe-a071-45b3-9feb-ac134374628c
Response-Timestamp: 2020-08-11T08:45:42Z
Signature: HMACSHA256=9UPUFzOqJc47aJzD9ESOTcWg6TMsg3mqSP+DnUO8ENE=

Response Header Explanation

Parameter	Description
Client-Id	Same as the request
Request-Id	Same as the request
Response-Timestamp	Timestamp Response on UTC with format ISO8601 UTC+0 from DOKU
Signature	Signature generated by DOKU based on the response body

Here is the sample of response body:

{
    "order": {
        "invoice_number": "DOKU202212345828",
        "amount": "61000"
    },
    "internet_banking_payment": {
        "status": "SUCCESS"
    }
}

Response Body Explanation

Parameter	Type	Mandatory	Description
order.invoice_number	string	Mandatory	Same as the request
`order.amount	string	Mandatory	Same as the request
internet_banking_payment.status	string	Mandatory	Status of the refund. Possible Value: 1. SUCCESS = If Jenius Pay approved refund request 2. FAILED = If Jenius Pay reject refund request

Split Settlement

If you are a platform or a marketplace, you can use this feature to settle the funds to your sellers or partners programmatically, save many operational efforts.

• Settlement