Use cases: Construction software
Your own card, tied to every job
Issue cards in your brand from your construction software: physical for crews, virtual for supplier orders, each swipe tied to a job and checked against its budget.
Field spend happens outside your software
On most jobs, field spend runs on the owner's personal card, a supply-house account or petty cash: materials runs, fuel, tools, equipment rental, permits and per diems. Receipts get chased at month-end, and the office codes each charge to a job and cost code weeks after the money is spent. Your software holds the jobs and the budgets, but the spending happens somewhere else.
With Moon, your platform launches its own card program through one API: physical cards for crews and virtual cards for supplier orders, all in your brand. Store the job and cost code on each card, and every authorization, purchase and decline reaches your platform by webhook with them attached. With real-time authorization enabled for your program, your platform approves each swipe against the job's remaining budget.
Corporate-card companies have started selling job-level cards to contractors, and some now sit inside construction software, where they own the card, the customer and the spend data. With Moon, the card program and the customer stay yours. Construction-credit lenders can use the same setup, so a contractor spends a materials line on a card and each swipe is approved against the line.
How the money moves
- Crew card issuedcrew_site7 · physical
- Job budget loadedSite 7 · $5,000.00
- Supply run approvedSupply house · $642.75
See the API call
curl --request POST \
--url https://api.themooncard.com/v1/api-gateway/card/8f1c611d-098d-4f61-b106-f7b6d344b1ae \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--header 'x-api-key: YOUR_API_KEY' \
--data '{
"external_id": "crew_site7",
"amount": 5000,
"card_type": "PHYSICAL",
"metadata": { "site": "7" }
}'What you can do
- 01
Crew cards for field spend
Give each crew or foreman a physical card for supply-house runs, fuel and small tools, loaded for the job and limited to the merchant categories you allow.
- 02
Virtual cards for orders
Create a virtual card for a materials order or an equipment rental booked in your app, for the order amount, and close it once the charge settles.
- 03
Permits and per diems
Pay permit fees and per diems for out-of-town crews on a card tagged to the job, so those costs land on the project instead of overhead.
- 04
Materials credit on a card
Construction-credit lenders can let contractors spend a materials line at any supplier that accepts Visa, with each swipe approved against the line.
- 05
A balance for each contractor
Set up each contractor customer as its own organization with its own balance and cards, so one company's job money never mixes with another's.
- 06
Crew changes and close-out
Freeze a card from your app when someone leaves the crew. When the job closes, close its cards and the unspent balance returns to your prepaid balance.
Why construction platforms choose Moon
Your card, your customer
Cards carry your brand and live in your app, so contractors manage job spend where they already run the job. The customer relationship and the spend data stay with your platform.
Every swipe tied to a job
Store the job and cost code as card metadata, and Moon returns them on every authorization, purchase and decline webhook. Daily reconciliation files give finance the full record.
Budgets checked at the swipe
With real-time authorization enabled for your program, your platform approves each purchase against the job's remaining budget or a contractor's credit line. Or load each card with the job's budget and let the balance set the limit.
Limits made for the field
Set monthly limits per card or per foreman, keep cards to the merchant categories a job needs, and freeze a card from your app in one call. Cardholder fees are set by your program and can be zero.
How it works
Connect
Integrate the Moon API, or start with our team on a pilot.
Issue
Create cards and send payouts from your own product.
Control
Set limits per card and see every transaction.
Questions
- Why not partner with a corporate-card company instead?
- You can, but then the card carries their brand, the contractor becomes their customer, and the spend data sits in their portal. With Moon it's your card program: cards in your brand, issued and controlled through one API, with every transaction reported to your platform. You decide the limits, the cardholder experience and the product roadmap.
- What about suppliers that add a fee for card payments?
- Some suppliers add a surcharge when a large invoice is paid by card. Use cards for field spend and smaller orders, where speed and job coding matter most, and keep big invoices on the payment terms you use today. Your platform can offer both side by side.
- How does spend get coded to jobs and cost codes?
- Your platform holds the jobs and cost codes. Store them as metadata when you create a card, or give each job its own card, and Moon returns that metadata on every authorization, purchase, refund and decline webhook. Receipt capture and accounting exports stay in your product, fed by those webhooks and the daily reconciliation files.
- Can crews be paid on the card?
- In the US, only as an option workers choose. Offer pay on a card next to direct deposit, let each worker decide, and check state payroll rules with your payroll and legal teams. Workers verify their identity through a hosted link from your app before their card is issued.
- Can a contractor's credit line back the card?
- Yes, through a lender partner. The lender carries the credit and funds the program; Moon doesn't lend. With real-time authorization enabled, each swipe is approved against the contractor's available line in the lender's ledger, and the line can be spent wherever Visa is accepted. Repayment and credit terms stay with the lender.
- Where can we launch, and which licenses do we need?
- Card programs can launch in the US, Latin America and Southeast Asia. Cards are issued by Moon's partner financial institutions under their licenses, so you don't need a card-issuing license of your own. You can start with a pilot on one job: the Sandbox runs the same endpoints as production, so you can issue a crew card for a test job, simulate supply-house purchases and declines, and check how your job costing handles each webhook.
Put your own card in every crew's truck.
Tell us how your contractors pay for field spend today, and we'll set up a sandbox around your jobs.
Other use cases
- Payroll, EOR & PEOPay employees and contractors on cards.
- Lenders & BNPLDisburse loans and fund purchases on cards.
- Insurance claim payoutsPay claims to a card instead of a cheque.
- Travel & booking agentsPay suppliers with one card per booking.
- Fleet, fuel & rideshareCapped cards for every vehicle and driver.
- Ad spend & marketing agenciesCards for every campaign, dozens per client.
- Property, facilities & hostsSpend cards per property and vendor payouts.
- Accounting firmsClient cards your firm can see and reconcile.
- AI agentsBudgets, controls or approval on every agent's card.
- Remittance & cross-borderCards for senders and the families they support.
- Marketplaces & creator payoutsPay sellers, pros and players the moment they earn.
- Brokerage, prediction & bettingA card on the cash or winnings in every account.
- Payment providers & B2B cross-borderCards on the balances you settle to clients.
- Loyalty & rewardsRewards, rebates, and refunds, spendable anywhere.