Configure payments3 min read

Connect DOKU QRIS and test the connection

Connect a DOKU account with QRIS already active. Follow the same guide as the OurBooth payment panel; illustrations use sample data.

Version reference: Android 3.0.3 · iOS/iPadOS 1.2.1

Follow the section for your platform. Screenshots show native UI with demo data; menus depend on version, plan and device. Test-build features may not yet be in the public release.

Content reviewed: 2026-10-18

Before you begin

Confirm QRIS is active in DOKU Production. Have access to the DOKU dashboard and OurBooth payment settings.

Set up booth payments — Workflow diagram. Optional steps depend on event configuration.

Web dashboard

1In DOKU, check QRIS activation. Creating a DOKU account alone is not enough.
2Open Settings → API Keys in DOKU. Copy the BRN- or MCH-prefixed Client ID into Client ID from API Keys in OurBooth, and place the Secret Key in its own field.
3Open Settings → Checkout Appearance → QRIS Credential Settings in DOKU. The numeric Client ID shown on the QRIS page goes into Merchant ID QRIS in OurBooth; it differs from the API Keys Client ID. Keep Terminal ID A01 unless DOKU supplies another value; enter the outlet postal code and save account & merchant details.
4Copy the complete public key provided by OurBooth. In DOKU, open Settings → API Keys → Edit Merchant Public Key, paste it and save.
5Copy the notification address displayed by OurBooth into DOKU Settings → QR Payment → Edit → Notify URL, then Submit. Save credentials, then run Test connection.
6The connection test creates a test QR and then cancels it. Do not pay that QR. After a successful test, enable QRIS in device policy and check the booth payment screen.

96-second DOKU walkthrough. Synthetic illustrations, no merchant data.

QRIS activation. Sample-data illustration; UI labels follow the provider dashboard.

API Keys Client ID. Sample-data illustration; UI labels follow the provider dashboard.

QRIS Merchant ID. Sample-data illustration; UI labels follow the provider dashboard.

Merchant Public Key. Sample-data illustration; UI labels follow the provider dashboard.

Notifications and connection test. Sample-data illustration; UI labels follow the provider dashboard.

Check the result

Operator check

The connection test passes and settings are saved. This validates the connection, merchant and QR, not customer-payment settlement.

If something goes wrong

Symptom	Next step
Client ID or Merchant ID is rejected	Check each value’s source: API Keys BRN-/MCH- and the numeric QRIS value are not interchangeable.
Notification is not yet proven	Check notification-address configuration. Missing notification history does not necessarily mean the connection test failed.

Web dashboard

1In DOKU, check QRIS activation. Creating a DOKU account alone is not enough.

2Open Settings → API Keys in DOKU. Copy the BRN- or MCH-prefixed Client ID into Client ID from API Keys in OurBooth, and place the Secret Key in its own field.

3Open Settings → Checkout Appearance → QRIS Credential Settings in DOKU. The numeric Client ID shown on the QRIS page goes into Merchant ID QRIS in OurBooth; it differs from the API Keys Client ID. Keep Terminal ID A01 unless DOKU supplies another value; enter the outlet postal code and save account & merchant details.

4Copy the complete public key provided by OurBooth. In DOKU, open Settings → API Keys → Edit Merchant Public Key, paste it and save.

5Copy the notification address displayed by OurBooth into DOKU Settings → QR Payment → Edit → Notify URL, then Submit. Save credentials, then run Test connection.

6The connection test creates a test QR and then cancels it. Do not pay that QR. After a successful test, enable QRIS in device policy and check the booth payment screen.

96-second DOKU walkthrough. Synthetic illustrations, no merchant data.

QRIS activation. Sample-data illustration; UI labels follow the provider dashboard.

API Keys Client ID. Sample-data illustration; UI labels follow the provider dashboard.

QRIS Merchant ID. Sample-data illustration; UI labels follow the provider dashboard.

Merchant Public Key. Sample-data illustration; UI labels follow the provider dashboard.

Notifications and connection test. Sample-data illustration; UI labels follow the provider dashboard.

If something goes wrong

Symptom	Next step
Client ID or Merchant ID is rejected	Check each value’s source: API Keys BRN-/MCH- and the numeric QRIS value are not interchangeable.
Notification is not yet proven	Check notification-address configuration. Missing notification history does not necessarily mean the connection test failed.