Create Accountor Login
Docs

Payments with Stripe

Part of the MountDev Ops Invoices documentation. Updated November 18, 2026

MountDev Ops Invoices documentation | Updated November 18, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

Your Own Stripe Account

Invoices charges your customers and takes their payments with your own Stripe account. The money goes straight to your Stripe balance; nothing passes through anyone else.

  1. In Stripe, open Developers, API keys, and copy your secret key (or a restricted key) and your publishable key.
  2. On Invoices' Settings page, under Payments With Stripe, copy the Webhook address (action invoices.stripe.status). In Stripe, open Developers, Webhooks, add an endpoint with that address, and choose these events: payment_intent.succeeded, payment_intent.processing, payment_intent.payment_failed, and setup_intent.succeeded. Copy the endpoint's signing secret.
  3. On Operations, then Integrations, then My Connections, choose Connect a Service, then Stripe, and enter the three keys (Connected Services). The secret key and the signing secret are stored encrypted and never shown again.

Until Stripe is connected, Run Billing says so, and invoices are not charged.

One Stripe Account for Several Workspaces

One Stripe account can serve more than one workspace (for example, two companies run by the same owner). Each workspace keeps to its own:

  • Everything it makes in Stripe (customers, payments, saved bank accounts and cards) is tagged with the workspace (mdo_account in Stripe's metadata), and its idempotency keys name the workspace, so two workspaces' invoice 12 are never the same payment.
  • Each workspace has its own webhook endpoint, and Stripe sends every event to both. A workspace acts only on what is its own: tagged with it, or (made before tagging) a payment it started or recorded, or one for a customer saved on one of its Billing Accounts. A dispute is acted on only by the workspace whose payment it is. Everything else is answered and ignored.
  • The daily check compares only the workspace's own payments with its invoices.
  • Give each workspace its own Card statement suffix (Invoices Settings, Disputes), such as MOUNTDEV, so clients see which company charged them.

Automatic Payments

When an invoice is finalized, it is charged with the customer's saved bank account, unless Charge automatically is off on the customer's Billing Account.

  • The bank account is charged first. If Stripe refuses the bank payment at once, before any money moves, and the customer saved a backup card, the card is charged instead.
  • Open late charges on the invoice are charged with it, as one payment.
  • A bank payment takes a few business days to clear. The invoice shows Payment clearing, and gets no reminders or late fees meanwhile.
  • If a bank payment comes back, it is never tried again on its own, not even on the backup card. The invoice is open again, the late fee clock starts from that day with the usual grace, the billing contacts are told by email, and your owners and admins are asked on Run Billing and by email to talk with the customer first. A person then chooses Charge Now, or the customer pays on their invoice page.
  • Customers who saved a bank account before (for a company moving from an older client portal) keep it: their Stripe customer and saved payment methods come over with their Billing Accounts, so nobody enters anything again.

One Charge per Invoice

Bank payments take days and rest on your customers' trust, so Invoices makes sure nobody is ever charged twice:

  • One payment at a time. Each payment on an invoice is recorded before Stripe is asked, and only one can be in progress for an invoice: starting, waiting on the invoice page, or clearing. Two runs, a retry, Charge Now pressed twice, or Pay pressed twice on the invoice page never start a second payment.
  • One key per attempt. Every payment is sent to Stripe with its own idempotency key for that invoice and attempt, so a retry after Stripe did not answer is always the same payment.
  • Clearing counts as in progress. While a bank payment clears, the invoice is not charged again by anyone.
  • The invoice page. Paying again with the same method is the same payment. Choosing the other method cancels the first one in Stripe before the new one is made; if Stripe cannot cancel it (it is already going through), nothing new is made.
  • Billed once. A finalized invoice keeps what it bills: each subscription line for its period, the client's monthly invoice for its month, a proposal payment, and a late fee. A second invoice for the same thing is refused when it is finalized, and the month's run leaves a line that is already billed off its new draft, with a warning. Voiding the first invoice frees them.

Payments in a Demo Account

A demo account holds made-up data only, so its payments never reach Stripe. Charging, refunds, payouts, and payment checks in a demo say: "This is a demo account, so no payment is made. Payments here never reach Stripe." See Demo Accounts.

The Daily Check

Every day after the daily run, Invoices reads the last 8 days of payments in your Stripe account that moved money and compares them with your invoices. If a customer was charged the same amount more than once within 7 days, or a payment belongs to no invoice or to more than one, your owners and admins get one alert on Run Billing and one email. Customers are never emailed about it, and the same findings are not raised again while the alert is open.

The Customer's Invoice Page

Every invoice email links to the invoice's own private page. No sign-in is needed, and the link expires after 180 days (each email has a fresh one).

  • The customer sees the invoice: who it is from, the dates, every line, the total, the balance, and any open late charges.
  • Download PDF makes the invoice as a PDF, with a Preparing spinner until it is ready.
  • Pay by Bank Account or Pay by Card opens Stripe's secure payment form on the page.
  • Save a Bank Account for Automatic Payments keeps a bank account for future invoices; a customer with one can add or change a backup card. Saving one never turns billing on by itself (Billing Active).
  • A draft never has a page, and a link for another company or invoice never works.

The Powered by Line

When your account turns on the Powered By line for invoices and receipts (Settings, Brand), a small "Powered by" line shows under the totals on the customer's invoice page. It is off until you turn it on. See Powered By and Earn.

Invoices from Your Previous Billing System

An invoice you imported from another billing system, and did not bill here, may still be collected by that system: its own email link, or its own automatic payments. So it can be paid in exactly one place:

  • Never charged here on its own. The daily run, Charge Now, and the invoice page never take a payment for it.
  • Paid from the Billing page, after a check. When a customer chooses Pay on it in their account, your connection to the previous system reads that system first. If the invoice is still unpaid there for the same amount, the invoice page opens to pay for 15 minutes, with every rule above (one payment at a time, one key per attempt, clearing counts as in progress). If the previous system cannot be reached, nothing is charged and the customer is asked to try again shortly.
  • Paid there first. If the previous system shows the invoice paid (all or part), those payments are copied onto the invoice here once each, with no receipt sent, and only what is left can be paid.
  • Recorded there after. Each payment taken here on such an invoice is listed for your connection to record in the previous system, so its own link and automatic payments have nothing left to take. A bank payment that comes back is removed there again.
  • Kept up to date. Your connection can also copy the previous system's payments onto every open imported invoice, so your customers' balances are right before anyone chooses Pay.
  • Taken over for good. When you are ready to stop using the previous system, your connection turns off its collection for these invoices, copies its last payments, and takes them over. From then each is an ordinary invoice here, paid on its page with no check. It is still never charged automatically; a person can choose Charge Now.
  • An imported invoice that came with a proposal payment or with the billing you took over is paid here as usual.

What Stripe Tells Invoices

Stripe sends each payment's news to the webhook address, and Invoices checks every message with your signing secret before it changes anything. Each message counts once.

  • Processing: the payment is recorded as Pending, and the invoice shows Payment clearing.
  • Succeeded: the payment is recorded, the balance goes down, and the billing contacts get a receipt. A payment for an invoice and its late charges is split over them, the invoice first.
  • Failed: see above for a bank payment that comes back. A card payment the customer tried on the page that did not go through leaves nothing behind.
  • A payment method saved: a bank account becomes the one charged automatically and a card the backup, each replacing the one before. The Billing Account keeps the day each was added, and the day a bank account was removed.

Card Disputes

When a client disputes a card charge, Invoices answers it with your evidence and tells your owners and admins at once (Card Disputes). Each card saved asks for 3D Secure where the card supports it, and the card's own checks are kept in the client's evidence record.

  • Your brand on the invoice page. Once you save a Brand Kit (Settings, Brand), the invoice page your customers open uses your colors, font, and logo. The seller name is the one in Invoices Settings, or your Brand Kit's name when that is empty (Brand Kit).

Ask Us Anything

We’d love to hear from you!