Checking access…

Skip to main content
Version: v2

Customer Login

CCG supports HSID (HealthSafe ID) authentication for resolving customer identity before checkout actions continue. This lets merchants balance conversion and security based on their own customer journey.

Get Started

To request this capability, see Capability Enablement Requirements.

Key Benefits​

Real-world Example

A merchant who wants customers to authenticate with the HSID system before wallet operations can require sign-in so only validated users can perform CCG operations. A merchant optimizing for quick guest flows can allow checkout without mandatory sign-in, reducing friction while still allowing identity linking when available.

Without Customer LoginWith Customer Login
Every merchant handles identity verification independentlyVerified identity (HSID) is resolved consistently across merchants
No way to balance conversion against security per use caseTwo modes let a merchant choose the right tradeoff for their journey
Guest flows and secure flows require separate integrationsOne capability covers both, selected per merchant account

How It Works​

Two authentication modes are available. You choose which mode applies to your account as part of onboarding; your CCG onboarding representative configures it for you.

ModeBusiness IntentCustomer Experience
Sign-in requiredEnforce verified identity before protected actionsCustomer signs in with HSID before wallet-sensitive actions continue
Sign-in not requiredAllow eligible actions without mandatory identity sign-inCustomer can continue checkout without signing in

Business Rules​

Pre-Conditions​

  • The merchant has chosen a single authentication mode for the relevant customer journey (see Capability Enablement Requirements).
  • For sign-in required, enterprise identity configuration on the HSID system must be completed before this mode can be enabled.
  • Merchant-facing channels clearly communicate sign-in expectations before critical actions.

Post-Conditions​

OutcomeBehavior
Identity required and successfully resolvedCustomer proceeds with eligible wallet and payment actions
Identity required but not resolvedProtected actions are not completed and the customer sees recovery options
Identity not requiredCustomer continues the allowed wallet flow, identified by request input instead

Scenarios​

Merchant-Facing Scenarios
#ScenarioModeBusiness OutcomeMerchant Action
1Returning customer completes sign-in successfullySign-in requiredWallet experience continues normallyNone
2Customer cannot complete sign-in in the current sessionSign-in requiredWallet experience pauses until identity is resolvedProvide re-entry/sign-in guidance
3Checkout with no mandatory sign-inSign-in not requiredWallet experience continues normallyContinue standard checkout flow