Skip to main content
GET
Returns the full payment-methods configuration for the vendor bound to your API key, enriched with global catalog data (uuid, name, description). The endpoint takes no query parameters — accountId and vendorId are derived from the API key. All methods are returned (enabled and disabled) so the client can decide what to show. Methods in the account JSONB without a catalog match are excluded.
There is now a v2 of this endpoint that resolves the configuration per store, with channel, fulfillment and terminal levels, and returns the configuration values. This v1 stays available and has no sunset date — migrate when it suits you.

Authentication

string
required
Your Fire API key with the payment-methods:read scope. The key must be vendor-scoped (account + vendor binding) — keys without a vendorId are rejected with 403.

Request

Response

boolean
Always true on a 200.
object

Notes

  • uuid comes from the global payment_methods catalog, not from the per-account JSONB.
  • Disabled methods are included so you can render them with an “unavailable” state or hide them — it is your decision.
  • countries groups by country code from the JSONB.

Channels config

Companion endpoint to read configured sales channels.

Authentication

How vendor-scoped API keys and scopes work.