Rental management software

The rental ends later. Payment control starts now.

Connect holds, captures, refunds and scheduled charges to the rental lifecycle through one API.

Rental #042: a $500 authorization hold before handover; at return $360 is captured and $140 released
Rental #042: a $500 authorization hold before handover; at return $360 is captured and $140 released

Your platform authorizes $500 at handover and captures $360 at return. The hold sits with the provider on the customer’s card, and the provider releases the unused $140.

Match the action to the rental: capture when it is completed, void when it is cancelled before capture, refund when a refund is needed after capture
Match the action to the rental: capture when it is completed, void when it is cancelled before capture, refund when a refund is needed after capture

Your platform picks the operation for each rental: capture when it is completed, void when it is cancelled before capture, refund after return. Orchestra sends it to the provider.

Funds follow the rental

Model payment state alongside rental state.

Reserve funds before handover, capture when the rental is confirmed, void when it is cancelled, and refund supported amounts after return.

Supported operations depend on the selected provider and payment method.

Authorization control

Hold funds now. Capture only what the rental needs.

Pre-authorize before handover. At return, capture the rental amount and supported adjustments, then release or refund the remainder.

Rental #042: $500 authorized, $320 rental charge plus $40 fuel adjustment captured as $360, $140 released
Rental #042: $500 authorized, $320 rental charge plus $40 fuel adjustment captured as $360, $140 released

At return, your platform captures only what the rental used: a partial capture of $360 from the $500 authorization. The provider releases the other $140.

Rental #042 extended to Jun 22: the $240 weekly charges on Jun 01 and Jun 08 stay charged, and a third $240 weekly charge is scheduled for Jun 15
Rental #042 extended to Jun 22: the $240 weekly charges on Jun 01 and Jun 08 stay charged, and a third $240 weekly charge is scheduled for Jun 15

When a rental is extended, your platform updates the payment contract and Orchestra charges the extra week on schedule. Charges already made stay as they are.

Time-based charges

When the rental changes, the schedule changes with it.

Create future or recurring charges, then update the schedule when a rental is extended, shortened or cancelled.

Scheduling availability depends on provider and payment method support.

Rental developer FAQ

Questions you probably have.

Can we pre-authorize before handover?

Yes. Pre-authorize before handover, then capture the rental amount and supported adjustments at return. Availability depends on provider support and authorization windows.

Can we capture less than the authorized amount?

Supported providers can capture the required amount and release the remainder within their authorization rules.

Can recurring charges follow an extension?

Yes. Create future or recurring charges, then update the schedule when a rental is extended, shortened or cancelled. Scheduling availability depends on provider and payment method support.

Can we void or refund from the same integration?

Yes. Void the authorization when a rental is cancelled, or refund supported amounts after return, through the same API.

Test the full rental payment flow

Validate every payment state before the first live rental.

Use the sandbox to test holds, partial capture, schedule changes and supported refunds.

Free · Up to 100 live requests per month · Unlimited sandbox testing · No credit card required