Manage Mongodb

How to cancel MongoDB and stop unexpected charges in new zealand

Understanding MongoDB and why you might want to cancel

MongoDB is a cloud database platform that offers flexible, scalable solutions for developers and organisations building modern applications. The service delivers managed clusters, serverless deployments, data lakes, and enterprise support through its MongoDB Atlas console. While powerful, MongoDB's billing model can catch you off guard if you're not managing active deployments carefully.

You might be cancelling because your project ended, costs escalated unexpectedly, or you've found a more suitable alternative. Whatever your reason, Stopee is here to walk you through the process with clarity and confidence. We've helped thousands of New Zealand consumers navigate cancellations that companies make deliberately confusing, and MongoDB is no exception.

When you should consider cancelling

Cancel your MongoDB subscription or support plan if you're no longer using the database, your free trial is ending and you don't want to pay, or your business has moved to a competitor. Many users discover that even after cancelling their support plan, active deployments continue charging them-a critical trap we'll help you avoid.

What MongoDB actually charges for

MongoDB charges for three main areas: your support plan (if you've purchased one), active database clusters, and serverless instances. The confusion arises because cancelling your support plan does not automatically stop charges from running clusters. You must terminate your deployments separately to prevent ongoing costs. At Stopee, we've documented this exact scenario hundreds of times with users who thought they'd cancelled everything.

Your consumer rights in new zealand and what they mean

New Zealand's Consumer Guarantees Act (1993) protects you even when cancelling digital services like MongoDB.

How the consumer guarantees act protects you

Under New Zealand law, digital services must be supplied with reasonable care and skill, delivered within a reasonable timeframe, and be fit for purpose. MongoDB's standard policy of "no refunds after 14 days" does not override these statutory rights. If MongoDB's service was faulty, misleading, or failed to deliver as described, you have grounds to dispute their refund terms and pursue a claim through the Consumer Guarantees Act.

Additionally, if MongoDB makes cancellation deliberately difficult, uses dark patterns to prevent you from leaving, or continues billing after you've attempted to cancel, these practices may breach the Fair Trading Act (2013). You can escalate to the Commerce Commission if MongoDB refuses to cooperate.

When you should escalate to authorities

Contact the Commerce Commission (comcom.govt.nz) if MongoDB refuses to honour a legitimate refund request within 14 days, continues charging after you've cancelled, or makes cancellation inaccessible. Document every step of your cancellation attempt, including screenshots and email confirmations. Stopee recommends keeping records for at least 12 months after any dispute.

Methods to cancel MongoDB: step by step

MongoDB offers multiple cancellation pathways depending on how you purchased your plan. Each has different steps and timelines.

Cancelling via MongoDB atlas (web console)

This is the primary method if you subscribed directly through MongoDB's website. Follow these steps precisely to avoid accidental charges.

1. Log in to your MongoDB Atlas account at mongodb.com/cloud/atlas
   • Use the email address and password associated with your account
   • Enable two-factor authentication if prompted for security
2. Navigate to the billing section
   • Click your account name in the top right corner
   • Select "Billing" from the dropdown menu
   • You should see your current plan and billing history
3. Locate your support plan or subscription
   • Find the active plan you wish to cancel (look for "Support Plan" or "Subscription" labels)
   • Check whether you're within the 14-day refund window
4. Select the cancel or downgrade option
   • Click the three-dot menu next to your plan
   • Choose "Cancel Plan" or "Downgrade"
   • MongoDB will ask you to confirm; select "Yes, cancel"
5. Confirm the cancellation takes effect
   • If you're within 14 days of purchase, billing stops immediately
   • If you're outside 14 days, cancellation takes effect at the end of your current billing month
   • You'll receive a confirmation email within minutes
6. Terminate all active deployments to stop charges
   • Go to the "Clusters" or "Deployments" tab
   • Select each active cluster, data lake, or serverless instance
   • Click "Delete" and confirm the permanent deletion
   • Warning: This action is irreversible; ensure you've backed up any critical data first

Cancelling app store subscriptions (iOS and android)

If you purchased MongoDB through Apple's App Store or Google Play, you cannot cancel within MongoDB's console. You must use the app store's subscription management system instead.

1. For Apple App Store subscriptions
   • Open the App Store app on your iPhone or iPad
   • Tap your account icon (top right corner)
   • Select "Subscriptions"
   • Find "MongoDB" in your active subscriptions
   • Tap "Cancel Subscription"
   • Confirm the cancellation date (usually the next renewal date)
2. For Google Play subscriptions
   • Open the Google Play app on your Android device
   • Tap your profile icon (top right)
   • Select "Payments and Subscriptions" then "Subscriptions"
   • Find "MongoDB" and tap it
   • Select "Cancel Subscription"
   • Follow the prompts to confirm cancellation
3. Verify the cancellation in your account
   • Return to MongoDB Atlas and check your billing section
   • Confirm your subscription no longer appears as active
   • Keep your cancellation confirmation email for your records

Cancelling via customer support (escalation method)

Pro tip: If you encounter technical issues or the self-service options don't work, contact MongoDB support directly. This creates a documented paper trail, which strengthens any future dispute.

1. Visit MongoDB's support contact page at mongodb.com/support
   • Select "Contact Support"
   • Choose "Billing" as your issue category
2. Submit your cancellation request in writing
   • State clearly: "I request immediate cancellation of my support plan and all active deployments"
   • Include your MongoDB account email and cluster names
   • Request written confirmation of the cancellation date
3. Follow up within 48 hours if you don't receive confirmation
   • Reply to MongoDB's response with a polite escalation
   • Ask for a cancellation reference number
4. Check your billing in Atlas after support confirms
   • Verify charges have stopped and deployments are deleted
   • Retain all support emails for your records

Refund eligibility and how to claim

MongoDB's official refund policy allows returns within 14 days of purchase. However, your consumer rights in New Zealand may entitle you to refunds beyond this window.

Refunds for direct MongoDB purchases

If you paid MongoDB directly (not through an app store), you can request a refund within 14 days of the transaction date. After 14 days, MongoDB's policy states refunds are not provided, but this does not prevent you from asserting your statutory rights if the service was faulty or misrepresented.

1. Calculate your 14-day window
   • Check your invoice or billing email for the purchase date
   • Count 14 calendar days from that date
   • If today falls within that window, you're eligible for a standard refund
2. Request your refund via support
   • Contact MongoDB support at mongodb.com/support
   • Provide your invoice number and account email
   • State: "I request a refund within the 14-day refund period"
   • Mention any technical issues or service failures that justify the refund
3. Follow up if MongoDB denies your request
   • Reference the Consumer Guarantees Act and New Zealand's statutory rights
   • Request a written explanation of their denial
   • Escalate to Stopee or the Commerce Commission if they refuse without justification

Refunds for app store purchases

Apple and Google handle refunds for subscriptions purchased through their platforms, not MongoDB directly. Contact them within 14 days of purchase for a full refund.

1. Request a refund from Apple (iTunes)
   • Visit reportaproblem.apple.com
   • Sign in with your Apple ID
   • Find the MongoDB charge and select "Report a Problem"
   • Choose "I would like a refund for this purchase"
   • Apple typically responds within 2-5 business days
2. Request a refund from Google Play
   • Visit play.google.com/store
   • Open your account menu and select "Order History"
   • Find the MongoDB charge and click "Report a Problem"
   • Select "Refund" and confirm
   • Google processes refunds within 1-3 business days

MongoDB pricing and plan options

Understanding MongoDB's pricing structure helps you choose the right plan and avoid surprise charges.

How to avoid surprise charges

Stopee's top tip: activate billing alerts in MongoDB Atlas to get notifications when your monthly spend reaches certain thresholds. Set alerts at 50%, 80%, and 100% of your expected budget to catch runaway costs early.

What happens after you cancel

Cancellation is not instantaneous; understanding the timeline prevents confusion and accidental re-billing.

Immediate effects on your account

Once you cancel, MongoDB will confirm the cancellation date via email. If you cancelled within 14 days, your support plan billing stops immediately. Outside 14 days, your plan remains active until the end of the current billing month. Your account access continues until the cancellation date, but new charges will not accrue for the cancelled plan.

Data retention and deployment access

Cancelling your support plan does not delete your data or deployments. You retain full access to your clusters, databases, and backups until you explicitly delete them. However, any active deployments continue to incur charges-a critical point many users miss. Stopee strongly advises deleting deployments as soon as you cancel if you don't plan to use MongoDB further.

Timeline for billing cessation

• Within 14 days: charges stop within 24 hours of cancellation confirmation
• After 14 days: charges continue until the end of your billing month, then stop
• Active deployments: charges continue indefinitely until explicitly deleted, regardless of support plan status
• Final invoice: MongoDB sends a prorated final invoice within 5-7 business days

Common mistakes that cost you money

Cancelling can feel stressful, and it's easy to overlook critical steps. We've seen these mistakes happen repeatedly, and they're entirely preventable.

Mistake one: cancelling your support plan and forgetting deployments

The most expensive error is cancelling your support plan while leaving clusters, data lakes, or serverless instances running. These continue charging you separately. Always delete your deployments immediately after cancelling your plan. Check your billing section weekly for 30 days post-cancellation to confirm charges have stopped.

Mistake two: assuming app store cancellation cancels everything

Cancelling a MongoDB subscription through Apple or Google does not affect your Atlas deployments or support plan. You must cancel both the app store subscription and your Atlas account separately. Stopee recommends cancelling Atlas first, then the app store subscription to avoid confusion.

Mistake three: not requesting written confirmation

If you contact MongoDB support verbally or via chat, always ask for a written confirmation email with a cancellation reference number. This protects you if charges continue and you need to dispute them. Self-service cancellations send automatic emails, but support cancellations sometimes don't-follow up within 48 hours if you don't receive confirmation.

Mistake four: missing the 14-day refund window

If you're outside the 14-day refund period, MongoDB will not issue a standard refund. However, Stopee advises you to still request one if the service was faulty or misrepresented. Include evidence of the problem in your request. The Consumer Guarantees Act may entitle you to a refund even after 14 days if the service failed to meet statutory standards.

Checklist before and after cancellation

Use this checklist to ensure you complete every necessary step and protect yourself from accidental charges.

Before you cancel

• Check whether you're within the 14-day refund window (look at your invoice date)
• Download or back up any data you need from your clusters
• Review your current billing statement to understand what you're paying for
• Decide whether to keep the free tier for future use or delete all deployments
• Screenshot your current billing section for your records

During cancellation

• Follow the exact steps for your cancellation method (web, app store, or support)
• Write down the cancellation date and reference number if provided
• Take a screenshot of the cancellation confirmation page
• Do not close your browser until you see "Cancellation confirmed"
• Delete all active deployments (clusters, data lakes, serverless instances)

After cancellation

• Check your email for a cancellation confirmation from MongoDB within 2 hours
• Log back into MongoDB Atlas and verify your plan no longer appears active
• Check your billing section again and confirm no new charges are pending
• Set a reminder to verify your next billing cycle (usually 30 days later) to confirm charges have stopped
• Save all confirmation emails and receipts for 12 months
• If charges continue, contact MongoDB support with your cancellation confirmation email

Deciding whether to keep or cancel MongoDB

Before you cancel, consider whether MongoDB still serves your needs or if the costs have simply become prohibitive.

Reasons to keep MongoDB

• You're actively developing or running applications in production
• The free tier meets your requirements at no cost
• Your business has budget allocated for database infrastructure
• You need enterprise support and compliance features
• Switching databases would cost more in engineering time than MongoDB's monthly fees

Reasons to cancel MongoDB

• Your project has concluded and you no longer need a live database
• Costs have escalated beyond your budget, and no cheaper alternative exists
• You've migrated to a competitor (PostgreSQL, DynamoDB, Firestore, etc.)
• Your trial period ended and you don't plan to pay for production use
• Deployments are running unnecessarily and accruing unmonitored charges
• MongoDB's pricing model doesn't align with your workload (e.g., too expensive for sporadic use)

Alternatives to full cancellation

If you're concerned about costs but want to keep MongoDB available, consider downgrading rather than cancelling. Downgrade to the free tier, delete unnecessary deployments, or pause serverless instances. Stopee recommends this middle-ground approach if you think you'll return to MongoDB in the future.

Contacting MongoDB in new zealand

If cancellation goes wrong or charges continue after you've cancelled, contact MongoDB directly. Stopee has compiled the official contact details for MongoDB's New Zealand entity.

Official MongoDB new zealand office

MongoDB New Zealand Limited is the registered legal entity responsible for cancellations and billing disputes in New Zealand.

• Company name: MongoDB New Zealand Limited
• Service of cancellation correspondence: Direct all cancellation notices to the registered office address
• Support contact: mongodb.com/support (email and chat)
• Billing inquiries: billing@mongodb.com
• Complaints: If standard support doesn't resolve your issue, escalate to MongoDB's legal team via registered office

Escalation to the commerce commission

If MongoDB refuses to honour a legitimate refund or continues billing after cancellation, file a complaint with the New Zealand Commerce Commission (comcom.govt.nz). Provide documentation of your cancellation attempts, confirmation emails, and billing records. The Commerce Commission has authority to investigate unfair trading practices and may compel MongoDB to refund you.

Final summary and next steps

Cancelling MongoDB doesn't have to be complicated. You've now learned how to navigate every cancellation method, understand your refund rights, and protect yourself from the most expensive mistakes. The key steps are simple: cancel your support plan in the Atlas console, delete all active deployments, and request written confirmation. If you're within 14 days, ask for a refund. If MongoDB refuses and you believe the service was faulty, invoke the Consumer Guarantees Act or contact the Commerce Commission.

Stopee has helped thousands of New Zealand consumers cancel subscriptions that companies deliberately obscured, reclaim undeserved charges, and assert their statutory rights. Whether you're leaving MongoDB for a competitor or pausing your account, you now have the knowledge and confidence to do it correctly. If you encounter resistance from MongoDB or if charges continue after cancellation, Stopee's detailed guides and consumer rights resources are here to support your next escalation. Take control of your billing today.