Checkout & Delivery

Factory options, delivery policy, test drives, and the server-authoritative purchase pipeline.

Resource
drs_vehicleshop
Version
v1.0.1-drs.8
Updated
Aug 30, 2026
Resource GitHub
Guide navigationCheckout & Delivery
Sections
01 / FACTORY CHECKOUT & DELIVERY

Factory checkout & delivery

Configure factory checkout

Checkout entries use stable option ids. The server resolves their GTA indexes, prices, availability, plate restrictions, and delivery support when creating a quote. Prefixes accept one to three uppercase letters or numbers and apply only to road vehicles.

config.lualua
Config.PaymentAccount = 'cash'
Config.DeliverPurchasedVehicles = true
Config.Checkout.quoteLifetime = 30000
Config.Checkout.platePrefix.enabled = true

Align delivery and garage identifiers

Default car, boat, and air garage ids must exist in the selected garage configuration. Drive-away is removed when delivery is disabled or a shop lacks a spawn point; garage delivery remains the safe fallback. Keep the acknowledgement and handoff timeouts long enough for the configured fade and streaming transition.

02 / TEST DRIVES

Test drives

Tune server-managed test drives

Review test-drive duration, geofence, handoff timeout, return fallback, and cleanup settings. The server creates, tracks, expires, and removes test vehicles; clients cannot grant keys or turn a test entity into an owned purchase.

03 / PURCHASE ARCHITECTURE

Purchase architecture

The purchase pipeline keeps authority on the server and makes every external side effect recoverable or reviewable.

Quote authority

The client requests a quote with configured option ids, shop id, model, and bounded prefix. The server resolves all prices, access, plate indexes, garage, spawn, and delivery policy, then rejects stale or changed quotes at purchase time.

Durable personal delivery

Plate reservation and order creation share a transaction. Payment, player_vehicles ownership, server entity creation, garage registration, persistence, keys, and the one-use client acknowledgement advance the journal through explicit states.

Safe failure convergence

Blocked spawns, failed persistence, failed keys, disconnects, resource stops, and acknowledgement timeouts converge to a stored owned vehicle. Ambiguous payment or refund exports become review states rather than automatic duplicate credits.

04 / VALIDATION & DELIVERY HELP

Validation & delivery help

Validate every dealership path

Open each enabled road, marine, and aviation shop. Test category access, search, one successful and one rejected quote, test-drive expiry, drive-away delivery, garage delivery, keys, ownership, storage, and retrieval.

A purchase is stored instead of delivered

Verify the selected garage is started and compatible, its identifier exists, the delivery spawn is clear, and persistence and key providers are healthy. Stored state is the intended safe result when delivery cannot be proven.