Coinepay | How to Pay for AWS Bedrock with a Coinepay Virtual Card

Amazon Bedrock does not have a single subscription checkout: model usage is billed through an AWS account, and some models require an AWS Marketplace subscription on first use. Before trying to pay with a Coinepay virtual card, check an important restriction: AWS says it does not accept virtual credit cards as payment methods for AWS services. Contact Coinepay support to confirm your card meets AWS’s payment requirements before you buy. Do not assume that entering the card will make it eligible.

What you need before you start

An AWS account: AWS offers a Free plan and a Paid plan. These are account plans, not Bedrock model tiers. Charges depend on the models and other resources you use, rather than a flat Bedrock subscription price.
An eligible payment method: AWS-accepted methods vary by seller of record and location. Check the payment options shown for your AWS account. AWS specifically lists virtual credit cards among methods it does not accept for AWS services.
Your real account and billing details: Use your actual identity, contact information and billing address. The details you enter for a card should match its billing records.
A Coinepay account, if you intend to check card eligibility: Register with Coinepay and complete identity verification before using card services. Coinepay issues virtual cards with a card number, expiry date and CVV; availability of Coinepay services varies by jurisdiction.
A Bedrock model and AWS Region: Model availability differs by Region. Check AWS’s model-and-Region documentation and the official Bedrock pricing page before you generate usage.

At the time of writing (October 2026), AWS described the Free plan as lasting until its credits run out or six months pass, whichever comes first. Eligible new customers received USD $100 in sign-up credits and could earn up to USD $100 more. Bedrock was listed in the new sign-up experience’s Free Tier, but Global and Geographic cross-Region inference were not supported there. Credits are not unlimited model access; check the current AWS Free Tier terms and Bedrock pricing page.

How AWS Bedrock charges reach your payment method

For ordinary On-Demand inference, you select an available model and use it through Bedrock; AWS records the resulting usage on your account. There is no separate monthly Bedrock subscription to purchase for this form of usage. AWS also lists Batch and Provisioned Throughput pricing arrangements. Its service tiers—Standard, Flex, Priority and Reserved—are separate from the Free and Paid AWS account plans.

Prices vary by model provider, model, modality, Region and usage. Check the official AWS Bedrock pricing page for the model and Region you intend to use. A paid account is generally billed monthly, and AWS ordinarily attempts to charge its default payment method automatically at the beginning of the month. Some third-party models initiate an AWS Marketplace subscription when you first invoke them; that step can require Marketplace permissions and a valid payment method. Anthropic models generally also require first-time use-case details.

Step by step: sign up and check your payment options

Create or open your AWS account. AWS offers “Sign up for AWS (new)” and “Sign up for AWS (advanced).” The new experience was in limited rollout when this guide was written, so you may see the advanced flow instead.
Complete the sign-up prompts. In the new flow, choose an email address or a supported Google, Apple, GitHub or Amazon login, verify your email, and enter your genuine contact details. AWS provides an initial project. A payment method is not required for most new customers at sign-up, although AWS may request one for identity verification. Follow the prompts shown if you receive the advanced flow.
Review payment-method eligibility before entering card details. AWS’s published guidance says virtual credit cards are not accepted for AWS services. If you want to consider a Coinepay virtual card, first ask Coinepay support to confirm that your card meets AWS’s requirements. You can also ask AWS billing support which methods are eligible for your account. If the card does not qualify, choose an accepted payment method instead; do not repeatedly submit it.
Add an eligible method in the appropriate settings. In the new sign-up experience, manage payment methods and billing in AWS Settings. In the advanced experience, open Billing and Cost Management → Payment preferences to add or manage a card and select the default method. Enter your real billing information and complete any verification AWS requests.
Choose a model and Region in Bedrock. Confirm that the model is available in your selected AWS Region and review its current pricing. If a third-party model starts an AWS Marketplace subscription on first invocation, ensure your AWS account has the necessary Marketplace permissions and an eligible payment method. Provide first-time use-case details if AWS requests them for an Anthropic model.
Monitor charges and pay an invoice if needed. Review AWS billing after you start using Bedrock. In the advanced billing experience, an unpaid invoice can be selected under Payments → Complete payment. Follow the AWS payment screen rather than treating a Bedrock model invocation as a separate card checkout.

Provisioned Throughput has an additional purchase decision. In the Bedrock console, go to Provisioned Throughput → Purchase Provisioned Throughput. Review and acknowledge the displayed commitment duration and price before selecting Confirm purchase. Do not confirm a commitment merely to test whether a payment method works.

Troubleshooting a declined card or blocked model access

A decline does not, by itself, identify the cause. Start with AWS’s eligibility rules: if the proposed method falls under its restriction on virtual credit cards, use a method AWS accepts. Contact Coinepay support to confirm whether your card meets the merchant’s requirements before trying it. If you already have an eligible method on file, check the following possibilities:

Insufficient available funds or a transaction limit: Check the available balance and applicable limits in your payment provider’s dashboard or app. Compare them with the amount AWS is trying to collect, then resolve any shortfall before retrying. For Coinepay-specific balances or limits, check the Coinepay app or ask support.
Billing address or card-detail mismatch: Recheck the card number, expiry date, CVV and billing information against your real records. Correct mistakes in AWS payment settings; do not substitute an address from another country. An expired card can also cause a decline.
Issuer-required authentication, including 3-D Secure where applicable: If AWS presents an authentication step, complete it through the method your payment provider supplies. If no prompt appears or authentication fails, ask the provider whether the attempted charge can be authenticated. Do not assume a particular card supports a particular authentication flow.
Merchant or region checks: The accepted methods depend on your AWS seller of record, and Bedrock model availability depends on the selected AWS Region. Check both separately. For example, AWS Europe lists different payment options from AWS India; switching a model’s Region does not establish that a card is eligible for your account.
Model subscription prerequisites: If Bedrock reports “Model access is denied due to INVALID_PAYMENT_INSTRUMENT: A valid payment instrument must be provided,” check the account’s eligible payment method and any Marketplace subscription requirements. Also confirm the required Marketplace permissions. The message alone does not prove which prerequisite failed.

Another reported card-entry message is “The card number isn't valid. Enter a valid card number.” Check for typing errors, but do not treat that message as proof of a specific cause. If accurate details still fail, ask AWS billing support about the account’s payment options and contact your payment provider about the attempted transaction.

How to stop future charges

To stop new On-Demand inference usage, stop sending requests and check for other AWS resources or arrangements that may still incur charges. Usage already incurred remains payable. Provisioned Throughput requires particular care: a Model Units purchase with a commitment cannot be deleted before its term ends, while no-commitment throughput continues billing until it is deleted. For Provisioned Throughput by Tokens, turning off auto-renew prevents renewal but does not remove the current term’s full provision fee, even if you run no inference. Review the purchase terms in AWS before confirming any commitment.

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

FAQ

Can I use a Coinepay virtual card to pay for AWS Bedrock?

Do not assume it is eligible. AWS says it does not accept virtual credit cards for AWS services. Contact Coinepay support to confirm your card meets AWS’s requirements before you buy, and use an AWS-accepted method if it does not.

Does AWS Bedrock have a monthly subscription fee?

Ordinary On-Demand model usage is billed through your AWS account rather than a single monthly Bedrock subscription. Pricing varies by model, Region and usage; Provisioned Throughput has separate purchase terms.

Where do I update my AWS payment method?

Use AWS Settings in the new sign-up experience. In the advanced experience, go to Billing and Cost Management → Payment preferences.

Why does Bedrock show INVALID_PAYMENT_INSTRUMENT?

A reported version of this error occurs when a model’s AWS Marketplace subscription cannot complete. Check for an eligible payment method and the required Marketplace permissions, then contact AWS support if the cause remains unclear.

How to Pay for AWS Bedrock with a Coinepay Virtual Card