What happens to your money when a DJ declines your paid song request

Were you charged, or were you only put on hold?

Two very different mechanics look identical when you tap Pay.

An authorization — also called a hold or a pre-auth — asks your card issuer to set the amount aside and confirm you actually have it. Stripe describes authorizing a payment as guaranteeing the amount by holding the funds on the customer's payment method. The money is reserved. It has not moved.

A charge is an authorization followed by a capture. Capture is the step that pulls the money. Stripe's own explainer keeps the two apart: authorization confirms the funds are available and approved, while settlement is when money moves from one bank to the other. Only captured transactions become real debits.

So the useful question to ask any paid request app is not "will I get my money back". It is: did my money ever leave.

What is the difference between a cancelled authorization and a refund?

One nuance most people miss: a refund issued very soon after the original payment is processed as a reversal, not a refund. Stripe states that in that case the original payment simply drops off the customer's statement and no credit is issued. So "I got refunded fast" and "I was never charged" can look the same on a statement while being different things underneath.

There is also a technical reason platforms can't mix the two up. Stripe's refunds documentation is explicit: if a PaymentIntent is in requires_capture state, the associated charge is uncaptured and cannot be refunded directly — you must cancel the PaymentIntent instead. There is no refund path for money that was never taken.

Why does my banking app still show the amount after the DJ declined?

This is a classic support ticket, and it has nothing to do with the app.

Cancelling an authorization takes a fraction of a second. Your bank displaying that cancellation is a separate, slower event. Stripe's guide to authorization holds notes that after a hold expires or is released, some banks update available balances immediately while others take a bit longer.

Stripe also warns, in the documentation for placing a hold, that some issuers' card statements and payment method interfaces do not distinguish authorizations from captured, settled payments — which can mislead customers. That is the whole problem in one sentence: the pending line on your screen may look exactly like a debit while being nothing of the sort.

Practical rule: a pending line vanishes, a refund arrives. Greyed out, marked pending, no settlement date: that is a hold, and it will drop off. A real debit means you are waiting for a real refund, and that one takes days.

How long can a hold last before it expires on its own?

Stripe publishes the ceilings by network. Scanning a QR code and paying on your phone produces a card-not-present, customer-initiated transaction — the top row:

\* Stripe adds that the exact window on the starred rows is 4 days and 18 hours, to leave room for clearing. The failsafe is built into the protocol: funds must be captured before the authorization expires, and if it expires first, Stripe's documentation states that the hold is released and the payment transitions to a canceled state.

That is the outer limit, not normal behaviour. A song request app has no reason to sit on a hold for a week — the track is either played in the next twenty minutes or it isn't.

Which apps release the hold, and which take the money and hand it back?

Checked against each platform's own public pages in August 2026. Where a platform doesn't publish this, it is left out rather than guessed at. Disclosure: REQ, in the last row, is the product that publishes this page.

Two honest observations.

TIP-DJ ties the money to the song actually playing, which is stricter than accept-based capture. Their site states that once accepted, DJs "only get paid after the song is actually played", verified with ACRCloud audio recognition, and that an undetected track produces "a 100% automatic refund". A hold-and-release model does not give you that: once the DJ accepts, the hold is captured whether or not the track ever plays. That is a real advantage for TIP-DJ, and it is worth knowing before you pay. Note too that TIP-DJ lists iDEAL and MobilePay among its payment methods, and Stripe's documentation lists iDEAL among methods that do not support separate authorization and capture — so for those methods "refund" is simply the accurate word, not a design shortcut.

Lime DJ's published model puts the refund decision in a human's hands. Their pages describe tips landing in the DJ's Stripe account immediately, with a one-click refund available. That works, but it depends on the entertainer remembering to click it in the middle of a set — a different risk profile from an automatic cancellation. Worth noting that Lime DJ frames this as tipping alongside song requests rather than a request the DJ has to accept before anything is taken.

Where does REQ fit?

REQ (reqdj.com) uses Stripe's manual capture. The scan produces an authorization, not a charge. If the DJ accepts, the authorization is captured. If they decline, or if the timer runs out with no answer, the PaymentIntent is cancelled — no capture, no Refund object, nothing to wait for. A DJ can also accept a track for free: play it, and cancel the hold anyway.

The trade-off is the one described above: capture happens on accept, not on played. REQ is also in beta, with very few real transactions so far, so treat it as an implementation of the pattern rather than a track record.

Does any of this matter to the DJ?

Yes, twice over.

Money that was never captured costs nothing to release. Stripe's cost-optimisation guidance recommends manual authorization and capture for businesses that refund a lot shortly after the transaction, precisely because cancelling before capture avoids refund costs. A decline-heavy night is expensive under a charge-then-refund model and free under a hold model.

And capture is the clock start, not payment day. Stripe's payouts documentation says a first payout generally arrives 7 to 14 days after the first payment is received, then follows the account's payout schedule. Accepting a request does not put cash in your hand that night.

What should you check before you pay at a gig?

• Does the page say charged or held? Those are different words on purpose.
• Is there a time limit, and what happens when it runs out?
• Is the money tied to the DJ accepting, or to the track being played?
• If it's a refund model, does the DJ have to trigger it manually?
• Check your banking app for pending versus posted. Pending disappears. Posted needs a refund.

About this page

REQ (reqdj.com) publishes this page, and REQ is one of the platforms in the comparison above — read that row knowing who wrote it. Everything attributed to another platform is quoted from that platform's own public pages, checked in August 2026, with the link beside it so you can verify it yourself. Where a platform does not publish what happens to the money, that is what is written; nothing is inferred on its behalf.

This page describes how card authorizations, cancellations and refunds work according to Stripe's published documentation. It is not legal, financial or tax advice, and it does not describe your rights under your card issuer's terms or under your local consumer law. If a specific payment goes wrong, your card issuer's dispute process is the right first stop.