Confirm the recipient
Search by username or email, then verify the account shown before sending. A transfer is for a system account, not an arbitrary email address that has never registered.
RideKip
Booking transfers between drivers
Send an order to a known account without losing the record of what happened next. Acceptance, service progress and transfer information fees stay distinct.
Wait for acceptance
The recipient opens the transfer and confirms whether to accept it. Sending is not the same as acceptance. Check the transfer state rather than assuming the job is already taken.
Keep a record on both sides
The original driver retains the linked transfer record and can inspect the recipient's progress, such as in progress or completed. The service is delivered by the accepting driver.
Record the right income
If the transferred fare is 100 and the sender's information fee is 10, do not count the full 100 as the sender's income. Identify the transfer fee and keep its payment or collection status separate.
Illustrative example
A 100 fare with a 10 transfer fee
- Sender
- Confirms the recipient and records a 10 transfer fee
- Recipient
- Reviews the order and confirms acceptance
- Service
- Recipient's progress remains visible in the transfer record
- Money
- The sender tracks the transfer fee, not the full transferred fare
The example describes transfer accounting, not an automatic collection of the fee.
Before your first trip
Can I transfer on both iOS and Web?
Yes. The same account-confirmation and acceptance workflow applies on both surfaces.
Is an accepted transfer automatically completed and paid?
No. Acceptance, service completion and money settlement are separate states.
Keep the next trip in focus.
Start with your bookings and build a clearer record of your daily work.