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-BAY-TMJJBE0x5875…06cc60.00 eUSD0.000.0014 Oct, 13:59Held
PROOF-BAY-6151G0xdd5c…f6910.000.0060.007 Oct, 13:52Expired, returned
PROOF-BAY-5XP500xbCdB…80cF0.000.0060.007 Oct, 13:49Expired, returned
PROOF-BAY-5UH350x3147…8C880.000.0060.007 Oct, 13:47Expired, returned
EXAMPLE-BAY-020x5875…06cc47.60 eUSD12.400.0013 Oct, 20:14Held
EXAMPLE-BAY-010xaf9e…57a60.0020.0739.937 Oct, 20:24Captured, rest returned

Quay Street Charging (example)

Reference EXAMPLE-BAY-02
Customer copy0x5875…06cc
Held for Quay Street Charging (example)47.60eUSD
Valid until13 Oct, 20:14 UTC, in 6 days
Merchant copy0xA715…029a
Authorized60.00eUSD
  • Imprinted, 6 Oct, 20:2460.00
  • Captured so far12.40
Stub 16 Oct, 20:46
Captured12.40 eUSD
Fee0.02
Hold no. 0x1cf982db…aa1518Opened 6 Oct, 20:24 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 Quay Street Charging (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.