From “can you deliver?” to proof it arrived.
One flow, two ways to pay. Every delivery is priced server-side, reviewed by Couranr, and captured only after Couranr confirms — an estimate is never an instant confirmation.
The order things happen in
This sequence is fixed. Couranr cannot capture a payment before it has confirmed the delivery, and it does not dispatch one it has not confirmed.
Quote
The delivery is described and priced server-side, in exact cents. The quote is accepted before anything else happens.
Payment authorized
A payment method is confirmed and authorized. The money is held, not taken — nothing is captured at this point.
Marked ready
You prepare the order and mark it ready. Couranr does not dispatch against an order that is not.
Couranr review
Couranr Operations reads the request. This is a person, not a rule engine, and it is why an estimate is never an instant confirmation.
Couranr confirmation
Couranr confirms the schedule and the vehicle. Only now is payment captured.
Couranr-managed dispatch
The delivery is created and assigned to a Couranr-managed driver. There is no marketplace, no bidding and no self-selection.
Two ways to pay, one delivery
Chosen per delivery, not per account. Steps 3 to 6 above are identical either way — only who authorizes changes.
Your business pays
- You create the delivery request in your Couranr workspace.
- You confirm a payment method and it is authorized for the server-computed quote.
- Capture happens after Couranr confirms — you see authorization, confirmation and capture, in that order.
- Authorization, confirmation and capture are three events you can see, in that order.
Your customer pays
- You create the request and send your customer a secure payment link.
- Your customer authorizes payment on that link — no Couranr account required.
- Capture happens after Couranr confirms here too. You see the authorization status without ever handling their card details.
- The delivery proceeds identically from there.

An estimate is never an instant confirmation
A price appears immediately because it is computed, not negotiated. A confirmation appears when Couranr has read the request and committed a schedule and a vehicle to it. Those are different events, and Couranr will not blur them to look faster.
If Couranr cannot confirm, the authorization is released and you are not charged. See the full pricing schedule →
What gets recorded, and what never does
Proof requirements are fixed by handoff type before the driver arrives — chosen when the delivery is created, not improvised at the door. Two things are never collected, on any delivery: face photos and ID-document photos.
At pickup, every time
- Merchant pickup PIN
- Package count
- Shipment photo
- Condition photo
- Timestamp and location
- The actual vehicle
A material discrepancy pauses the pickup and may require a requote — Couranr does not carry something it cannot describe.
Direct handoff
- Recipient PIN
- First name
- Timestamp
- Location
Signature
- Signature
- Signer name
- Timestamp
- Location
Leave at door
- Merchant permission
- Customer authorization
- A safe location
- Weather suitability
- Photo, timestamp and location
When something changes mid-delivery
- Couranr Support
- In-app support with a 15-minute response target during operating hours.
- Live tracking
- You and your customer follow the delivery from a secure link scoped to that one delivery. All time windows and ETAs are estimates.
- Changes go through Couranr
- A change to a confirmed delivery is a Couranr decision, not a driver's judgment call at the door.