payment.offer.set
Decide whether a STORE offers one of the tenant’s installed payment apps, and where it sits in that store’s list. The app stays installed (and configured) for the tenant; a store with no row offers every installed app, in install order. A withheld app is not listed by read.payment_methods for that store, and place_order / payment.initiate refuse it by name (payment_not_offered).
- Scope:
extensions.write - System: no
- Reachable from:
POST /v1/commands/payment.offer.set— the tenant data face, with a tenant credential carryingextensions.write· MCP toolpayment.offer.set· SDKclient.call('payment.offer.set', …) - Events:
payment.offer.updated
Input (JSON Schema)
Section titled “Input (JSON Schema)”{ "properties": { "extension_id": { "minLength": 1, "type": "string" }, "offered": { "type": "boolean" }, "position": { "anyOf": [ { "maximum": 10000, "minimum": 0, "type": "integer" }, { "type": "null" } ] }, "store_id": { "minLength": 1, "type": "string" } }, "required": [ "store_id", "extension_id", "offered" ], "type": "object"}Result (200)
Section titled “Result (200)”Open (unknown) — this command does not declare an output schema.
Errors
Section titled “Errors”validation_failed (400) · unauthorized (401) · forbidden (403) · conflict (409) · internal (500)