Authentication Strategy
Authentication Strategy determines whether a customer must sign in with enterprise identity (HSID System) before checkout actions can continue. This capability helps merchants balance conversion and security by supporting two operating modes: IDP_REQUIRED and IDP_NOT_REQUIRED.
Get Started
For Configuration guidance, see the Merchant Settings Authentication Strategy
Key Benefits
Real-world Example
A merchant who wants customers to authenticate with the HSID system before wallet operations can enforce IDP_REQUIRED so only validated users can perform CCG operations. A merchant optimizing quick guest flows can use IDP_NOT_REQUIRED to reduce friction while still allowing identity linking when available.
How It Works
| Strategy | Business intent | Customer experience | Typical merchant objective |
|---|---|---|---|
IDP_REQUIRED | Enforce verified identity before protected actions | Customer signs in before wallet-sensitive actions continue | Customer Identity based on login to HSID System |
IDP_NOT_REQUIRED | Allow eligible actions without mandatory identity sign-in | Customer can continue checkout | Customer identity based on the request input |
Standard Flow
Business Rules
Pre-Conditions
- Merchant configures a single authentication strategy for the relevant customer journey. Refer Merchant Settings.
- For IDP_REQUIRED, enterprise identity configuration on HSID system must be completed before this strategy 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 customer sees recovery options |
| Identity not required | Customer continues allowed wallet flow, with customer identity based on input request |
Scenarios
Authentication Scenarios
Merchant-Facing Scenarios
| # | Scenario | Strategy | Business Outcome | Merchant Action |
|---|---|---|---|---|
| 1 | Returning customer completes sign-in successfully | IDP_REQUIRED | Wallet experience continue normally | None |
| 2 | Customer cannot complete sign-in in current session | IDP_REQUIRED | Wallet experience pause until identity is resolved | Provide re-entry/sign-in guidance |
| 3 | checkout with no mandatory sign-in | IDP_NOT_REQUIRED | Wallet experience continue normally | Continue standard checkout flow |