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.
To request this capability, see Capability Enablement Requirements.
Key Benefitsβ
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 Login | With Customer Login |
|---|---|
| Every merchant handles identity verification independently | Verified identity (HSID) is resolved consistently across merchants |
| No way to balance conversion against security per use case | Two modes let a merchant choose the right tradeoff for their journey |
| Guest flows and secure flows require separate integrations | One 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.
| Mode | Business Intent | Customer Experience |
|---|---|---|
| Sign-in required | Enforce verified identity before protected actions | Customer signs in with HSID before wallet-sensitive actions continue |
| Sign-in not required | Allow eligible actions without mandatory identity sign-in | Customer 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β
| Outcome | Behavior |
|---|---|
| Identity required and successfully resolved | Customer proceeds with eligible wallet and payment actions |
| Identity required but not resolved | Protected actions are not completed and the customer sees recovery options |
| Identity not required | Customer continues the allowed wallet flow, identified by request input instead |
Scenariosβ
Merchant-Facing Scenarios
| # | Scenario | Mode | Business Outcome | Merchant Action |
|---|---|---|---|---|
| 1 | Returning customer completes sign-in successfully | Sign-in required | Wallet experience continues normally | None |
| 2 | Customer cannot complete sign-in in the current session | Sign-in required | Wallet experience pauses until identity is resolved | Provide re-entry/sign-in guidance |
| 3 | Checkout with no mandatory sign-in | Sign-in not required | Wallet experience continues normally | Continue standard checkout flow |