Retrieve an offline payment method
One tender’s configuration, addressed by name rather than by an id: the (store, method) pair is unique and the store comes from your key, so there is no surrogate id on this API at all. 404 MEANS THE MERCHANT NEVER CONFIGURED IT, which is not the same fact as enabled false. Only one of those two is a decision, and a client reporting a merchant’s setup needs to tell them apart.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Path Parameters
Response
Success
