Payment Methods Model

Payment Method Model

CCG supports multiple operating models for payment methods so merchants can align with different vendor integrations and data ownership strategies.

Managed Model

CCG manages each payment method throughout its full journey, from the time it is added through any changes and eventual removal.

This model works well for vendors such as Stripe, where payment methods are managed locally in CCG.

Vendor-Hosted Model

In the vendor-hosted model, payment methods remain primarily managed by the vendor rather than by CCG.

This approach helps merchants support payment experiences where certain payment methods are maintained by external partners and made available to customers as part of their checkout journey.

This model works well for vendors such as OPTUM_BANK, where payment methods are managed by the vendor.

Mixed Model

The mixed model gives merchants a flexible way to use both merchant-managed and vendor-hosted payment methods in the same customer journey.

This is helpful when a merchant wants to keep some payment methods under its own control while also offering payment methods that are provided by a partner.

With this model, customers may see different payment options depending on how they enter checkout and which options are available for that journey.

Payment Methods Return Matrix

Get Started

For guidance, see the

• Merchant Settings
• Enterprise Identity
• Authentication Strategy

This matrix describes how payment methods are returned based on Authentication strategy, customer identifiers, HSID resolution status, and selected payment method mode.

Authentication strategy	Customer Identifier(s) provided by merchant?	Customer Identifier(s)	HSID Resolved from EIMP?	Payment Method Model	Include Stripe PMs	Include Optum Bank PMs
IDP_NOT_REQUIRED	Yes	EID, merchant identifiers (for example: patientId, studentId, enrollmentId)	Yes	Managed	✅	❌
IDP_NOT_REQUIRED	Yes	EID, merchant identifiers (for example: patientId, studentId, enrollmentId)	No	Managed	✅	❌
IDP_NOT_REQUIRED	Yes	EID, merchant identifiers (for example: patientId, studentId, enrollmentId)	Yes	Vendor Hosted	❌	✅
IDP_NOT_REQUIRED	Yes	EID, merchant identifiers (for example: patientId, studentId, enrollmentId)	No	Vendor Hosted	❌	❌
IDP_NOT_REQUIRED	Yes	EID, merchant identifiers (for example: patientId, studentId, enrollmentId)	Yes	Mixed Model	✅	✅
IDP_NOT_REQUIRED	Yes	EID, merchant identifiers (for example: patientId, studentId, enrollmentId)	No	Mixed Model	✅	❌
IDP_NOT_REQUIRED	Yes	HSID	Yes	Mixed Model	✅	✅
IDP_NOT_REQUIRED	Yes	HSID	Yes	Managed	✅	❌
IDP_NOT_REQUIRED	Yes	HSID	Yes	Vendor Hosted	❌	✅
IDP_REQUIRED	Resolved from customer authentication	HSID	Not applicable	Managed	✅	❌
IDP_REQUIRED	Resolved from customer authentication	HSID	Not applicable	Vendor Hosted	❌	✅
IDP_REQUIRED	Resolved from customer authentication	HSID	Not applicable	Mixed Model	✅	✅

Related Documentation

• Merchant Settings