Coinepay | How to Pay for MongoDB Atlas with a Coinepay Virtual Card

You can add a Coinepay virtual card to MongoDB Atlas when setting up a paid deployment or through your organization’s billing settings. This guide covers what to prepare, how Atlas charges for usage, where to enter your card, and what to check if a payment fails.

Before you start

Set up Coinepay: Register and complete identity verification before using card services. You can manage your card in the Coinepay dashboard or mobile app and view its card number, expiry date, and CVV.
Prepare your real billing details: Use your own identity and the correct billing address for your payment information. Keep access to your Coinepay app in case you need to review a card transaction or complete an authentication request.
Choose an Atlas organization: Atlas billing is managed at the organization level. Projects within the same organization share its billing settings, so confirm you are adding the card to the organization that will own your deployment.
Check available funds: Allow for Atlas’s US$1 card-verification charge, which MongoDB says it refunds, as well as charges from the resources you use. Check your available balance and applicable card details in Coinepay before proceeding.

MongoDB Atlas offers Atlas Core and Atlas Infinite. Atlas Core deployment choices include Free, Flex, and Dedicated. Free is the M0 tier and does not require a paid cluster; the steps below are for adding a card to pay for eligible usage. Atlas Infinite was in public preview at the time of writing and is available only in supported AWS regions. Free and Flex also have deployment-region limitations. A supported cloud deployment region is not necessarily an indication that every customer billing location is eligible.

Understand Atlas pricing before adding a card

For self-serve, pay-as-you-go deployments, Atlas charges for usage rather than selling a fixed-price cluster at checkout. MongoDB describes cluster billing as hourly, with monthly invoices. Your eventual bill can depend on deployment settings and additional usage, so review the configuration and pricing estimate shown by Atlas before creating a paid deployment.

At the time of writing (October 2026), MongoDB listed Atlas Core Free at US$0, Flex starting at US$0.011 per hour, and Dedicated starting at US$0.08 per hour for M10. It listed Atlas Infinite public preview starting at US$0.09 per hour, with separate compute, storage, backup, and transfer cost components. These are published starting figures, not a quote for your configuration. Check MongoDB’s official pricing page and the Atlas console for current prices and usage details.

Atlas also uses the word subscription for arrangements such as Elastic, Flex Commitment, Monthly Commitment, Marketplace, and Prepaid. These are different from selecting a Free, Flex, or Dedicated deployment. A Sales-purchased subscription can be applied under Billing → Overview → Apply Code; a marketplace subscription is invoiced through its marketplace. Follow the terms of that arrangement rather than assuming that entering a card creates or replaces it.

How to sign up and pay for MongoDB Atlas

Create or open your Atlas account. Sign up for MongoDB Atlas using email, GitHub, or Google, or sign in to an existing account. Atlas creates an organization and project during initial setup; you can deploy a cluster within a project.
Select the correct organization and project. Check the organization before creating a paid deployment, especially if you manage several teams or clients. Its billing settings apply across its projects.
Choose a deployment. In the Atlas console, select an available deployment type and configure its cloud provider, region, and other options. If you only need to explore Atlas, consider whether Free meets your needs. If you choose Flex or Dedicated, review the estimated costs and any additional billable features before continuing. Atlas no longer offers M2, M5, or Serverless as new deployment choices.
Select a payment method during paid deployment setup. For a first paid deployment, Atlas lets you choose a payment method while deploying. Select the card option if it is available for your account. The Atlas console also lists other methods, including Google Pay, US bank account, SEPA Direct Debit, Revolut Pay, Link, and PayPal; availability depends on the method and location.
Enter your Coinepay card details. Copy the card number, expiry date, and CVV from your Coinepay dashboard or app into Atlas’s card form, which asks for the number, expiry, and CVC. Enter your real billing details accurately. Review the deployment configuration before confirming it.
Watch for verification and later invoices. Atlas says it makes and refunds a US$1 charge when a card is first connected. An issuer decline of that charge may stop card confirmation. After deployment, monitor Atlas billing and your card activity; pay-as-you-go charges are not limited to the amount displayed at initial setup.

If you already have an Atlas organization and need to add or change its card, navigate to organization → Billing → Overview → Payment Method → Edit. Make sure you are editing the organization responsible for the relevant project, then save the updated payment details. Check the Atlas billing area for invoices and payment status.

If Atlas declines the card or a payment fails

A declined verification charge and a failed monthly invoice can have different causes. Start with the status shown in Atlas, then check your Coinepay card activity. Do not repeatedly create cards or accounts to work around a payment or location check.

Insufficient available balance: Confirm the card has enough available funds for the US$1 verification charge or the invoice amount. MongoDB identifies insufficient funds as a possible reason for failed payments. Remember that paid deployments can continue to accrue usage charges after setup.
Incorrect card or billing details: Recheck the number, expiry, and CVV, and correct any typing errors. If Atlas requests a billing address, enter your genuine address consistently. An address mismatch is worth checking, but do not assume it is the confirmed cause of a particular decline without information from Atlas or the card issuer.
Authentication or 3-D Secure: If a card-authentication step appears, follow the legitimate prompt and complete it promptly. Strong customer authentication requirements can affect EEA payments. If a prompt does not arrive or authentication fails, check the transaction in Coinepay and contact Coinepay support for help with the card-side issue; Atlas support can help investigate its checkout or invoice status.
Currency or issuer authorization: MongoDB lists inability to pay in USD and issuer authorization as possible payment-failure issues. Check the currency and payment details presented for your account, then ask Coinepay support to investigate a declined authorization. Do not assume that a published US-dollar list price determines the final amount charged to every card.
Merchant location or card eligibility checks: If Atlas indicates that a payment method is unavailable or rejects a card after checking its details, do not change your location or billing information to get around the check. Payment-method availability varies: for example, MongoDB limits US bank account payments to the US and SEPA Direct Debit to the EEA. Contact MongoDB about the requirement shown for your account and Coinepay support to confirm whether your card meets it before you try again.

For an India-issued credit card, MongoDB documents a recurring-payment mandate requirement: a payment above ₹15,000 that is not authorized, or a revoked mandate, can result in a FAILED payment. This rule should not be assumed to apply to every card. If an invoice fails, check the payment method and use Atlas’s option to retry the failed invoice after addressing the underlying problem. Contact the appropriate support team if you cannot identify the cause.

Manage charges when you are finished

Removing a card or leaving a project unused is not the same as stopping billable resources. To stop future deployment charges, terminate deployments you no longer need and review other billable Atlas activity. MongoDB says billing for Atlas activity stops after active clusters, projects, and organizations are deleted, but fees already incurred remain payable. Under its self-serve Cloud Terms of Service, amounts paid are non-refundable.

If your organization has a contracted subscription, review its order form and agreement before making changes: subscription payments may be non-refundable, and deleting a self-serve deployment does not necessarily cancel a contractual commitment. Keep an eye on invoices in Billing and check Coinepay’s dashboard or app for related card transactions.

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

FAQ

Do I need a card for the MongoDB Atlas Free tier?

Free is Atlas Core’s M0 tier, listed at US$0. Add a payment method when setting up a paid deployment or when Atlas requires one for the service you select.

Where do I change my Atlas payment card?

Open the relevant organization, then go to Billing → Overview → Payment Method → Edit. Projects in that organization share its billing settings.

Why did Atlas make a US$1 charge when I added my card?

MongoDB says it makes a US$1 verification charge when a card is first connected and refunds it. A decline of that charge can prevent card confirmation.

Will deleting my Atlas deployment cancel all charges?

Terminate deployments to stop their future charges, then review other Atlas activity and any subscription commitments. Fees already incurred remain payable.

How to Pay for MongoDB Atlas with a Coinepay Virtual Card