Funds and payouts

From rent request to confirmed settlement.

Use precise event language to understand what the tenant, operator and recipient can rely on at each stage.

Explore the workflow.

Use these paths to compare the product, operating model and next decision.

1. Request

An obligation is recorded.

The RentLink identifies the tenant, amount, due date and relevant options.

2. Payment

A confirmed event changes status.

Requested, pending, paid and failed describe different events.

3. Payout

Allocation and settlement stay distinct.

Agreed routing does not by itself confirm funds arrived.

Explore payouts

A request is not a payment.

Creating or sending a RentLink records what is due and gives the tenant a supported payment route. It does not mean the tenant has approved, started or completed payment.

If an event is still awaiting a next step, the interface should name that step where known rather than using a vague completed label.

Protection has its own conditions.

An overdue status does not automatically establish an eligible guarantor or rent-guarantee payout. The contract can require evidence, review, limits and dispute handling.

Current eligible timing statements of due date +30 days or +1 day apply to the relevant proposition and conditions. They should not be presented as universal bank-arrival promises.

Questions operators ask.

Does allocated mean settled?

No. Allocation shows the agreed distribution; settlement is a later confirmed event.

Does paid mean the operator can withdraw funds?

Not necessarily. Availability depends on processing, routing and the agreed payout setup.

Can a payment be partially refunded?

If only part is confirmed refunded, the status should say partially refunded rather than refunded.

Who can receive a payout?

Verified landlords, operators and approved service providers according to the agreed setup.

Bring CasaPay into your operation.

Start with the connected workflow your portfolio needs, then confirm market availability and terms during onboarding.