Capability Enablement Requirements
Several Convenient Checkout capabilities are off by default and must be enabled for a merchant account before use. This page lists what to collect for each gated capability during Merchant Onboarding, so requests can be made upfront instead of discovered one capability at a time.
Get Started
Not sure which capabilities apply to a merchant? See Know Your Use Case first. To request any capability below, contact your CCG onboarding representative with the information listed for that capability. Capability requests are submitted to a CCG onboarding representative β they are not self-service.
| Capability | What You Need to Provide | Where to Learn More |
|---|---|---|
| Payment Method Types & Channels | Tell CCG which payment method types (Card, Bank Account, HSA, etc.) and which channels (Web form, Text, Email, etc.) should be enabled for your account, and which vendor handles each (e.g., Stripe for cards, Optum Bank for bank accounts). This is foundational β several other capabilities below (Split Tender, Manufacturer Card) depend on the relevant payment method type already being enabled. | Payment Methods, Payment Method Channels |
| Split Tender | Request enablement for your merchant account. Requires the Card payment method type to be configured and active. | Split Tender Payments |
| HSA-Aware Wallet | Request HSA support enabled for your merchant account. Your customers will also need an HSA account with a supported vendor (e.g., Optum Bank). | HSA-Aware Wallet Capabilities |
| HSA Payment Method (bank account) | Request HSA support enabled for your merchant account. This is a separate, vendor-hosted payment method type β not the same as HSA-Aware Wallet above (that's a tag on a saved card; this is its own payment method). Customers need an HSA account with a supported vendor (e.g., Optum Bank) with an available balance at checkout. | HSA Payment Method |
| Manufacturer Card | Request the MANUFACTURER_CARD category configuration enabled for your merchant account. Note: adding a manufacturer card is only supported through the UI widget, not via direct API. | Manufacturer Card |
| Apple Pay / Google Pay | Provide your domain(s) β including subdomains β during onboarding for registration and validation. Configure a clear, descriptive statement descriptor for the payment sheet. | Express Checkout with Digital Wallet |
| Enterprise Wallet | Provide the customer-identifier field(s) your system sends (e.g., where in your request a patient ID or name lives), so CCG can configure enterprise identity matching against your merchant account. This is not automatic β only the underlying EIMP lookup is transparent; the merchant-specific identifier mapping must be configured first. | Enterprise Wallet |
| Agent-Assisted On-Screen Entry (WS2) | Confirm whether agents entering card details on-screen are members of the PCI_Workstation_2 group in UHC Secure. If so, request the ws2check merchant setting be enabled so WS2 group membership gates on-screen card entry (instead of the weaker agent.isAccessVerified check). | Payment Method Channels |
| Customer Login (HSID) | Tell CCG whether customers must sign in with HSID before wallet-sensitive actions continue, or whether checkout can proceed without mandatory sign-in. Your onboarding representative configures the mode you choose. | Customer Login |
| Webhooks | Expose a publicly-accessible HTTPS endpoint to receive events, and validate incoming requests using the JWT public key CCG provides during onboarding. If consuming via Stargate/HCP instead, register with HCP and share your client credentials with CCG. | Webhook Configuration |
| Reporting (ECG) | Determine your report destination location and request setup through the ECG dashboard. CCG provides the source user ID and merchant ID needed for that setup during merchant configuration. | ECG Setup |
| Transaction Metadata | Tell CCG which transaction-level metadata fields (e.g., order ID, order type) you want attached to payments, so they're available in reports and webhook payloads. | Merchant Onboarding Integration Guide |
What Happens If a Capability Isn't Requestedβ
| Outcome | Behavior |
|---|---|
| Capability enabled and prerequisites met | The capability becomes available for the merchant's integration to use |
| Capability requested but prerequisites incomplete (e.g., domain not yet validated for Apple Pay/Google Pay) | The capability may be enabled but will not function correctly until prerequisites are met |
| Capability not requested | The capability remains unavailable, with no error specific to "not enabled" surfaced until integration is attempted |
Related Documentationβ
- Merchant Onboarding
- Know Your Use Case
- Payment Methods
- Payment Method Channels
- Split Tender Payments
- HSA-Aware Wallet Capabilities
- HSA Payment Method
- Manufacturer Card
- Express Checkout with Digital Wallet
- Enterprise Wallet
- WS2 (PCI Workstation Verification)
- Customer Login
- Webhook Configuration
- ECG Setup
- Merchant Onboarding Integration Guide