Skip to main content

HyperPay

HyperPay is a payment gateway commonly used for card and regional payment methods in the Middle East / North Africa. CMP uses it when enabled for the customer’s currency and branch.

Provider: hyperpay.com

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

What HyperPay is used for in CMP

ModeBehaviour
PrepaidWallet top-up when HyperPay is active
PostpaidOnly if Has Autocharge is supported and enabled
ManualOffline payment — no HyperPay auto-charge

See Payment Gateways hub.

Configure HyperPay

  1. Obtain HyperPay sandbox entity / access credentials (then live)
  2. Provide credentials to StackConsole
  3. Enable HyperPay 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-hyperpay.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-hyperpay.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.