Abeyo

Merchant desk

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.

ReferenceCustomerHeldCapturedReturnedValid until (UTC)State
EXAMPLE-TAB-TMJJBJ0xaf9e…57a6100.00 eUSD0.000.0014 Oct, 13:59Held
EXAMPLE-TAB-020xaf9e…57a6100.00 eUSD0.000.0013 Oct, 20:14Held
EXAMPLE-TAB-010xF950…640a0.0086.4013.607 Oct, 20:24Captured, rest returned

The Long Room (example)

Reference EXAMPLE-TAB-TMJJBJ
Customer copy0xaf9e…57a6
Held for The Long Room (example)100.00eUSD
Valid until14 Oct, 13:59 UTC, in 7 days
Merchant copy0x9229…700F
Authorized100.00eUSD
  • Imprinted, 7 Oct, 14:09100.00
  • Captured so far0.00
Hold no. 0xc0e9b4c1…4ae400Opened 7 Oct, 14:09 UTC

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.

What the merchant's server hears

Every vault event for The Long Room (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.