Skip to main content

PayPal

PayPal lets customers pay with PayPal accounts (and related methods where integrated). CMP uses PayPal when the gateway is active for the branch and currency.

Provider: paypal.com

Quick start
Configure in CMPSettings → Billing Setup → Payment Setting / Payment Provider
SandboxProvide PayPal REST Client ID / Secret — Prerequisites
Payment modesTypically prepaid top-up; confirm postpaid autocharge with StackConsole

What PayPal is used for in CMP

ModeBehaviour
PrepaidCustomer chooses PayPal for wallet top-up when enabled
PostpaidOnly if CMP integration supports recurring/variable charges for PayPal and Has Autocharge is set
ManualOffline payment — no PayPal auto-charge

See Payment Gateways hub.

Configure PayPal

  1. Create a PayPal sandbox app and obtain Client ID / Secret
  2. Provide credentials to StackConsole
  3. Enable PayPal 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-paypal.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-paypal.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.