Skip to main content

Overview

Payment session endpoints are designed for browser/client checkout experiences. They expose invoice context in a browser-safe way using session headers.

Authentication

Requires:
  • x-session-token: pst_...
  • x-signature: sig_...

Request

Endpoint:
  • GET /api/v1/payments/session-details
Playground (interactive reference): Example:

Response

Notes:
  • remaining_time is milliseconds until expiration (clamped at 0).
  • remaining_seconds is seconds until expiration (clamped at 0).

Underpaid lock-in

If invoice_status is underpaid, the response includes:
  • locked_network
  • locked_token_id
  • locked_payment_address
Payors must complete the remaining balance with the locked token/network.

Errors

  • 401 invalid session token/signature
  • 404 session not found / expired

Examples

Next: Available tokens