Skip to main content

Dinger

Dinger is a regional payment gateway (Myanmar / Southeast Asia focus) that CMP can enable for local payment methods supported by your merchant account.

Provider: dinger.asia

Quick start
Configure in CMPSettings → Billing Setup → Payment Setting / Payment Provider
SandboxProvide Dinger sandbox API credentials — Prerequisites
Payment modesTypically prepaid top-up; confirm postpaid with StackConsole

What Dinger is used for in CMP​

ModeBehaviour
PrepaidWallet top-up when Dinger is active
PostpaidConfirm Has Autocharge support with StackConsole
ManualOffline payment — no Dinger auto-charge

See Payment Gateways hub.

Configure Dinger​

  1. Obtain Dinger sandbox merchant / API credentials
  2. Provide credentials to StackConsole
  3. Enable Dinger under Payment Setting
  4. Configure Payment Provider — see Payment Gateway Providers

Edit Payment Gateway Settings fields​

Each gateway has its own CMP form fields. Field details for this provider will be documented here when confirmed from the CMP UI / StackConsole.

Until then:

  1. Configure the gateway under Settings → Billing Setup → Payment Setting
  2. Assign Branches — see branch visibility
  3. Assign the gateway to each currency — see currency assignment

img/screenshots/cmp-payment-gateway-dinger.png

Screenshot: CMP — Edit Payment Gateway Settings for this provider

Payment Gateway Providers​

Path: Settings → Billing Setup → Payment Provider

Form title: Edit Payment Gateway Providers

Path: Settings → Billing Setup → Payment Provider (breadcrumb: Payment Gateway Providers)

Configure this provider’s currencies, Has Autocharge, logos, and status. Field details will be expanded when confirmed from the CMP UI.

img/screenshots/cmp-payment-provider-dinger.png

Screenshot: CMP — Payment Provider settings for this gateway

Has Autocharge

Yes / No (when applicable). Enables postpaid auto-charge for this provider in CMP.

Has Autocharge in CMP is not enough

Enabling Has Autocharge only turns the feature on at the application layer. The payment gateway must also support autocharge natively — typically automatic charging of saved credit cards for recurring payments with variable amounts.

Confirm native support with the gateway vendor and StackConsole before using this gateway as a postpaid default. See Payment Gateways — postpaid requirement.