Coinepay | How to Pay for Google Cloud Speech-to-Text with a Virtual Card

Google Cloud Speech-to-Text is a usage-priced API, not a monthly subscription with a separate checkout. To pay for it, you set up a Google Cloud project, link a Cloud Billing account and add a payment method to that billing account. This guide explains where a Coinepay virtual card fits into that process—and which Google payment restrictions to check before you begin.

Before you start: check card and account eligibility

You need a Google account, a Google Cloud project and permission to manage its billing. You also need a Coinepay account: register with Coinepay and complete identity verification before using card services. Coinepay issues virtual cards with a card number, expiry date and CVV, which you can access through its app or self-service dashboard.

Check Google’s payment rules before relying on a card. Google lists accepted card brands by billing country, but it does not accept prepaid cards or debit cards that require in-session two-factor authentication for recurring automatic charges. Do not assume a Coinepay card meets those requirements. Contact Coinepay support to confirm your card meets Google’s requirements before you buy. Google also limits Cloud Billing sign-up and service access in certain locations. Use your real identity, billing country and billing details; a payment method cannot bypass regional eligibility rules.

Have enough available funds for any applicable initial charge and subsequent usage charges. Check the Coinepay app for your card’s available funds and any applicable card settings. If you are setting up billing for a business, use the business and payment-profile information that accurately belongs to that business.

Understand what Google charges for Speech-to-Text

Google publishes separate Speech-to-Text V2 API and Speech-to-Text V1 API price schedules. There is no Speech-to-Text subscription plan to select. At the time of writing (October 2026), published V2 Standard recognition pricing starts at USD $0.016 per minute for the first 500,000 minutes per account per month, while V2 Standard dynamic batch recognition is listed at USD $0.003 per minute. Higher usage tiers and other models have different prices. Check Google Cloud’s official Speech-to-Text pricing page before enabling a workload, particularly if your billing account uses a currency other than USD.

Do not apply a V1 allowance to V2 usage: the published V1 Speech Recognition schedule lists the first 60 minutes per account per month as free, but the published V2 schedule does not show that allowance. Google bills successfully processed audio in one-second increments, including requests that return an empty transcription. Separate audio channels and associated Cloud Storage usage can add charges.

Eligible new Google Cloud users may see a $300 Welcome credit for 90 days through the Google Cloud Free Trial. Check eligibility and what the credit covers during sign-up; it is not a Speech-to-Text plan or a substitute for reviewing billing details.

Step by step: set up billing and add your card

Create or choose a project. Sign in to the Google Cloud console with the Google account that will own or manage the workload. Create a project for Speech-to-Text, or select an existing project you are authorized to use.
Create or choose a Cloud Billing account. In the console, open Manage billing accounts. If you need a new self-serve account, choose Create account, select the correct country and Google payments profile, then follow the prompts through Submit and enable billing. Review these choices carefully: Google says the billing country and assigned currency cannot later be changed on that account.
Enter the payment details. In the relevant billing account, open Payment method and follow Google’s prompts to add a card. Retrieve the card number, expiry date and CVV from your Coinepay app or dashboard. Enter your genuine billing name and address as required by the Google payments profile. Complete any verification Google requests, without assuming that a successful verification means the card is eligible for ongoing charges.
Link billing to the project. Confirm that the project you selected uses the intended active Cloud Billing account. This matters if your organization has multiple projects or payment profiles: Speech-to-Text usage is charged through the project’s linked billing account, not through a separate API checkout.
Enable the API. In the project, enable the Speech-to-Text API and set up your application according to Google Cloud’s Speech-to-Text setup instructions. Before sending production audio, check whether your chosen V1 or V2 model, language and feature are available in your processing location. For example, Chirp 3 is a V2-only model; V2 combinations vary by location.
Review usage and payments. Return to the Google Cloud console’s Billing pages to monitor charges and manage the payment method. Self-serve billing accounts normally charge their primary payment method automatically for accrued usage; monthly invoicing is a separately arranged account type.

If a Cloud Billing account already exists, you generally do not need to create another one solely for Speech-to-Text. Select the right account, check that the project is linked to it and review its payment method before enabling the API.

Troubleshoot a declined card or charge

Start with the exact message in Google Cloud Billing. If a charge—not just the addition of a card—was declined, the billing account’s Transactions page may show a bank-provided reason. Then work through the checks below rather than repeatedly submitting unchanged details.

Insufficient available funds: Check your available funds in Coinepay and compare them with the amount Google is attempting to charge. Remember that automatic charges can relate to usage already accrued, not just your next transcription request. If funds appear sufficient but the charge still fails, ask Coinepay support to review the attempted transaction.
Billing details do not match: Check the name, billing address and payments profile entered with Google. Correct genuine errors in Google’s Payment method settings or linked Google payments profile. Do not enter a different country or an invented address to make a payment go through.
Recurring-payment or authentication restriction: Google documents the card-addition error “Your card does not support automatic recurring payments.” It also documents “General decline of the card. No other information was provided by the issuing bank.” Google does not accept prepaid cards or debit cards requiring an SMS code or other in-session two-factor check for recurring automatic charges. If either message appears, contact Coinepay support to confirm whether your card meets Google’s requirements before trying again. A verification prompt is not a reason to bypass an authentication requirement.
Merchant or region checks: Google’s accepted payment methods differ by country, and Cloud Billing sign-up is unavailable in some locations. Confirm that your real billing country, Google payments profile and card details are consistent, then check Google’s payment-method rules for that country. If Google’s rules rule out the card, use another payment method that Google explicitly allows for your account, if one is available.

Google lists American Express, Mastercard and Visa among its supported card brands, with additional country-specific options, but that list alone does not establish that any particular virtual card will be accepted. For an unresolved issuer-side decline, give Coinepay support the attempted amount, date and Google’s message; avoid sending your full card number or CVV in a support message.

Manage charges or stop using the API

Use the Google Cloud console’s Billing pages to review usage, transactions and the payment method. If you no longer want a project to incur Speech-to-Text charges, stop its workload and disable billing on that project. For a self-serve account, Billing → Account management → Close billing account is a broader action: it stops services in every linked project, and Google issues a final bill for usage accrued before closure.

Closing billing is not an automatic refund of usage charges. If you have an eligible unused Postpay payment balance, Google provides Billing → Payment overview → Request a refund; unused promotional credits are not refundable. Check the account’s status and any final transactions before removing a payment method or closing an account used by other teams.

Get your Coinepay virtual card: Sign up · App Store · Google Play · Customer support

FAQ

Do I buy a monthly Google Cloud Speech-to-Text plan?

No. Speech-to-Text is a usage-priced API. Link an active Cloud Billing account to your project, enable the API and check the applicable V1 or V2 pricing schedule.

Where do I add my Coinepay virtual card?

In the Google Cloud console, select your self-serve Cloud Billing account and open Payment method. Google’s payment restrictions still apply; confirm card eligibility with Coinepay support before relying on it.

What does “Your card does not support automatic recurring payments” mean?

Google may be rejecting the card for its automatic billing requirements. Google does not accept prepaid cards or debit cards requiring in-session two-factor authentication for recurring charges. Ask Coinepay support to confirm whether your card meets Google’s requirements.

Will closing my billing account stop Speech-to-Text charges?

It stops services across all projects linked to that billing account, but Google can still issue a final bill for usage accrued before closure. To stop one project, stop its workload and disable billing on that project.

How to Pay for Google Cloud Speech-to-Text with a Virtual Card