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
MCP-JOB0x9AF3…48A60.003.1246.888 Oct, 14:41Captured, rest returned
MCP-JOB0xB71D…17B90.003.1246.888 Oct, 14:40Captured, rest returned
MCP-JOB0xA354…e7BB0.003.1246.888 Oct, 14:39Captured, rest returned
MCP-JOB0xc8EA…963220.00 eUSD0.000.008 Oct, 14:38Held
EXAMPLE-JOB-TMJJBF0x9793…E12642.08 eUSD7.920.0014 Oct, 13:59Held
PROOF-JOB-6151G0xdd5c…f6910.0010.1839.828 Oct, 13:51Captured, rest returned
PROOF-JOB-5XP500xbCdB…80cF0.0010.1839.828 Oct, 13:48Captured, rest returned
PROOF-JOB-5UH350x3147…8C880.0010.1839.828 Oct, 13:45Captured, rest returned
EXAMPLE-JOB-010x9793…E12629.12 eUSD20.880.0013 Oct, 20:14Held

Saltmarsh Inference API (example)

Reference EXAMPLE-JOB-01
Customer copy0x9793…E126
Held for Saltmarsh Inference API (example)29.12eUSD
Valid until13 Oct, 20:14 UTC, in 6 days
Merchant copy0x6c5D…844F
Authorized50.00eUSD
  • Imprinted, 6 Oct, 20:2420.00
  • Added by the agent, 6 Oct, 20:24+30.00
  • Captured so far20.88
Hold no. 0xbb1e0978…0f464dOpened 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 Saltmarsh Inference API (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.