JaminanPasporPayPal hold $100.00

The deposit that remembers the dent was already there.

At a Bali scooter counter the jaminan, the deposit, is often your passport, and at return whoever holds it wins the argument. Jaminan holds the deposit on PayPal instead: when the shop points at a mark, it cannot be charged if the confirmed pickup baseline already lists that damage there or, once a model passes the bench, the vision model finds it in the pickup photos, and the deposit pays only the lines the renter accepts.

Recorded on the PayPal sandbox · claim answers scripted until the vision bench

  1. authorize $115.00 · fee + deposit, one renter approval
  2. capture the $15.00 fee · final_capture=false
  3. capture accepted lines · final_capture=true releases the rest · or void

PayPal's read‑back after the fee capture and after the final capture or void · all three runs ↓

Recorded replay. PayPal sandbox calls at their recorded speed; the two claim answers are scripted until the vision bench. All three runs ↓

Sewa · Rental
R-JUDGE-9001
Demo scooter 1
B 0000 JMN · 1 day
Rental fee$15.00 captured from the hold · final_capture=false · PayPal: PARTIALLY_CAPTURED
Mirror housing — crack$18.00 new since pickup — priced from the tariff
Side panel — dent— visible at pickup — cannot be charged
Jaminan kerusakan · Damage deposit
$100.00
held on PayPal — not charged$18.00 captured
$82.00 released
$100.00 released
$18.00 invoiced
DilepasReleasedPayPal: CAPTURED
  1. Recorded run R-JUDGE-9001, PayPal sandbox: one capture of $18.00 with final_capture=true → read-back CAPTURED; the other $82.00 released by the same call. Evidence
243tests passing, 8 of them against the PayPal sandbox APIevidence/test-run.txt
18of 18 live end-to-end checks passed on the deployed app on 2026-10-24, as two phones at 375 pxevidence/e2e-live.txt
19PayPal REST endpoints in a hand-written client: orders, payments, vault, invoicing, webhooks, reportingevidence/README.md
23,040input combinations swept through the claim rule: a result is chargeable only when the benchmarked model answered, every answer says new since pickup, and the tariff has a price (this tests the rule, not image recognition)tests/test_invariants.py

No. 1 Aturan · the rule

The owner points. The shared baseline answers.

At pickup, renter and shop walk eight angles round the scooter and confirm the photos together. At return the shop taps each mark it wants to charge and names it from the published tariff. A vision model answers narrow questions about the photos both sides confirmed. It never sets a price.

  1. 1Toko menunjukThe shop taps a mark and picks its part and kind from the tariff list.mirror_housing · crack · $18.00
  2. 2Foto awal menjawabThe model only answers what the shared pickup photos can show.visible_at_pickup · pickup_comparable · mark_at_return
  3. 3Penyewa memutuskanThe renter accepts or contests each line. The hold pays only what they accept.capture · final_capture=true

What the shared baseline can't show, nobody can charge.

Code turns the model's answers into one of these lines, in this order. Only the last kind of line has a price, and only from the shop's published tariff.

Who it is for: family-run scooter counters in Jakarta and Bali, and the tourists and locals who rent from them and today leave a passport or KTP as the deposit.

The shared baseline shows…Price
The mark was already visible at pickup—visible at pickup — cannot be charged
The pickup photo can't show that spot (glare, blur)—the shared baseline can't show this — cannot be charged
There is no mark there at return—no mark found at return — cannot be charged
It is not the kind of damage the shop named—doesn't look like that — can't be paid from the hold
It is clearly new since pickuptariffnew — priced from tariff (mirror housing crack: $18.00)

No. 1½ Coba · your turn

Tap a claim. See what the model said.

AI-generated test images (not photographs) A pickup image made by qwen-image-2.0 and a return image edited from it by wan2.6-image, which removed both mirrors. The builder pointed two claims; a script running the same crop, model-call and decision steps as the app's claim path asked the vision model three times each. One angle, no rental, no close-ups.

The model read both claims wrong, in all 3 calls each.

AI-generated test images (not photographs): the pickup image of a white scooter, front-left view, both mirrors on, a grey scuff on the front fairing
At pickup · AI-generated test images (not photographs)
AI-generated test images (not photographs): the return image of a white scooter, front-left view, edited so both rear-view mirrors are gone
At return · AI-generated test images (not photographs)

The model read both claims wrong, in all 3 calls each. Tap a box on the return image for its recorded answer.

These are recorded answers, not a benchmark and not real-world evidence. No rental or payment was involved. Had this model been pinned without the bench, the rules would have priced C1 at the tariff's dent price, $45.00, for a scuff that was there at pickup. A false “new” on an old mark is the error the benchmark has to rule out before any model is pinned, so no model can price a line until it passes the bench on real photos.

No. 2 Uang · the money

One authorization carries the whole rental.

One renter approval authorizes the fee and the deposit together ($115.00) and saves the wallet for later fines. Everything after happens on that one authorization, and every stamp waits for PayPal's own read-back.

Rentals longer than three days are reauthorized once on day 4, inside PayPal's day 4 to 29 window. On the sandbox, reauthorize answered 201 on two holds, one with its fee already captured, and refused a second reauthorize of an already reauthorized hold with 422 REAUTHORIZATION_TOO_SOON. If PayPal refuses one, the service authorizes again on the saved wallet and voids the old hold. Inside the app, the day-4 trigger rule and this fallback are unit-tested, including through cron_daily(); the scheduled daily job has not yet run on a rental, so the recorded sandbox calls are the live proof. evidence/paypal-reauthorize.jsonl

  1. 16:29:30POSTauthorize fee + deposit · $115.00/v2/checkout/orders201 COMPLETEDf129062b61ea42,487
  2. 16:29:32POSTcapture the fee · $15.00 · final_capture=false/v2/payments/authorizations/{id}/capture201 COMPLETEDf666818a6fc152,079
  3. 16:29:33POSTwrite the handover/v2/checkout/orders/{id}/track201 COMPLETEDf5985964041c71,470
  4. 16:29:34GETread back/v2/payments/authorizations/{id}200 PARTIALLY_CAPTUREDf851387639df7860
  5. 16:29:37POSTcapture accepted line · $18.00 · final_capture=true/v2/payments/authorizations/{id}/capture201 COMPLETEDf92235735fe352,283
  6. 16:29:37GETread back/v2/payments/authorizations/{id}200 CAPTUREDf2917404f2365484
  7. 16:29:38POSTcapture again · $1.00 · final_capture=false/v2/payments/authorizations/{id}/capture422 AUTHORIZATION_ALREADY_CAPTUREDf5799404eea63671
  8. 16:29:38GETread back/v2/payments/authorizations/{id}200 CAPTUREDf937455696d61489

Recorded 2026-10-14 16:29 UTC on the PayPal sandbox by scripts/record_paypal_evidence.py: three rentals, each a merchant-initiated authorization on a saved sandbox wallet. The claim answers in these runs are scripted; the PayPal side is real. evidence/paypal-sandbox-run.json

No. 3 Aplikasi · the live app

Two phones. One rental.

The same flow runs at jaminan.edycu.dev/app. /judge mints a fresh sandbox rental on a saved sandbox wallet, with no login, and one tap releases it; priced claims wait for the vision bench. Screenshots of the live app; each names its rental.

Jaminan — the judge page with the hold live: $100.00 held under DITAHAN · HELD, and PayPal's read-back PARTIALLY_CAPTURED with the authorization id Jaminan — the same rental one tap later: DILEPAS · RELEASED, and PayPal's read-back VOIDED
/judge, rental R-JUDGE-13 (2026-10-14 17:11 UTC). The fee is captured from the hold and PayPal reads back PARTIALLY_CAPTURED; one tap voids the hold and the green stamp fires on PayPal's read-back, VOIDED.
Jaminan — the shop phone in Bahasa: a new rental stub with $100.00 to be held on PayPal, not charged
Shop phone, Bahasa. A new stub before the renter approves (live e2e run, rental R-1014-2E81996C; the renter's QR is cropped out: it carries their key).
Jaminan — the renter's receipt in English: the released stamp, PayPal says VOIDED, with the authorization, fee capture and handover ids
Renter phone, English. The receipt with PayPal's ids (R-JUDGE-13).
Jaminan — every PayPal call for the rental with HTTP status and PayPal debug ids, the live read-back VOIDED, and recent webhooks with their verification result
Swipe the screenshot sideways to read the whole log. Every PayPal call, live. /integrations/verify lists each call with its debug id, re-asks PayPal for the authorization, and shows recent webhooks with the result of PayPal's signature check.

No. 4 Cara kerja · how it is built

Arithmetic says no first. PayPal says yes last.

Bad frames never reach the model

Blur and glare are rejected by arithmetic on a fixed 1280 px frame, before any model call.

numpy + Pillow · Laplacian variance · clipped highlights

The model answers, never prices

Per tap: is there a mark now, is it the kind named, was it visible at pickup, can the pickup photo show that spot.

Qwen VL · JSON schema · 0–1000 boxes

Code decides

The answers become a line in a fixed order. A model the benchmark has not pinned can never produce a chargeable line.

rules.py · decide_claim

The handover is written to PayPal

PayPal's shipment tracking on the fee capture is the handover record: its tracking number carries the first 8 hex characters of the confirmed baseline's SHA-256.

orders/{id}/track

Fines later, on the saved wallet

A traffic-camera ticket whose plate and time match the rental is charged to the saved wallet, capped by the ceiling for that violation; the renter has 72 hours to contest. Offline-tested only: the recorded runs prove a merchant-initiated authorize on a saved wallet, not a fine.

merchant-initiated · vault_id

No. 5 Batas · honest by design

What it does not do yet.

Sandbox only. Nothing here has moved live money; live vault and merchant-initiated eligibility are unverified.— README · Honest limits 1
Wallet path only. The card-path authorize answered 422 on 2026-10-14 without a stated reason (PayPal's response gave none; we believe advanced card processing is not enabled for this Indonesia-region sandbox merchant), so cards are out of scope.— README · Honest limits 3
Non-return is out of scope. Jaminan covers damage and fines, not a scooter that never comes back.— README · Honest limits 4
No vision accuracy claim yet. Until the benchmark runs, no finding from a non-benchmarked model is chargeable.— README · Honest limits 5

Fair questions a judge would ask.

What does the AI decide?

Nothing about money. For each mark the shop taps, the vision model answers narrow questions about the shared pickup photos: is there a mark now, is it the kind named, was it visible at pickup, can the pickup photo show that spot. Code turns the answers into “cannot be charged” or a line priced from the tariff.

Has the vision model been benchmarked?

Not yet: the benchmark on the staged scooter set has not run. A partial check on 48 public Wikimedia Commons photos, each used as both pickup and return, with labels drawn by the builder's agent (Claude), not an independent annotator, failed: qwen3-vl-plus called an old mark new in 71 of 105 answers and a clean spot new in 66 of 66, against a bar of 0. One photo failed the blur gate and was not scored. It does not test new damage between two photos or real shop conditions (evidence/public-photo-bench). Until a model is pinned by it, every live claim ends “comparison unavailable — nothing charged from the hold”, which is why the recorded settlements on this page use scripted answers. The “Tap a claim” section shows the model's recorded answers on AI-generated test images (not photographs); it read both claims wrong, which is a reason for the bench, not a measurement. No benchmark accuracy number appears anywhere; the only real-photo numbers are this failed partial check.

What stops the shop from charging an old dent?

Two locks. The pickup baseline both sides confirmed: a mark it shows, or a spot it cannot show, cannot be charged. And the renter: the hold pays only the lines they accept.

And if the renter contests everything?

Every contested line leaves as an itemized PayPal invoice at the published tariff price, with a link to the evidence pack, and the hold is released. That is the trade: the hold never pays a line the renter did not accept, and the shop keeps a priced claim on photos both sides confirmed.

Can an AI agent book a scooter?

Yes, through four MCP tools: list_vehicles, quote_rental, start_rental and get_rental. The agent can price a rental and ask for it, but start_rental returns a PayPal link that only the renter can approve. No tool approves, answers a damage line, captures, voids or refunds. Claude Code and Codex each booked one on the sandbox on 2026-10-24 and read back the authorization; the transcripts are in evidence/mcp.

What happens when I open /judge?

It mints a fresh sandbox rental on a saved sandbox wallet, with no login, and opens it on the shop's phone; today it can only release the hold (read back VOIDED). A full-path button runs PayPal's real approval page with a sandbox buyer.