Legacy 3PIC (Third-Party Integrated Commerce) contracts on Google Cloud Marketplace behave differently from current iSaaS models. Changing billing in GCP under a 3PIC contract can disrupt Redis Cloud access, and a short grace window may apply before databases become inaccessible.
This guide explains how to safely coordinate billing changes for 3PIC subscriptions with Redis Support and Google to maintain continuity of service.
Prerequisites
Confirm contract type
Verify with your Redis Account Team or Support that your subscription is under a 3PIC (legacy) contract.
Check your Marketplace order details for legacy identifiers (e.g., “Redis Labs Inc.” as seller, not “Redis Ltd.”).
Google Cloud access
Role on the relevant Billing Accounts and projects sufficient to view and manage Marketplace orders:
roles/billing.admin or roles/billing.user.
Billing roles referenced here
Redis Cloud access
Account Owner permissions on the Redis Cloud account to be remapped.
Ability to change Payment method if a temporary fallback (Credit Card) is required.
Coordination and approvals
An active Redis Support ticket to plan and execute the billing change.
Internal approval to alter the payer or Billing Account in Google Cloud Marketplace.
Risk controls
Back up mission-critical databases before the change.
Schedule a maintenance window to avoid disruption.
Confirm a grace-period recovery plan with Support if an unmapping occurs.
Details to have ready
Current order link or ID from GCP Marketplace.
Target Billing Account ID and Project ID.
Redis Cloud account name that must remain mapped.
Quick Fix Table
| Problem | Likely Cause | Fast Fix |
|---|---|---|
| Access to Redis Cloud lost after billing change | Unmapping triggered under 3PIC rules | If within grace window, contact Redis Support immediately to re-establish mapping. Review unmapping behavior in Disconnect Redis Cloud from Google Cloud Marketplace. |
| Redis UI only shows Credit Card | Mapping not re-established | From GCP order, click Manage on provider, or coordinate with Support to reconnect the correct Redis Cloud account. |
| Unsure how to proceed | 3PIC workflow differs from iSaaS | Pause changes and open a Support ticket with Billing Account IDs, order link, and Redis Cloud account details. |
Step-by-step (Support-assisted process)
Engage Redis Support early
• Open a Support ticket describing the target Billing Account ID, Project ID, and desired timing.
• Include a link to the Marketplace order and confirm the subscription is 3PIC.Plan the maintenance window
• Work with Support to schedule a safe time for the billing transition.
• Back up all critical databases before the change.Coordinate with Support during the change
• Support and Google will manage or confirm any required unmapping/remapping steps.
• Do not unsubscribe manually.Re-establish mapping if required
• If the subscription becomes unmapped, Support will guide you through re-linking your Redis Cloud account.
• You may temporarily use a Credit Card payment method to maintain service continuity.Validate completion
• Verify the Redis Cloud account shows Payment method = GCP Marketplace again.
• In GCP Marketplace, confirm the order is Active under the new Billing Account.
Verify
In Google Cloud
The Redis Cloud order appears under the target Billing Account with Status: Active.
The Manage on provider link opens your Redis Cloud account correctly.
In Redis Cloud
Subscriptions show Payment method = GCP Marketplace.
All databases are accessible and no longer in a grace or suspended state.
Notes and Reminders
Do not unsubscribe a 3PIC contract from Marketplace; it can immediately terminate linked resources.
Keep Redis Support engaged throughout the process—3PIC flows cannot be completed self-serve.
Maintain a Credit Card fallback until the mapping is verified on the new Billing account.
Document Billing Account IDs, order links, and Redis Cloud account names for auditing and faster Support handling.
0 comments
Please sign in to leave a comment.