Skip to main content

Payment Service API Overview

Payment Service API is designed for server-to-server integrations.

Base Routes​

  • /integration/invoices
  • /integration/fees

Auth Model (API Key or Signature)​

You can choose between API Key or Request Signature for authentication.

Headers required:

  • x-depay-api-key (Recommended for server-to-server)
  • OR x-depay-signature + x-depay-timestamp (EIP-191 signature)

You can generate your API key in the dashboard at https://app.sodapopfi.com/.

2. Request Signature​

Server validates signature recovery, timestamp window, and replay uniqueness. For exact signing format and message structure, see Payment Service Request Signing.

Note: ownerAddress must always be provided in the request body (for POST) or query parameters (for GET/DELETE) regardless of the authentication method used.

Action Values​

  • invoice.create
  • invoice.status
  • invoice.delete
  • invoice.list
  • fee.set-meta
  • fee.set-payout-meta

Default Invoice Expiration​

  • 1 hour from creation unless explicit expiresAt is provided.

Integration Notes​

  • Keep action value aligned with endpoint intent.
  • Canonical JSON used for signature must match request payload exactly.
  • Regenerate signature when timestamp changes.