Gemini Code Assist is Google's AI coding assistant for IDEs and the Gemini CLI, billed through Google Cloud Billing. This guide explains how to attach a Coinepay virtual card to the Cloud Billing account behind a Gemini Code Assist subscription and what to do when a charge is declined. It also covers an important change to how the product is sold, so you know exactly what you can and cannot buy today.
Read this first: new Code Assist sales have ended
As of 9 October 2026, Google ended all new sales of the paid editions, Gemini Code Assist Standard and Gemini Code Assist Enterprise. New customers can no longer check out for these plans in the console. Existing subscriptions remain supported through their contractual term: per Google's sunset notice, existing subscriptions can add licenses through 31 January 2027, annual renewals are allowed through that date, and monthly renewals through 31 December 2027.
Separately, Gemini Code Assist for individuals (including access via Google AI Pro or Google AI Ultra) stopped serving IDE-extension and Gemini CLI requests on 18 June 2026, so that is not a current checkout tier either.
In practice, this means the realistic payment scenario today is: you already have a Standard or Enterprise subscription, and you want to make sure the payment method on the underlying Cloud Billing account is a working Coinepay card for ongoing monthly charges, added licenses, or a renewal. That is what the steps below address. If you are a brand-new customer, Google directs you to its sales team rather than a self-serve checkout.
What you need before you start
- A verified Coinepay account. Register at Coinepay and complete identity verification (KYC) before you try to use card services. You can manage everything from the dashboard or the Coinepay app for iOS and Android.
- Your Coinepay virtual card number, expiry date and CVV, which are available instantly in the app once the card is issued.
- Sufficient balance on the card for the upcoming charge, including any buffer the issuer holds during authorization.
- Administrator access to the Google Cloud project and billing account tied to your subscription.
- Your real billing details (name, address and country) exactly as they appear on your Coinepay account.
Understand the price basis
Google's USD price list, checked on 18 October 2026, describes existing subscriptions in license-hour terms rather than a fixed monthly invoice. At that time it listed Standard at $0.031232877 per license-hour on a monthly commitment (or $0.026027397 on a 12-month commitment), and Enterprise at $0.073972603 per license-hour on a monthly commitment (or $0.061643836 on a 12-month commitment). Both commitment lengths are billed monthly, and the hourly figures are published rates, not a set invoice amount. Non-USD customers are pointed to their currency's Cloud Platform SKU prices. Always confirm current figures on Google Cloud's official pricing page, as prices and plans change.
Add your Coinepay card to Google Cloud Billing
Payment methods live on the Cloud Billing account, which is linked to a Google payments profile. Subscription administration is separate (see below). To update the card:
- Sign in to the Google Cloud console with the account that administers your billing.
- Open Billing and select the billing account linked to your Gemini Code Assist subscription.
- Go to the Payment method page.
- Choose to add a payment method and enter your Coinepay card number, expiry and CVV.
- Enter the billing name and address that match your Coinepay account, then save.
- Set the Coinepay card as the primary method if you want it to carry the recurring charges.
When a billing account is first created, you select the country and profile, supply payment details, then choose Submit and enable billing. Note that the Cloud Billing country determines your currency and available payment methods and cannot be changed on an existing billing account.
Manage the subscription itself
Billing cards and subscription settings are in different places. To change edition, license count, commitment period or renewal, an authorized administrator uses Google Cloud console → Admin for Gemini → Manage Gemini Code Assist → Manage subscription. Use this area to add licenses (allowed through 31 January 2027 for existing subscriptions) or to manage renewal.
Card types Cloud Billing accepts, and what it refuses
Self-serve Cloud Billing accepts American Express, Mastercard, Visa, and Visa- or Mastercard-branded debit cards. Some card types are region-limited: Discover is US-only, JCB is Japan/US-only, Visa Electron works outside the US, and Elo credit is Brazil-only. Depending on your country, a bank account may be usable as the primary method, and Google lists limited PayPal support in Spain, Italy and Mexico, plus country-specific Pix, boleto and UPI arrangements.
Two restrictions matter most for virtual cards:
- Prepaid cards are not accepted for recurring Cloud Billing payments.
- Debit cards that require in-session two-factor authentication are not accepted for recurring payments.
Because Gemini Code Assist billing is recurring, your card must be able to support automatic, unattended charges. Coinepay does not publish, in this guide, which of these categories a given card falls into. Contact Coinepay support to confirm your card can be used for recurring Google Cloud charges before you rely on it. Reach the team through support or Telegram.
Troubleshooting a declined card
When a charge fails, the Cloud Billing Transactions page may show an issuer-provided reason. Google is clear that the issuing bank, not Google, declines the payment, so the fix usually involves the card or its issuer. Common causes:
"Your card does not support automatic recurring payments"
This documented error appears when the card or its issuer refuses recurring charges, or when the card requires in-session authentication Google cannot complete on a recurring run. Confirm with Coinepay support that your card supports recurring Google Cloud payments, and replace the method if it does not.
"General decline of the card. No other information was provided by the issuing bank."
This generic decline comes straight from the issuer. Check your Coinepay balance, make sure the card is active, and review the Transactions page for any issuer note. If the decline persists, contact Coinepay support with the date and amount of the attempt.
Insufficient balance
Top up the Coinepay card so it covers the charge plus any temporary authorization hold, then retry the payment from the Transactions or Payment method page.
Billing address mismatch
The name and address on the Cloud Billing payment method must match your Coinepay card details. Correct any mismatch and save before retrying.
3-D Secure / authentication prompts
A recurring charge cannot pause for an interactive 3-D Secure step, which is why cards needing in-session two-factor authentication are not accepted. If your card triggers this, it is not suitable for the recurring charge; ask Coinepay support for guidance.
Regional and India-specific checks
Google restricts access to some services in places including China, Crimea, Cuba, Iran, North Korea and Syria. In India, banks may decline automatic recurring Google Cloud charges over ₹15,000 under RBI-related requirements; Google suggests making a manual payment if the automatic charge fails.
Cancellation and refunds
An existing Code Assist subscription cannot be cancelled during its commitment term. Instead, turn off auto-renewal in the subscription settings so it expires at the end of the term. Google's committed-unit terms require payment for the selected term whether or not units are used, with refunds of unused prepaid fees only in specified cases (for example where Google non-renews, terminates other than for your breach, or discontinues the service). A refund of unused funds from an early payment to a Postpay account is a separate procedure and is not the same as a refund of an unused commitment.
Keep records of your Coinepay charges from the app, and if a payment problem is on the card side rather than Google's, Coinepay support can help you investigate.
Get your Coinepay virtual card: Sign up · App Store · Google Play · Customer support
FAQ
Can I buy a new Gemini Code Assist subscription with a Coinepay card?
No. Google ended new sales of Standard and Enterprise on 9 October 2026, and there is no self-serve checkout for new customers. You can pay for an existing subscription, add licenses through 31 January 2027, or renew within Google's published windows. New customers are directed to Google's sales team.
Will my Coinepay virtual card work for recurring Google Cloud charges?
Cloud Billing does not accept prepaid cards or debit cards requiring in-session two-factor authentication for recurring payments. Before you rely on your card, contact Coinepay support to confirm it can be used for recurring Google Cloud charges.
Where do I update the card on file for my subscription?
Open the Google Cloud console, go to Billing, select the billing account linked to your subscription, and use the Payment method page to add or change your Coinepay card. Subscription settings are separate, under Admin for Gemini.
Why does Google show 'General decline of the card'?
That message comes from the issuing bank, not Google. Check your Coinepay balance, confirm the card is active, make sure the billing address matches, and review the Transactions page. If it continues, contact Coinepay support with the attempt date and amount.
How do I stop future charges?
An existing subscription cannot be cancelled mid-term. Turn off auto-renewal under Admin for Gemini so the subscription expires at the end of its commitment. Committed-term fees are generally payable whether or not you use the licenses.
Related guides
- How to Pay for Hetzner Cloud with a Coinepay Virtual Card
- How to Pay for Lovable with a Coinepay Virtual Card
- How to Pay for SonarQube Cloud with a Coinepay Virtual Card
- How to Pay for v0 with a Virtual Card (Step-by-Step Guide)
- How to Pay for Snyk with a Virtual Card (Step-by-Step Guide)
- How to Pay for Bolt.new with a Virtual Card (Step-by-Step Guide)

