The current MVP simulates payment states for workflow testing. JOR does not currently operate a regulated escrow account and must not accept production funds until its payment-provider agreement and webhook controls are live.
Planned payment flow
- Fleet owner reviews job price, JOR fee and applicable tax before payment
- The contracted payment provider processes the transaction
- Payment status is confirmed by signed provider notification
- Completion and dispute state determine settlement eligibility
- Driver payout and invoice references are recorded
Price and fee disclosure
The final payable amount, platform fee, taxes, cancellation terms and driver payout must be shown before confirmation. Pricing displayed during the pilot is subject to the signed pilot agreement.
Cancellations, refunds and disputes
Refund eligibility depends on job status, evidence and the applicable policy accepted at booking. JOR should provide a reasoned outcome and preserve an audit trail for disputed transactions.
Payment security
- Payment credentials stay with the authorised provider
- Provider webhooks require signature verification and replay protection
- Settlement actions require restricted admin permissions
- Reconciliation must detect duplicate, missing or inconsistent transactions
No banking or credit promise
JOR does not offer a deposit account, loan, investment or guaranteed return. Any future credit, insurance or financial product will require separate terms and an appropriately authorised partner.