Auto-Charging Monthly Barricade Rentals to a Card on File

Short answer: to auto-charge a monthly barricade rental, get the customer's written agreement to recurring charges, save the card with your payment processor rather than in your own files, and tie the charge to the rental record so it stops when the devices come back. The agreement is the part most rental companies skip, and it is the part that decides whether a disputed charge stays paid.

Below is what the agreement needs to say, how to choose a billing cycle, how it works in Traffic OS, and what to do when a card fails.

Why rentals belong on a saved card

A barricade rental is an open engagement. The devices go out for a job whose end date nobody knows, and the bill repeats until they come back. For a large prime contractor that pays by check on its own schedule, a recurring card charge changes little. For the small contractors, utility subcontractors and private-property customers who make up much of a rental book, it removes the monthly chase.

Without a saved card, every billing period is the same routine: build the invoice, send it, wait, follow up, wait again. Across a few dozen open rentals, that becomes a standing job for someone in the office. With a saved card, the charge happens on the date it is due and the follow-up only starts when something fails.

There are customers you should not put on a card. A public agency will pay by its own process. A prime contractor with a negotiated payment term will not accept a card charge in place of it. Use cards where they fit, usually the smaller accounts, and keep invoicing the rest. Our post on taking card payments for barricade rentals covers the cost side of that choice.

What the customer has to agree to

The rule is simple: you may charge a saved card only for what the customer agreed to, and you need to be able to show the agreement.

Stripe's documentation on saving a payment method for later charges says the business is responsible for complying with laws and card network rules, and that terms for charging a customer who is not present should cover the customer's agreement to the payments, their expected timing and frequency, how the amount is worked out, and the cancellation policy.

Visa's 2017 guide to transactions with stored credentials goes further. Before storing a card for future use, the merchant must have an agreement with the cardholder that includes the last four digits of the card, how the cardholder will be told about changes to the agreement, when the agreement expires if it does, and how the card will be used. For charges the merchant starts, it adds the cancellation and refund policy, the merchant's location, the amount or how it is calculated, any surcharge where one is permitted, and the frequency of the charges. The same guide says to keep the agreement for as long as the consent lasts and to notify the cardholder when it changes.

For a barricade rental, that turns into a one-page authorization that travels with the rental agreement:

• The rental it covers — rental number, job or site, and the devices going out.
• The card — by brand and last four digits only.
• The amount — the weekly or monthly rate per device, or the total, and what is added on top, such as sales tax.
• The cycle — weekly or monthly, and the date the first charge happens.
• When it stops — when the devices are picked up, on the end date, or on written notice, whichever you agree.
• The partial period — how the last week or month is charged if the devices come back mid-cycle.
• Cancellation and refunds — how the customer stops the charges and what happens to a charge already made.
• Changes — how you will tell the customer about a rate change before it applies.
• Your business — legal name, address and a phone number for billing questions.

Have the customer sign it. A card read over the phone with no signed authorization is the charge that comes back as a dispute three months later.

Weekly or monthly

Pick the cycle per rental, not per company.

Monthly suits long jobs and established customers who reconcile once a month. It means fewer charges and fewer receipts for their bookkeeper.

Weekly suits short jobs, new customers you have not extended much credit to, and devices that turn over quickly. A declined card on a weekly cycle costs you one week of rent, not one month.

Traffic OS bills rentals weekly or monthly. It does not have a daily billing cycle; for short work, day rates can be used on quote and ticket lines instead. Whatever cycle you choose, write it into the authorization so the first charge does not surprise anyone.

How it works in Traffic OS

A rental in Traffic OS can be billed to a saved card. The charge runs through your business's connected Stripe account, so the money settles to you. The rental can be paused, resumed and given an end date, and the customer can update the card themselves in the customer portal instead of reading a new number to your office.

Two costs to know. Stripe charges its own processing fee, listed on Stripe's pricing page as 2.9% plus 30 cents for a domestic card as of November 2026. Traffic OS adds a 1% platform fee on payments that go through its Stripe connection; the current rate is shown in Settings. Traffic OS plans are $499, $949 and $1,499 a month with every feature, seats included, extra drivers $20 a month (as of November 2026). The pricing page has the plan details, and the barricade rental page shows how rentals fit with the rest of the system.

Rentals that are not on a saved card still bill weekly or monthly; they produce invoices the customer pays the usual way.

When a card is declined

Cards fail for ordinary reasons: the card expired, the customer hit a limit, the bank flagged an unusual charge, or the card was reported lost. Most of these are temporary.

Stripe's documentation on automatic payment retries says that for new Stripe accounts, Smart Retries is on by default and set to up to 8 retries within 2 weeks, and that a business can change the number and the window. It also lists hard declines, such as lost_card and stolen_card, that cannot be retried until the customer provides a new payment method.

In Traffic OS, when a rental charge is declined, the customer gets an email with a link to update the card in the customer portal, and Stripe keeps retrying on your account's schedule. Your part is the phone call. A useful sequence:

1. Day of the decline — the automatic email goes out. Nothing else.
2. Two or three days later — if the card has not been updated, call the customer's office. Most declines are an expired card nobody noticed.
3. About a week later — decide what happens next with the account: a new card, a switch to invoicing with your normal terms, or a pickup date.

One thing not to do: do not pull devices out of a live work zone because a payment failed. Barricades protecting an open closure are safety equipment for the crew and the traveling public. Agree a pickup with the contractor so the closure comes down properly.

Also look at what your Stripe account is set to do when the last retry fails. The same Stripe page lists the choices: cancel the subscription, mark it unpaid, leave it past due, or pause it. Pick the one that matches how you treat a rental whose devices are still out. Canceling ends the automatic billing for that rental.

Pausing, ending and extending

Pause only by agreement. A job on hold with the devices staying on site is still using your equipment. If you agree to stop billing during the hold, put it in writing; if not, keep billing.

End on the pickup date. Set the end date when the pickup is scheduled so the last charge is right and no charge runs after the devices are back in the yard. Our post on automating equipment rental billing covers why the pickup date is where rental revenue leaks.

Extend by moving the end date. A two-week extension should bill two more weeks without anyone remembering to do it.

Mistakes that cause disputes

• Charging without a signed authorization. It is the first thing a card issuer asks for when the customer disputes the charge.
• Charging after the devices came back. One charge after pickup and the customer stops trusting every charge before it.
• Keeping card numbers in a spreadsheet or a file. Let the processor hold the card.
• Adding a card fee without checking the rules. Card network rules and state law both apply, and they differ by state.
• Changing the rate without notice. The authorization should say how you will tell the customer, and you should do what it says.

Set up this way, a recurring charge is less work for you and less work for the customer's office, and the signed authorization is your answer when someone asks why their card was charged.