Your next ride.
A fairer route.
We’re building a simpler way to get around London, with better value in mind, familiar payment choices and drivers who help shape the network.
How a ride
will work.
A familiar journey, with the details that matter along the way.
Choose your journey.
Enter your pickup point and destination, then review the journey details. Start with where you are and where you want to be.
Review the fare and payment option.
See the fare in pounds and choose a supported payment method. The aim is to show relevant charges before you confirm.
Request your ride.
The service would look for an available driver. A request and a confirmed driver are different stages; requesting does not guarantee a match or pickup time.
Meet your driver and travel.
The intended confirmation would include driver, vehicle and pickup information to review before getting in. Then it’s time for your journey.
Finish with a clear trip record.
After the journey, see a summary of the trip and payment, with the information you need to understand the charge or raise a question.
Familiar payments.
Your choice.
Card, Apple Pay or Google Pay.
The aim is a familiar checkout in pounds. You wouldn’t need to buy crypto, connect a wallet or manage the technology behind the payment.
Supported stablecoins.
For riders who already use them, we’re developing a stablecoin payment option on Solana, initially around USDC. You would need a supported, compatible wallet and network.
Follow the money.
How we’re designing the journey from your payment to the driver’s payout.
- Rider
- Payment processor
- USDC funding
- Solana transfer
- Driver earnings
- Settlement provider
- Bank account
View all steps
These roles explain the intended flow. One provider could perform several roles; the sequence does not define who would hold funds.
Rider payment · Card, Apple Pay or Google Pay
- You pay in pounds
Choose your ride and a familiar payment method. No crypto wallet needed.
More about this step
Card, Apple Pay and Google Pay are the familiar payment options we’re developing. Conversion would happen behind the scenes; you wouldn’t place a cryptocurrency order.
- Payment processor
A payment processor handles the card payment and its approval.
More about this step
Authorisation can reserve funds on a card. Capturing the payment and those funds becoming available are separate stages. JURNE’s exact capture schedule is still being developed.
- USDC funding
Behind the scenes, a provider would arrange USDC for the driver-earnings flow.
More about this step
This requires available funds or separately arranged prefunded liquidity. A card approval does not instantly become settled stablecoins. The funding arrangements are still being developed.
- USDC moves on Solana
Solana is the chosen network for transferring the stablecoin funds.
More about this step
Solana supplies the transfer network. It does not process the card charge, convert currencies or send pounds to a bank account. Transfers may be aggregated rather than made once for every ride.
- Driver earnings build
After completed rides, the driver’s share is recorded, with pending and available earnings kept separate.
More about this step
The driver’s earnings follow the fare allocation and applicable deductions. Drivers would see USDC and an indicative GBP value, accumulating earnings before requesting a withdrawal. Funds can be transferred in batches while earnings are recorded per ride. An earnings record does not automatically mean a personal on-chain wallet.
Rider payment · USDC on Solana
- Your supported wallet
See the fare in pounds and the USDC amount for the applicable quote.
More about this step
The proposed USDC option requires a compatible supported wallet and the Solana network. USDC is dollar-linked; it is not worth a fixed pound. Supported wallet requirements and fees are being developed.
- USDC payment on Solana
Pay with supported USDC using the chosen network.
More about this step
This route uses USDC directly, without a card processor or an unnecessary conversion into pounds and back. Applicable checks, fees, accounting and provider involvement still matter.
- Payment recognised
The payment is recognised separately from completion of the ride.
More about this step
A network confirmation concerns the transfer. It does not mean a driver has been matched, the journey has finished or the driver’s earnings are available to withdraw.
- Driver earnings recorded
After the completed ride, the driver’s resulting earnings enter the earnings record.
More about this step
The driver’s earnings follow the fare allocation and applicable deductions. Drivers would see USDC and an indicative GBP value, accumulating earnings before requesting a withdrawal. Funds can be transferred in batches while earnings are recorded per ride. An earnings record does not automatically mean a personal on-chain wallet.
Driver payout · Bank account
- Your earnings
Completed trips add to your earnings record. Only available funds can be requested for withdrawal.
More about this step
USDC is designed to track the US dollar, not the pound. You’d see an indicative GBP equivalent, which changes with exchange rates and conversion costs. Pending earnings are still being processed; available earnings are eligible for a withdrawal request.
- You request a cash-out
Choose how much of your available earnings to withdraw.
More about this step
The driver initiates the request. Daily requests are the intended common pattern, subject to available funds and checks. That does not guarantee daily bank receipt or an automatic payment after every trip.
- Review the payout
See the conversion rate, provider fees and the amount due to reach your bank before confirming.
More about this step
A quote should show each part of the payout clearly. Any expected arrival is an estimate, subject to checks, the provider and bank processing.
- USDC amount
- Conversion rate
- Fees
- Net GBP payment
- Expected arrival
- Settlement provider
After approval, the provider would convert USDC into pounds and arrange the bank payment.
More about this step
The settlement provider is the company handling conversion and bank payout. Provider arrangements are still being developed. One company may perform several of the roles shown here.
- Your bank account
The payout reaches your bank through the banking network.
More about this step
A request is not a completed payment. Requested, processing and completed receipt need distinct records. Timing depends on available funds, required checks, the provider and your bank.
Driver payout · Crypto wallet
- Available USDC earnings
Completed trips add to your earnings record. Only available funds can be requested for withdrawal.
More about this step
USDC is designed to track the US dollar, not the pound. You’d see an indicative GBP equivalent, which changes with exchange rates and conversion costs. Pending earnings are still being processed; available earnings are eligible for a withdrawal request.
- Withdrawal request
Choose how much of your available earnings to withdraw.
More about this step
The driver initiates the request. Daily requests are the intended common pattern, subject to available funds and checks. A request is separate from a completed wallet transfer, and earnings would not transfer automatically after every trip.
- Check wallet and fees
Check the compatible wallet, supported network and any transfer fee.
More about this step
The destination needs to support USDC on Solana. Service or transfer fees may apply. Checking an address does not guarantee recovery from a mistaken transfer; transfers should not be assumed reversible.
- USDC transfer on Solana
The available funds would move as USDC on the supported network.
More about this step
This route bypasses conversion into pounds and the banking network. It still requires an eligible withdrawal request, any applicable checks and fee review.
- Your crypto wallet
USDC arrives at the compatible wallet destination.
More about this step
A withdrawal request and a completed transfer are different stages. This option would keep your withdrawal in USDC; it would not create a fixed GBP balance.
A fairer route.
London first.
A leaner operating model is our route towards better-value rides. It’s an objective, not a guaranteed saving. Driver participation would give drivers a stronger voice in how the network develops.
We’re planning a small, controlled London start, with space to learn from real journeys before expanding.
Solana is the network we’ve chosen for the payment infrastructure. For card-paying riders, it stays behind the scenes.
Useful rider questions.
Do I need crypto to use JURNE?
No. We’re designing card, Apple Pay and Google Pay options that don’t require a crypto wallet or a separate crypto purchase. The stablecoin option would be a choice.
How will I see what a ride costs?
The intended booking flow shows the fare in pounds and relevant charges before confirmation. The detailed pricing and fare-change terms are still being developed.
Where in London will JURNE start?
A small, controlled initial area. Specific coverage has not been decided; the intention is to make the available area clear before you request a ride.
What if I need to cancel or a payment needs correcting?
Cancellation and payment-correction policies are being developed. The goal is clear terms before booking and a route to raise a problem against your trip record.
How would I get help with a ride?
We’re designing a way to contact support about a particular journey. The support arrangements are still being developed, including how issues are reviewed and followed up.
London, let’s take a fairer route.
Every ride has two sides. Explore the earnings, cash-out choices and driver voice we’re working towards.
Thinking of driving with JURNE?