Waymark / Routes / api.storedgefms.com Capture a card securely for a storEDGE web payment using the transport-key flow
domain: api.storedgefms.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Authenticate via one-legged OAuth 1.0. Call POST /v1/:facility_id/web_payments/create_transport_key to generate a transport key for a browser-based card-capture form. Render the payment form using the returned transport key so raw card data never touches your own server. If the customer abandons or the payment fails, call POST /v1/:facility_id/web_payments/cancel_transport_key to invalidate the key. Once payment succeeds, reconcile it against the tenant's ledger using the existing ledger/invoice GET endpoints. Known gotchas This is a tokenization/handshake mechanism, not a payment-submission endpoint — it's a front-end security primitive, not a full payment API. Docs don't specify a token TTL; always call cancel_transport_key on abandonment rather than assuming silent expiry. Distinct from ledger-level make_payment (posting an already-known payment to a ledger) — don't conflate the two when designing a checkout.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp