Taking Deposits and Prepayments: How Card Rules Treat Money Collected Before Delivery, and the Documentation That Protects You

A card payment collected today for a product or service delivered weeks or months later creates a different risk profile from a normal same-day retail sale. The merchant receives money before completing its obligation, which makes clear customer authorization, delivery terms, refund policies, processor disclosure, and fulfillment records especially important.

Taking deposits by credit card is legitimate and common across many industries. Contractors collect deposits before ordering materials, custom manufacturers take advance payments before production, event venues reserve dates with customer deposits, ecommerce sellers accept preorders, and service businesses may collect partial payment before work begins.

The complication is not simply that money was collected early. It is that the transaction remains connected to a future obligation. Until the merchant delivers the promised goods or performs the service, there is continuing exposure to cancellation requests, refunds, customer complaints, business interruptions, fulfillment delays, and card disputes.

Visa’s advance-payment guidance defines an advance payment as a transaction covering part or all of the cost of goods or services that will be provided later. 

Its guidance emphasizes disclosure, customer consent, transaction processing, receipts, cancellation procedures, and refund policies. Merchants can review Visa’s dedicated guidance on advance-payment transactions directly.

The operating principle is straightforward:

The longer the gap between payment and delivery, the more important accurate disclosure, authorization, fulfillment records, refund terms, and processor underwriting become.

A strong operational workflow follows the entire obligation rather than treating the initial transaction as finished:

Customer Agreement → Deposit/Prepayment → Payment Authorization → Order/Service Record → Fulfillment Tracking → Delivery/Completion → Final Payment → Reconciliation → Dispute Documentation

The following guide explains how merchant deposits and prepayments work, how future-delivery activity affects merchant accounts, and what documentation businesses should maintain from the moment a customer agrees to pay until the obligation is completely fulfilled.

What Is a Deposit or Prepayment?

A deposit is generally an amount collected before the entire purchase or service has been completed. It may reserve inventory, secure an appointment or event date, fund the beginning of custom work, demonstrate customer commitment, or apply toward a later final balance.

A partial prepayment covers only part of the expected total purchase price. A full prepayment means the customer pays the entire amount before all goods or services have been delivered. The business may also use terms such as advance payment, booking deposit, service deposit, down payment, or preorder payment.

A retainer can be different. In some professional fields, the word may have specific contractual, legal, accounting, or trust-account implications. A lawyer’s trust retainer, for example, should not automatically be treated as equivalent to an ordinary merchant prepayment for a custom product.

Likewise, a preorder is usually a purchase accepted before the merchandise is available for immediate shipment or delivery. A preorder may involve a deposit or full payment depending on the seller’s arrangement and applicable rules.

Terminology matters because card-network rules, merchant agreements, consumer law, and accounting treatment do not necessarily use each term in exactly the same way.

Deposit vs. prepayment vs. authorization hold

An authorization hold is particularly important to distinguish from a deposit. Authorization asks the issuer whether a transaction can be approved and may temporarily reduce the customer’s available credit or funds. It is not the same as capturing and settling a payment.

A captured deposit, by contrast, is submitted into the payment flow for clearing and settlement. Once funded, the merchant has received money even though some or all of the promised goods or services remain outstanding.

This distinction matters operationally. Businesses should not attempt to use an ordinary authorization hold as a long-term substitute for a genuine deposit simply because fulfillment will occur later. Authorization validity, reauthorization procedures, reversal requirements, and permitted practices depend on transaction type and network rules.

For additional background, the distinction between payment authorization and settlement is explained in this merchant-processing guide. Payment Authorization vs. Settlement Explained Visa also describes reauthorization as a separate tool for situations in which fulfillment extends beyond the original authorization validity period, including certain delayed ecommerce shipments.

Payment Type	Money Captured?	Merchant Has Funds?	Typical Purpose
Authorization hold	Usually no	No	Temporarily confirm availability or secure an estimated amount
Deposit	Yes	Normally after settlement	Reserve goods, services, production capacity, or a future commitment
Partial prepayment	Yes	Normally after settlement	Pay part of the purchase before fulfillment
Full prepayment	Yes	Normally after settlement	Pay the entire purchase price before fulfillment
Final payment	Yes	Normally after settlement	Pay the remaining balance at or near completion

A recurring payment is different again. It involves charges made according to an agreed recurring schedule. An installment payment usually divides a purchase into planned payments over time. A stored credential simply means payment credentials or a token are retained for eligible future transactions; storing a credential does not by itself authorize every future charge.

Can Merchants Take Deposits by Credit Card?

Yes. Merchants can commonly accept legitimate deposits or advance payments by credit card, provided the transactions comply with applicable card-network requirements, the merchant agreement, processor or acquirer policy, consumer-protection law, and any industry-specific restrictions.

Visa’s advance-payment transaction guidance recognizes both partial and full advance payments and addresses disclosure, customer consent, transaction processing, receipts, cancellation procedures, and refund policies. 

There is no single universal card deposit rule that gives every merchant the same allowable deposit percentage, fulfillment period, maximum ticket, or cancellation policy.

Visa, for example, has specific global guidance for advance-payment transactions. Its published materials state that cardholder disclosures for advance payments should cover matters such as the promised goods or services, transaction amount, delivery timing, total purchase price, refund and cancellation policies, and—in partial-payment arrangements—terms for the final payment.

American Express also has rules governing advance-payment and delayed-delivery charges. Its merchant regulations can require disclosure and consent, separate authorizations in delayed-delivery arrangements, and appropriate identification of the deposit and balance. Exact obligations depend on the applicable merchant agreement, country, and transaction structure.

Mastercard publishes its rules and transaction-processing standards for merchants and processors and expressly cautions that standards can change and that official rules control where discrepancies occur. Merchants should therefore confirm their specific workflow with their acquirer or processor rather than copying another business’s deposit policy.

Deposit and prepayment card rules depend on the transaction

Several factors can change the compliance and risk analysis:

• Whether the transaction is card-present or card-not-present
• Whether the amount is a partial or full prepayment
• How far in advance payment is collected
• Whether the merchandise is custom-made
• Whether the customer can cancel
• Whether the merchant will keep any amount after cancellation
• Whether there is a final balance
• Whether the payment credential will be stored
• Whether the service is provided at specific milestones
• Whether state or industry rules impose additional requirements
• Whether the merchant’s approved processing profile includes future-delivery sales

A custom cabinet maker collecting a deposit for materials presents a different profile from an ecommerce company accepting thousands of preorders for a product not yet manufactured. Both may be legitimate, but the amount of undelivered customer money and the time before fulfillment are different.

The merchant’s processing agreement matters as well. Some accounts are underwritten based on expected monthly volume, average ticket, maximum ticket, refund exposure, sales channel, delivery timeframe, and business model. 

A business that materially changes those characteristics should communicate with its processor rather than assuming initial approval covers every future sales strategy.

Why Advance Payments and Future Delivery Create Additional Risk

Future-delivery risk exists because the card transaction can be complete while the merchant’s underlying commercial obligation is not.

Suppose a furniture company receives a $4,000 payment for a custom dining set scheduled for delivery several months later. The transaction may settle quickly, but the company still has to purchase materials, manufacture the product, complete quality control, arrange shipping, and deliver the furniture as promised.

During that interval, several things can go wrong:

• Production may be delayed.
• Suppliers may fail.
• The customer may cancel.
• The merchant may suffer a cash-flow problem.
• The customer may claim the product was never delivered.
• The merchant may be unable to issue expected refunds.
• A large number of prepaid orders may become due at the same time.
• The business may stop operating before fulfillment.

From an acquiring perspective, this creates exposure that does not exist to the same degree in a normal same-day retail transaction.

A processor or acquirer may therefore look not only at how much the merchant processes, but how much of that volume represents unfulfilled customer obligations. Long delivery periods, large future obligations, rapid volume growth, refund delays, or increasing disputes may contribute to additional review.

Future-delivery merchant accounts and underwriting

Merchant underwriting creates a baseline for the processing account. Underwriters may examine expected monthly volume, average ticket, highest expected transaction, business history, sales channel, refund policy, fulfillment model, chargeback history, and financial capacity.

A useful overview of how merchant accounts are approved explains how delayed delivery, ticket size, chargebacks, refund exposure, and processing history can influence risk review.

For a merchant account for prepayments, the processor may reasonably want to understand:

• What percentage of customers pay before delivery
• Typical time from payment to fulfillment
• Average and maximum prepayment amount
• Whether deposits are refundable
• Whether goods are custom-made
• How cancellations are handled
• How the business funds fulfillment
• How delivery or service completion is documented
• Whether major seasonal preorder campaigns are expected
• Whether the merchant retains stored payment credentials

This does not mean every future-delivery merchant is automatically classified as high risk. Risk depends on the whole profile.

A long-established contractor with stable volume, documented milestone billing, strong financials, and short completion periods may present a very different profile from a new seller collecting full payment on unproduced goods with uncertain release dates.

Credit Card Deposits Before Delivery: Building the Transaction Correctly

The safest deposit workflow starts before the payment page or terminal is opened.

Customers should understand exactly what they are paying for, whether the payment is partial or full, what remains due, when they should expect performance, and what happens if either side cancels.

Visa’s advance-payment guidance is useful because it illustrates how detailed that disclosure can be. The guidance identifies the promised goods or services, terms of service, delivery timing, transaction amount, refund and cancellation policy, total price, other charges, and final-payment terms where relevant as information associated with written advance-payment consent.

Partial deposit, full prepayment, and milestone billing

Different payment structures distribute risk differently.

Structure	Merchant Benefit	Customer Risk	Processor Risk
Smaller deposit	Provides commitment while limiting advance collection	Lower amount exposed before fulfillment	Lower outstanding prepaid amount, all else equal
Larger deposit	Provides more working capital or material funding	More money paid before receiving value	Greater unfulfilled payment exposure
Full prepayment	Maximum upfront cash flow	Entire purchase price is exposed until fulfillment	Highest outstanding obligation for that order
Milestone billing	Aligns collections with project progress	Customer pays as value is created	Exposure can be aligned with completed work

There is no universal percentage that makes one structure compliant and another noncompliant. The appropriate structure depends on the merchant agreement, economics of the job, applicable law, customer contract, and the processor’s approved profile.

For long projects, genuine milestone billing can make operational sense:

Deposit → Materials/Start → Midpoint → Completion

Each milestone should represent a legitimate part of the commercial arrangement. Businesses should not create artificial partial payments merely to stay below a processor’s ticket threshold, bypass fraud controls, avoid an authorization requirement, or hide the true size of a transaction.

Deposit amount, average ticket, and large transactions

Merchant account average ticket deposits deserve special attention. If an account was underwritten around $100 transactions and the merchant suddenly begins processing multi-thousand-dollar deposits, the activity may no longer resemble the approved profile.

The issue is not that a large deposit is automatically prohibited. It is that payment risk systems compare actual processing with expected activity.

Before accepting materially larger tickets or substantially higher monthly volume, merchants should review their merchant agreement and talk to their processor. Relevant questions include whether the expected ticket range has changed, whether supporting invoices may be requested, and whether the new delivery timeframe alters the account’s risk profile.

Rapid changes can also occur when a business introduces a new product line. A merchant that historically sells ready-to-ship products but begins taking full payment for custom goods months in advance should not assume its existing account was underwritten for the new model.

Card-Present, Card-Not-Present, Phone, and Online Deposits

A deposit can be taken in person or remotely, but those channels are not identical from a payment-risk perspective.

With a card-present transaction, the customer and merchant interact at the same location and an approved terminal can capture chip, contactless, or other card-present data. 

That interaction can provide useful transaction evidence, but it does not make the payment immune from chargebacks. The customer can still dispute a deposit for issues such as non-delivery, cancellation, refund problems, or a disagreement about the service.

A card-not-present deposit occurs when the card is not physically presented to the merchant. Common examples include ecommerce checkout, telephone payments, invoice links, mobile payment links, and virtual-terminal transactions.

Remote transactions generally place more importance on identity verification, authentication, customer consent, order records, and fulfillment evidence.

Card-not-present deposits and online checkout

A well-designed online deposit checkout should tell the customer, before payment:

• The deposit amount
• What the deposit applies to
• The total price where known
• Remaining balance
• Expected delivery or service date
• Cancellation rules
• Refund terms
• Merchant identity and contact information
• What happens after payment
• Whether a credential will be stored for later use

Where appropriate, the merchant should retain evidence that the customer affirmatively accepted relevant terms. That might include an electronic acceptance record, order confirmation, contract signature, or checkout consent record.

Security also matters. A hosted payment page or properly implemented payment integration can reduce the need for staff to handle raw card data.

Taking deposits over the phone

Telephone deposits should be processed through an approved virtual terminal or another secure payment workflow supported by the merchant’s provider. Staff should not casually write complete card numbers on paper, copy payment information into notes, or request that customers send card numbers by ordinary email.

Call recording deserves particular attention. PCI Security Standards Council guidance says sensitive authentication data such as card verification values may not be retained after authorization. For recorded payment calls, organizations should prevent sensitive authentication data from being recorded where possible or securely remove it as required.

PCI SSC also confirms that a card verification code may be requested when appropriate for authorization in a card-not-present transaction, but it must not be stored after authorization, even in encrypted form.

Deposit Authorization Documentation and Customer Agreements

Documentation protects more than a chargeback response. It helps customer service explain the order, finance reconcile money, operations track fulfillment, and management identify outstanding obligations.

For each deposit or prepayment, the business should be able to connect the payment to a specific customer obligation.

At minimum, a practical record may contain:

• Customer name
• Order, invoice, reservation, or contract number
• Transaction date
• Deposit or prepayment amount
• Total price where known
• Remaining balance
• Description of goods or services
• Expected delivery, completion, or service date
• Refund and cancellation terms
• Customer acceptance record
• Processor transaction identifier
• Payment confirmation
• Subsequent changes or communications

These records are more useful when maintained during the normal course of business rather than assembled after a dispute has already occurred.

What a credit card deposit agreement should address

A deposit agreement should make the commercial arrangement understandable without forcing the customer to reconstruct it from several disconnected documents.

It should explain what the customer is buying, what the deposit secures, whether the payment is partial or full, when the balance becomes due, and when the merchant expects to deliver.

It should also describe relevant cancellation and refund rules. For custom work, this may include production milestones, change-order procedures, approval steps, and the effect of cancellation after production begins.

For event businesses, the contract may address the reserved date, cancellation, rescheduling, no-show conditions, and merchant cancellation. For contractors, it may address job scope, materials, milestones, expected completion, and customer approvals.

State law may independently regulate some deposits. Home-improvement contracts are a good example: deposit limits, cancellation rights, contract wording, licensing rules, or notices can vary by jurisdiction. Card-network compliance does not replace those obligations.

Businesses should therefore use qualified counsel when the underlying contract is legally significant rather than treating a generic payment-processing checklist as universal contract language.

Refundable and nonrefundable deposits

Calling a payment nonrefundable does not automatically eliminate cardholder dispute rights, network rules, or consumer-law obligations.

A merchant may have a legitimate cancellation provision allowing it to retain some or all of a deposit in specified circumstances, but the provision should be clearly disclosed and lawful. The merchant still needs to consider whether it actually performed according to the agreement.

Visa’s advance-payment guidance, for example, ties retention of certain nonrefundable advance payments to appropriate disclosure on the transaction receipt and also says a merchant must refund the amount paid when it has not adhered to the terms of the sale or service.

A strong prepayment refund policy is therefore:

• Visible before payment
• Consistent across checkout, contract, and receipt
• Specific enough to understand
• Consistently applied
• Compatible with applicable network and merchant rules
• Compatible with relevant consumer law

Preorders, Delayed Delivery, Custom Orders, Contractors, and Events

Preorders are one of the clearest examples of future-delivery payment risk. The merchant may accept money before inventory is available, which makes accurate release-date representations and delay management especially important.

Customers should receive realistic information about availability, shipping, cancellation, and refund options. A speculative production date should not be presented as guaranteed if the merchant lacks a reasonable basis for that promise.

For merchandise ordered through the Internet, phone, or mail in the United States, the FTC’s Mail, Internet, or Telephone Order Merchandise Rule can also apply. The FTC states that sellers must have a reasonable basis for the advertised shipment timeframe. 

The FTC Mail, Internet, or Telephone Order Merchandise Rule requires covered sellers to have a reasonable basis for their advertised shipment timeframe. When shipment cannot occur as promised, the rule can require customer consent to the delay or a refund for the unshipped merchandise. 

If no shipment time is stated, the rule generally uses 30 days; if the seller cannot ship as required, delay-consent and refund obligations can arise.

Merchants can review the FTC’s official rule guidance.

That rule concerns covered merchandise sales and should not be casually applied to every service transaction.

What to do when delivery is delayed

When a promised delivery or service date slips, silence is usually the wrong operational response.

A practical delayed-fulfillment workflow is:

1. Identify affected prepaid orders.
2. Notify customers promptly.
3. Explain the reason without making unsupported promises.
4. Provide a realistic revised delivery or completion date.
5. Offer any cancellation or refund options required by the agreement, card rules, or law.
6. Record the customer’s decision.
7. Update the order and fulfillment system.
8. Escalate material business-wide delays to the processor when appropriate.

Visa’s dispute guidance similarly advises merchants to keep customers informed when delivery is delayed and to provide updated delivery or service dates.

Custom orders and contractors

Custom-order deposits require unusually good specifications. The record should show what is being made, approved dimensions or features, customer-selected materials, production changes, approvals, expected completion, and delivery.

If the customer requests a change, use a documented change order. A dispute becomes much harder to explain when the original contract says one thing, staff notes say another, and the final product reflects an undocumented phone conversation.

Contractors and home-service businesses should link deposit payments to work orders and project milestones. Documentation may include signed scope, material orders, permits where relevant, progress photographs, customer communications, milestone invoices, and completion acknowledgement.

However, local contractor and home-improvement laws may regulate deposits independently. Businesses should verify state requirements rather than assuming payment-card rules determine the maximum allowable deposit.

Event and reservation deposits

Event venues, photographers, caterers, planners, and similar businesses often collect money to reserve capacity that cannot easily be resold at the last minute.

Their agreements should distinguish between reservation deposits, installment payments, cancellation charges, rescheduling, no-show terms, and payments for services already performed.

Force-majeure or extraordinary-event clauses may also be relevant, but those are contractual matters that should be reviewed with qualified counsel.

A card transaction does not make a contract enforceable by itself. Likewise, a signed contract does not prevent a cardholder from initiating a dispute. Good operations require both a valid commercial agreement and accurate payment processing.

Milestone Payments, Split Payments, Final Balances, and Stored Credentials

A legitimate partial-payment workflow can be useful when value is delivered over time.

A contractor might collect a deposit when the contract is signed, another payment after materials are delivered, a progress payment after a defined stage, and the final balance after completion. A custom manufacturer might collect a design deposit, a production payment after customer approval, and a final payment before or at delivery.

Those are legitimate milestone structures when the payments reflect the actual commercial arrangement.

They are not the same as artificially splitting one large charge into multiple smaller transactions solely to avoid authorization controls, fraud screening, processor ticket limits, or account monitoring.

Merchants should explicitly reject practices such as:

• Splitting charges to remain below an approved ticket limit
• Using another merchant account to hide volume
• Processing a deposit as an unrelated retail purchase
• Selecting an inaccurate MCC
• Misrepresenting the delivery date
• Routing transactions around processor risk controls

Deposit plus final payment

When a deposit and final payment are separate transactions, both should remain linked to the same commercial record.

Use the same:

• Customer
• Contract
• Project or order number
• Invoice
• Fulfillment record
• Internal customer account

The final invoice should show the total purchase price, the deposit already received, adjustments or approved changes, and the remaining amount due.

This makes reconciliation easier and provides a more coherent evidentiary record if either payment is later questioned.

Card-on-file for the remaining balance

Some businesses want to retain a customer’s payment credential and automatically charge the final balance later. That arrangement must be distinguished from simply accepting the initial deposit.

Visa’s stored-credential framework requires merchants and other participants to follow specific stored-credential processing requirements. Its published guidance describes stored credentials as card information or tokens retained for future transactions and emphasizes transaction identification and consent.

Merchants can review Visa’s stored-credential framework directly.

Storing a credential does not mean the merchant has unlimited authority to charge it whenever desired. The merchant should have appropriate customer authorization for the final-balance arrangement, follow applicable network and processor requirements, and use the correct transaction indicators.

Never retain the CVV for future balance charges. PCI SSC expressly prohibits storing the card verification code after authorization for card-on-file or recurring transactions.

Receipts, Descriptors, Fulfillment Evidence, and Dispute Documentation

A deposit receipt should make the transaction recognizable months later.

At minimum, it should identify the merchant, transaction date, deposit amount, what the payment applies to, remaining balance where relevant, and the next expected step.

Depending on the applicable network rules and transaction type, additional information may be required. Visa’s advance-payment guidance, for example, describes receipt information such as the advance-payment amount, scheduled delivery or start date, cancellation and refund policy, and appropriate terms such as “Advance Payment,” “Prepayment,” “Deposit,” “Partial Payment,” or “Balance.”

A recognizable billing descriptor also helps. A customer who sees an unfamiliar name months before delivery may assume fraud occurred and contact the issuer rather than the merchant.

Proof of delivery and proof of service completion

For physical goods, fulfillment evidence may include:

• Carrier tracking
• Shipping address
• Delivery confirmation
• Signature confirmation where appropriate
• Store-pickup record
• Pickup identification or acknowledgement
• Customer communication confirming receipt

For services, evidence may include:

• Appointment records
• Work orders
• Completed project milestones
• Customer acceptance
• Signed completion record
• Electronic check-in or service logs
• Completion photographs where appropriate and lawful
• Correspondence discussing completed work

Evidence should be created as part of normal operations. Staff should never fabricate a signature, reconstruct a false delivery record, alter a timestamp, or manufacture documentation after receiving a dispute.

Advance payment dispute defense

When an advance payment is disputed, the best evidence depends on the reason for the dispute.

Potentially relevant records include:

Record	Why It Matters
Order or contract	Shows what was purchased and the commercial terms
Deposit authorization	Connects customer consent to the payment
Receipt	Shows amount, timing, and transaction description
Refund/cancellation policy	Establishes disclosed cancellation terms
Customer communications	Documents approvals, changes, delays, or cancellations
Delivery/progress record	Shows fulfillment or progress
Final invoice	Connects deposit to total price and remaining balance
Refund documentation	Shows whether and when a credit was issued
Processor transaction ID	Connects business records to the payment-system record

Visa describes a dispute as a reversal of all or part of a transaction through the issuer/acquirer process and encourages merchants to respond promptly with relevant information. Mastercard publishes a dedicated merchant chargeback guide with transaction-specific dispute standards.

Documentation does not guarantee a win. Evidence must address the applicable dispute reason, be submitted according to processor requirements, and satisfy the relevant network rules.

Chargebacks, Cancellations, Refunds, and Duplicate-Credit Risk

Prepayment disputes commonly involve claims that goods were not received, services were not provided, a transaction was canceled, a credit was not processed, the transaction was unauthorized, or the delivered product or service materially differed from what was promised.

Future-delivery merchants remain especially exposed to non-receipt concerns until delivery actually occurs. Payment authorization proves that the issuer approved a transaction request; it does not prove that a future service was completed or merchandise eventually reached the customer.

When a valid cancellation or refund is due, merchants should process it promptly according to their merchant agreement and applicable rules.

Refund posting time should not be presented as one universal number. The time between the merchant initiating a refund and the cardholder seeing the credit can vary by processor, network, issuer, transaction type, and banking process.

Avoid duplicate refunds after a chargeback starts

Before manually refunding a disputed deposit, determine whether a formal chargeback or other dispute credit has already been initiated.

If staff issue a full merchant refund while the same transaction is also being reversed through the dispute process, the customer can potentially receive two credits temporarily or permanently unless the duplicate is corrected.

A practical workflow is:

1. Locate the original transaction.
2. Check processor dispute status.
3. Determine whether funds have already been debited or credited.
4. Follow processor instructions regarding a merchant credit.
5. Record the action in the customer account.
6. Reconcile both the refund and dispute entries.

Finance and support teams should have a shared procedure for this scenario rather than acting independently.

For broader context on how refunds, holds, reserves, and disputes affect merchant funding, see this guide to how merchants get paid after card transactions.

Prepayment Transaction Monitoring, Aging, Reserves, and Processor Reviews

A merchant should not treat a prepayment as fully earned simply because the processor deposited the money in the bank.

Operationally, the business still has an outstanding obligation until it delivers the goods or service or refunds the customer.

A useful management measure is:

Outstanding Prepayment Exposure = Money Collected − Value Already Delivered or Refunded

This is an operational risk measure, not a rule for financial-statement accounting. Revenue recognition, customer deposits, deferred revenue, and other accounting treatment should be determined with qualified accounting professionals.

Aging outstanding deposits

Businesses with meaningful prepayment volume should maintain an aging report.

Order	Deposit Date	Amount	Expected Delivery	Current Status	Days Outstanding
Order A	Date recorded	$1,200	Scheduled date	Materials ordered	12
Order B	Date recorded	$3,500	Scheduled date	In production	37
Order C	Date recorded	$850	Revised date	Customer notified	64

The purpose is not merely bookkeeping. Old undelivered orders are an operational warning.

A growing aging balance may indicate production delays, unrealistic sales promises, supplier problems, refund pressure, or an increasing amount of customer money that remains exposed to disputes.

Useful monitoring metrics include:

• Number of outstanding prepaid orders
• Total dollars collected but not fulfilled
• Age of deposits
• Orders past promised delivery
• Cancellation requests
• Pending refunds
• Chargebacks related to future delivery
• Average days from deposit to fulfillment
• Material changes in preorder volume

Funding holds and rolling reserves

Processors and acquiring banks may use funding holds, delayed settlement, reserves, limits, or additional reviews based on their merchant agreements and risk assessments.

There is no universal rolling-reserve percentage or release period.

A rolling reserve generally means that part of settlement is withheld and released later according to the account terms, assuming applicable obligations are satisfied. Reserves can help protect the acquiring side against future chargebacks or refunds when a merchant’s obligations extend beyond the payment date.

Merchant agreements often contain reserve and risk-review provisions. A useful overview of those clauses appears in this guide to common merchant service contract terms.

Processor review can be triggered by circumstances such as:

• Rapidly increasing prepayment volume
• Large increases in average or maximum ticket
• Longer fulfillment periods
• High outstanding future obligations
• Complaint spikes
• Delayed refunds
• Rising disputes
• Abrupt product changes
• Activity inconsistent with underwriting
• Unexpected seasonal campaigns

Accounting, Settlement, and Deposit Reconciliation

Taking prepayments by credit card creates two records that should never become disconnected: the customer obligation and the payment transaction.

The operational chain should look like this:

Order/Contract → Deposit Transaction → Processor Settlement → Bank Deposit → Customer Deposit/Accounting Record → Final Invoice → Final Payment

A deposit reconciliation record should include:

• Order or contract number
• Customer
• Deposit amount
• Deposit transaction ID
• Transaction date
• Settlement batch
• Settlement date
• Bank deposit reference
• Refunds or adjustments
• Final invoice
• Final payment
• Remaining customer balance

The processor deposit that reaches the bank may not equal one customer’s payment. Batches may contain many sales, refunds, chargebacks, fees, reserves, or other adjustments.

Finance teams therefore need to reconcile in stages.

Daily reconciliation may compare the POS, ecommerce platform, virtual terminal, or invoicing system with processor transactions and batches. Monthly reconciliation can then compare processor statements, bank deposits, refund activity, disputes, customer balances, and accounting records.

Good reconciliation helps answer important questions quickly: Was the deposit actually captured? Which settlement contained it? Was part of the amount refunded? Has the final balance been paid? Is the customer still owed a refund? Is the project still unfulfilled?

It also prevents staff from mistakenly charging a final balance that has already been paid through another channel.

PCI DSS, Payment Data Security, and Secure Final-Balance Processing

Collecting payment before delivery does not reduce or change the fundamental responsibility to protect payment data.

A merchant accepting service deposit payments, custom-order deposits, or preorders should use secure systems appropriate to its payment channels.

Useful controls include:

• Hosted payment pages where appropriate
• Tokenization
• Approved terminals or virtual terminals
• Restricted employee access
• Secure administrative authentication
• Payment-system logging
• Minimal card-data retention
• Secure customer communications
• Documented retention and deletion procedures

PCI SSC explains that organizations should retain cardholder data only when necessary for legitimate business, legal, or regulatory purposes and protect stored data according to PCI DSS. It also makes clear that sensitive authentication data such as the card verification code cannot be retained after authorization.

Merchants can review PCI SSC’s official guidance on card verification code storage.

Email, chat, ordinary documents, spreadsheets, photographs, and scanned forms should not become informal repositories for raw card data.

A customer giving permission to save the CVV does not make storing it permissible under PCI DSS.

For final-balance charges, use the processor’s supported stored-credential or customer-initiated workflow and maintain authorization appropriate to the transaction. If the original agreement permits a later merchant-initiated balance payment, preserve the evidence and follow applicable network indicators and processor procedures.

How to Reduce Avoidable Deposit and Prepayment Risk

The strongest prepayment program combines good underwriting disclosure, customer communication, fulfillment management, and payment operations.

A practical checklist is:

1. Disclose future-delivery activity during underwriting: Explain deposits, preorders, custom work, expected ticket size, and typical fulfillment time.
2. Set realistic delivery dates: Do not sell against production assumptions you cannot reasonably support.
3. Use clear customer agreements: State what is being purchased, what the deposit covers, and what remains due.
4. Keep deposit amounts consistent with legitimate business needs: Avoid sudden unexplained ticket changes.
5. Communicate delays promptly: Do not wait until customers begin filing disputes.
6. Process required refunds promptly: Keep a refund confirmation and transaction reference.
7. Preserve fulfillment evidence: Track production, shipping, service milestones, and customer acceptance.
8. Reconcile prepaid orders regularly: Match customer obligations with processor and bank records.
9. Monitor aging deposits: Escalate orders approaching or exceeding promised delivery.
10. Notify the processor about material business changes: Major preorder campaigns or substantially longer fulfillment periods can change account risk.

Merchants should never attempt to hide future-delivery activity by changing transaction descriptions, using an unrelated merchant account, selecting an inaccurate MCC, misrepresenting goods or services, or artificially dividing payments.

Common deposit and prepayment mistakes

Frequent operational failures include:

• Unclear refund terms
• Taking full payment far in advance without disclosing the model to the processor
• Unrealistic delivery promises
• Missing customer authorization
• Weak card-not-present authentication
• Not documenting customer acceptance
• Failing to communicate delays
• Treating “nonrefundable” as an absolute defense
• Keeping poor fulfillment records
• Using authorization holds as long-term deposits
• Charging final balances without appropriate authorization
• Storing card data insecurely
• Retaining CVV for later charges
• Ignoring aging deposits
• Delaying required refunds
• Artificially splitting transactions
• Processing through the wrong MID or MCC to avoid monitoring

Deposit and prepayment checklist

Area	What to Verify
Processor approved prepayments	Business model was accurately disclosed
Deposit amount clearly disclosed	Customer knows exact amount being charged
Total price documented	Full expected transaction value is recorded where known
Delivery timeline stated	Realistic expected date is provided
Refund/cancellation policy	Terms are visible and applicable
Customer authorization	Consent record is retained
Receipt issued	Deposit/prepayment is clearly identified
Order linked to transaction	Payment can be traced to the obligation
Fulfillment evidence retained	Delivery or service progress can be demonstrated
Final balance procedure	Authorization and stored-credential requirements are addressed
Refunds tracked	Credits are connected to original transactions
Outstanding deposits monitored	Aging and undelivered obligations are reviewed
Settlement reconciled	Processor and bank activity match internal records
PCI controls maintained	Payment data is securely handled

Questions to Ask Your Processor

A processor’s answers should reflect your actual merchant agreement and processing profile rather than generic industry assumptions.

Before building a significant deposit or preorder program, ask:

• Does our merchant account permit our planned deposits and prepayments?
• What future-delivery activity was disclosed during underwriting?
• What average and maximum ticket were approved for the account?
• Is there an approved monthly volume or other account parameter we should monitor?
• Are unusually long fulfillment periods subject to review?
• How does the agreement address reserves or funding holds?
• What happens if our expected delivery timeframe materially increases?
• Which transaction and fulfillment records should we retain?
• Which dispute categories most often affect our business model?
• Does the platform support partial payments and milestone billing correctly?
• How should the final balance be processed?
• Which stored-credential requirements apply?
• Should we notify you before launching a large preorder campaign?
• What supporting documentation may be requested for unusually large deposits?
• How should refunds be handled if a chargeback has already been opened?

Write down the answers and incorporate them into employee procedures.

Payment operations are safer when sales, customer service, fulfillment, finance, and management all follow the same deposit workflow.

Frequently Asked Questions

Conclusion

Taking deposits by credit card can help merchants secure reservations, fund custom work, manage project commitments, accept preorders, and structure payment for goods and services that cannot be delivered immediately.

The payment itself, however, is only the beginning of the obligation.

A well-run deposit program connects the customer’s agreement to the payment authorization, order record, fulfillment process, delivery evidence, final balance, refunds, reconciliation, and dispute documentation. 

Businesses that preserve that chain can answer customer questions faster, reconcile money more accurately, and provide more relevant evidence when disputes occur.

The central principle remains:

The longer the gap between payment and delivery, the more important accurate disclosure, authorization, fulfillment records, refund terms, and processor underwriting become.

Merchants should disclose future-delivery activity accurately, keep transaction volume and ticket sizes aligned with their approved merchant profile, communicate material changes to their processor, and never hide prepayments through false descriptions, inaccurate MCCs, unrelated merchant accounts, or artificial transaction splitting.

Customer-facing documentation should explain what the deposit secures, how much was collected, the expected delivery or completion date, cancellation and refund provisions, and the remaining balance. Internally, merchants should monitor aging prepayments, outstanding obligations, refunds, disputes, fulfillment delays, settlement, and final payments.

Most importantly, documentation should be treated as evidence of what actually happened—not as a guarantee that every dispute will be decided in the merchant’s favor.

Card-network requirements, acquirer policies, merchant agreements, state laws, and industry-specific consumer protections can vary by transaction and jurisdiction. This guide is for general payment, operational, and educational purposes and is not legal, accounting, tax, or individualized compliance advice. 

Merchants with significant advance-payment exposure should confirm their specific processing arrangement with their acquirer or processor and consult qualified legal or accounting professionals where appropriate.