For rental security deposits, choose the provider and rental application together. Stripe and Square both support separating card authorization from capture, but that does not mean every payment link, terminal or rental app exposes the required workflow. A provider choice is incomplete until you know the sales channel, capture deadline and inspection process.
Stripe is worth evaluating for remote deposit requests through an application that supports card holds. Square is worth evaluating when your counter workflow or an existing rental integration fits. Neither is a universal winner, and a saved card is not an indefinite reservation of funds.
Compare the deposit route, not just the payment brand
Keep three operations separate: authorizing a hold, capturing an amount and refunding an already collected payment. A normal payment link may collect money immediately. Buying a link product does not establish support for authorization-only deposits.
Square's delayed-capture documentation gives default completion thresholds of 36 hours for card-present payments and seven days for online card-not-present payments. These are documented API defaults, not a promise that a standard Square checkout link or terminal offers a rental-deposit control.
Stripe's authorization documentation distinguishes card network and transaction type. For standard online cards it lists seven days for customer-initiated transactions; Visa merchant-initiated transactions have a shorter window, stated precisely as four days and eighteen hours. Use the actual authorization's capture deadline rather than promising every renter seven days.
| Purchasing question | Stripe route | Square route |
|---|---|---|
| Does the provider support authorization before capture? | Yes, for eligible methods and integrations | Yes, through supported delayed capture |
| Does my rental app expose this? | Demonstrate request, capture and release | Demonstrate the exact counter or online flow |
| What deadline should staff follow? | Actual authorization deadline and eligibility | Actual delayed-payment deadline and integration behavior |
| Is a reusable checkout link enough proof? | No; verify authorization-only behavior | No; verify delayed-capture behavior |
| Can I switch the payment record between providers? | Treat a new provider as a separate payment arrangement | Do not assume an existing hold transfers |
The practical choice is the working combination of provider, application and rental channel. Check eligibility in your country; do not import another country's fee or hardware assumptions into the decision.
A weekend rental needs more than a Saturday deadline
Imagine equipment handed over on Friday at 16:00 and inspected after return on Monday at 12:00. The required coverage is 68 hours. Add a six-hour operational buffer and the purchasing requirement becomes 74 hours. This is an original hypothetical timetable, not a completed payment test.
Against Square's documented 36-hour card-present default, the hold would reach its threshold on Sunday at 04:00, thirty-two hours before inspection. A seven-day online default would cover this timetable on paper, but the rental integration must actually use that supported online flow. It is not legitimate to label an in-person payment “online” merely to claim a longer window.
For Stripe, compare 74 hours with the real capture deadline for the actual authorization. Do not assume an extended authorization feature is available to every account, card or business. An integration supporting a longer period needs its own eligibility check.
This example is a purchase filter: if the demonstrated route cannot cover return, inspection and the agreed buffer, it fails this rental's requirement even if its processing rate is attractive. For a longer hire, recalculate from the proposed authorization time; do not simply reuse the weekend answer.
Give each supplier the same acceptance sheet
Ask for a demonstration of these outcomes before selecting software. This is a buying protocol, not a report of tests we performed.
| Scenario | Evidence to require |
|---|---|
| Customer completes the deposit request | Authorized amount, customer reference and actual deadline |
| Equipment returns clean | A release action and a clear customer message |
| A justified partial damage claim occurs | Exact amount collected and handling of the remainder |
| Inspection cannot finish before expiry | A documented decision and customer communication route |
| Authorization expires | Clear status; no claim that money remains held |
| Payment or damage claim is disputed | Records linking terms, inspection and payment action |
In Square, confirm what happens at the threshold: its documented default is cancellation, while an integration can have supported completion behavior. For rental security, an automatic full charge must not be mistaken for release. Ask the supplier to explain the customer agreement and exact behavior rather than leaving this as a technical default nobody owns.
A saved card may support a later, separately permitted payment attempt, but it does not preserve the original hold or guarantee collection. Staff still need appropriate terms, evidence and authorization for any claim. Refund processing and an issuer's display of a released hold are also different processes.
When PayRequest is the appropriate Stripe application
PayRequest security deposits use your existing eligible Stripe account to send a deposit request, track authorization, capture an amount owed or release the hold. That provides a specific route to evaluate for short rentals; it does not add a Square connection, a guaranteed damage recovery service or an unlimited hold duration.
Check current deposit allowances as well as timing. Free lists three new requests per calendar month and one open request at a time; Premium lists fifteen new requests and five open. Pending, authorized and partially captured records count as open. Six overlapping rentals therefore exceed Premium's listed open allowance even if the month contains only six new requests. Confirm the right plan for actual concurrency.
Keep rental revenue separate from the refundable damage-security record. If you already have a rental platform with inventory, bookings and a suitable deposit integration, retaining that system may be the better operational choice. PayRequest is a collection layer, not a replacement for fleet or stock management.
Create an account, connect an eligible Stripe account and evaluate one representative short hire against its real inspection deadline. For the earlier mechanism decision, read card holds versus collected refundable deposits.
Editorial note: AI assisted the text and illustration. Provider documentation and PayRequest scope were reviewed on 27 October 2026. The 68-hour timetable, buffer and capacity example are hypothetical, not customer results, provider tests or legal advice.
