You are acting as the example merchant's own server: its key signs these captures, not Abeyo's. A merchant can capture only what a slip still holds, only before its valid-until date, and only to its payout address.
| Reference | Customer | Held | Captured | Returned | Valid until (UTC) | State |
|---|---|---|---|---|---|---|
| PROOF-ORDER-6151G | 0xdd5c…f691 | 0.00 | 0.00 | 85.00 | 9 Oct, 13:51 | Void |
| PROOF-ORDER-5XP50 | 0xbCdB…80cF | 0.00 | 0.00 | 85.00 | 9 Oct, 13:48 | Void |
| PROOF-ORDER-5UH35 | 0x3147…8C88 | 0.00 | 0.00 | 85.00 | 9 Oct, 13:46 | Void |
| EXAMPLE-ORDER-02 | 0xF950…640a | 0.00 | 0.00 | 85.00 | 8 Oct, 20:25 | Void |
| EXAMPLE-ORDER-01 | 0x5875…06cc | 0.00 | 79.12 | 5.88 | 8 Oct, 20:25 | Captured, rest returned |
This is one of the live examples on the home page, so the demo keeps it as it is. Open your own hold at the checkout to try this. Open a hold at the checkout, then come back here as its merchant.
Every vault event for Larder Grocery Delivery (example) also arrives as a Stripe-shaped webhook, signed in Stripe's scheme and checked on arrival. The same history is readable at /api/v1/events and /api/v1/payment_intents.
No webhooks yet. The next capture, void or new hold for this merchant sends one.