Built on 5 PayPal APIsSee the integrations

AI reordering for café suppliers

An agent proposes each café's next order, the café approves it, and PayPal keeps a fingerprint of that approval.

Open the live demo See the receipt

Café reorder · todayPayPal Vault · sandbox

Orders

CBCoffee beans 40lb bag$84.00Awaiting café approval

OMOat milk case (12)$48.00Verified with PayPal

SUSugar 10lb bag$24.00Verified with PayPal

CSCoffee beans 5lb bag$37.00Disputed · contest drafted

OMOat milk case (12)$72.00Rejected by the café

Check stock and reorder whatever is running low

Checked stock, today's budget and market prices (Channel3)

Coffee beans 40lb bag is down to 1, below its reorder point of 2. Two bags bring it back to 3 for $84.00.5 tool calls

Café approvesReject

The RelayPay console for café orders

Pick a charged order to see the café's sealed approval, its SHA-256 fingerprint and the checks RelayPay runs against PayPal's own record.

Open the receipts

Receipts / All

CBCoffee beans 40lb bag2 × $42.00 · $84.00Approved2m
OMOat milk case (12)2 × $24.00 · $48.00Approved9m
SUSugar 10lb bag2 × $12.00 · $24.00Verified1h
CSCoffee beans 5lb bag2 × $18.50 · $37.00Disputed2h
OMOat milk case (12)5 × $24.00 · $120.00Verified3h
CBCoffee beans 40lb bag3 × $42.00 · $126.00Verified1d
SUSugar 10lb bag3 × $12.00 · $36.00Verified1d
OMOat milk case (12)4 × $24.00 · $96.00Verified2d
CSCoffee beans 5lb bag1 × $18.50 · $18.50Verified3d

Approval receipt · sealed 5 Nov, 17:19

Coffee beans 40lb bag · 2 × $42.00

Approved by cafe-owner before payment, after the agent's proposal and 5 tool calls. Policy v3 checks passed.

Fingerprint 49701d33ecbe…630dd1c sent to PayPal as the order's custom_id.

PayPal captured $84.00 with the café's saved Vault payment method, no redirect.

Any edit to this receipt changes its fingerprint, so it no longer matches PayPal's copy.

Public check: anyone holding the receipt can recompute the fingerprint and compare it with PayPal's record.

Approval receipts sealed into each PayPal order

When the café approves, RelayPay seals what, how much, who and when into a receipt. Its SHA-256 fingerprint rides on the PayPal order as custom_id.

Orders over $100 need the café's extra tick
One edit breaks the fingerprint

Check a receipt

TSorders/create.ts Captured

const hash = hashReceipt(receipt);
const order = await createOrder({
  amount: "84.00",
  custom_id: hash,
  vault_id: cafe.vaultId,
});
// PayPal keeps custom_id
await capture(order.id);

The receipt's fingerprint, stored by PayPal.

Why it holds up

Dispute tools argue after the fact. RelayPay seals the café's approval before the purchase, and PayPal keeps an independent copy of its fingerprint.

PayPal disputes answered from the receipt. You decide what is sent.

New cases arrive by signed webhook, or paste any PayPal dispute ID.

Drafts the PayPal dispute reply

It reads the case and the café's receipt, then writes the response.

Dispute agent

Online

Buyer says they didn't authorize this payment.

The café approved this order before payment, and its fingerprint matches PayPal's capture record. I recommend contesting. Approval receipt PayPal capture

Approve the response.

Approve, refund or send evidence

Checks 4 facts with PayPal

Receipt, fingerprint, amount and capture, re-read live.

Verify with PayPal

4 of 4

Receipt unchanged
custom_id matches
Amount is $37.00
Capture completed

Attaches the receipt as a PDF

Receipt, timeline and PayPal IDs in one file.

4 parts added

Evidence packet.pdfPDF
Approval receiptReceipt
Capture recordPayPal
TimelineLog

Works with PayPal and your tools

RelayPay calls Vault, Orders, Payments, Disputes and Webhooks from its own server, plus Transaction Search for reconciliation when it is enabled. The agents never hold credentials or move money.

Channel3 checks market prices, owner alerts arrive by email, Discord, Slack or ntfy, AG Grid draws the tables.