Why payment apps hold your money, and how to keep it moving.

The job is done. The client paid by card. Then the money sits at pending for a week, or the app asks for three months of bank statements before it will pay you. It happens on every platform with built-in payments, and it happens most to new and small businesses.

This guide covers who actually holds the money, what sets off a hold, how to lower the odds, and what to do when it happens anyway. It is written for solo trades and small crews who take card payments on invoices. One thing up front: Falcon Bill runs payments through Stripe, and Stripe holds money too. Nothing below pretends otherwise.

When an invoicing app says payments are built in, a card processor sits behind it, such as Stripe or Square. The processor moves the money from the card network to your bank. It also carries the loss if a client disputes the charge months later and your account is empty. That is why the processor, not your invoicing app, decides when your money is released.

Three different things can slow your money down:

• The payout schedule. Money from a card payment becomes available after a set time, then goes to your bank on a schedule. This is normal and applies to everyone.
• The first-payout wait. New accounts wait longer for their first payout. Stripe, for example, says it typically schedules a new account's first payout 7 to 14 days after the first successful payment, and that it can take longer depending on industry, country, and risk level.
• A hold or review. The processor pauses payouts, or keeps part of your balance as a reserve, while it checks something. This is the one that hurts, because nobody tells you when it ends.

Processors do not publish their exact rules. The patterns in owner complaints are consistent, though. Holds cluster around these moments:

• The first big payment. An account that has only seen $200 charges suddenly receives $12,000.
• A sudden jump in volume. A busy month that is several times your normal month.
• Payment long before the work. A large prepayment for a job weeks away is the kind of charge that gets disputed if the job never happens.
• A mismatch with your profile. You signed up as a handyman and now charge $20,000 for a roof.
• Unfinished verification. Missing ID, a bank account in another name, or a business address that does not match.
• Early disputes and refunds. A couple of chargebacks on a new account can put the whole account under review.

That is the worst case: the account is closed and the client gets the money back, even though the work was done. It is rare. It is also why the steps below are worth ten minutes of setup.

1. Finish verification before your first invoice. Add your ID, your bank account, and your business details the day you connect payments, not the day a client tries to pay.
2. Describe your business the way you work. Pick the category that matches your trade, and a typical job size that matches your real invoices.
3. Run small charges first. If a big job is coming up on a brand-new account, let a few smaller invoices settle before it, so the account has a history.
4. Keep a paper trail for every job: the approved estimate, photos of the work, and an invoice that matches both. A review asks for exactly these.
5. Keep a second way to get paid for big jobs: bank transfer (ACH), check, or another account you already use.
6. Make your name recognizable. A charge the client does not recognize on their card statement is a charge they dispute.
7. Answer every dispute fast, with the estimate, the photos, and the invoice.

Some owners go further and take every big job by bank transfer or check. That works. Cards still win on speed for small and medium jobs, because the client pays from the link while you are still in the driveway.

1. Find out who is holding it. Open the processor's dashboard, not just your invoicing app. The notice there says what they need.
2. Send exactly what they ask for, the same day: usually ID, bank statements, the invoice, and proof the work happened.
3. Ask for the timeline in writing: when the review ends and when the payout goes out.
4. Do not refund and re-charge the client. It looks like the pattern processors watch for, and it doubles your exposure.
5. If the money was for materials, tell your client and your supplier early. A short heads-up beats a bounced payment.
6. Keep a dated record of every message. If the processor goes quiet, you will need it for a complaint.

Falcon Bill uses Stripe. You connect your own Stripe account in Settings, and when a client pays an invoice by card, the payment goes to that account. Falcon Bill takes no cut and charges nothing per payment; you pay the plan price. The charge on your client's card statement carries the name on your Stripe account, not ours.

Stripe runs the verification and sets the payout schedule. Falcon Bill adds no hold of its own and no delay on top of Stripe's schedule. We also cannot release a payment that Stripe is reviewing, and neither can any other app built on a processor. If Stripe asks for documents, answer Stripe directly.

Two habits in Falcon Bill help if a review ever comes: clients approve estimates from a link, and the approval is timestamped; and you can attach photos of the job to the estimate and the invoice, and they print in the PDF.