How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
BTCPay Server

BTCPay Server Stores (Payout Processors) API

Stores (Payout Processors) operations

Documentation Provider Profile APIs.io OpenAPI GitHub

BTCPay Server Stores (Payout Processors) API is one of 31 APIs that BTCPay Server publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Stores (Payout Processors). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, a GitHub repository, authentication docs, and rate-limit docs.

This API exposes 9 operations across 6 paths, and defines 10 schemas. It is described by OpenAPI 3.0.0, at version v1.

Requests are made against a single base URL, https://{btcpay-host}.

9 operations 6 paths 10 schemas 1 DELETE5 GET3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v1
Base URL
https://{btcpay-host}/api/v1
Authentication
API Key, HTTP Basic
Contact
BTCPay Server
License
MIT
Resource Areas
1

Authentication & Security 2

BTCPay Server Stores (Payout Processors) API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (API_Key). It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

  • API_Key — BTCPay Server API key. Format: 'token {apiKey}'
  • Basic — HTTP Basic Authentication with email and password

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 1 DELETE, 5 GET, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Stores (Payout Processors) 9

Stores (Payout Processors) operations

GET
/api/v1/stores/{storeId}/payout-processors
Get store configured payout processors
StorePayoutProcessors_GetStorePayoutProcessors 1 param → 200403404
DELETE
/api/v1/stores/{storeId}/payout-processors/{processor}/{paymentMethodId}
Remove store configured payout processor
StorePayoutProcessors_RemoveStorePayoutProcessor 3 params → 200403404
GET
/api/v1/stores/{storeId}/payout-processors/OnChainAutomatedPayoutSenderFactory/{paymentMethodId}
Get configured store onchain automated payout processors
GreenfieldStoreAutomatedOnChainPayoutProcessorsController_GetStoreOnChainAutomatedPayoutProcessorsForPaymentMethod 2 params → 200403404
PUT
/api/v1/stores/{storeId}/payout-processors/OnChainAutomatedPayoutSenderFactory/{paymentMethodId}
Update configured store onchain automated payout processors
GreenfieldStoreAutomatedOnChainPayoutProcessorsController_UpdateStoreOnChainAutomatedPayoutProcessorForPaymentMethod 2 params body → 200403404
GET
/api/v1/stores/{storeId}/payout-processors/LightningAutomatedPayoutSenderFactory/{payoutMethodId}
Get configured store Lightning automated payout processors
GreenfieldStoreAutomatedLightningPayoutProcessorsController_GetStoreLightningAutomatedPayoutProcessorsForPaymentMethod 2 params → 200403404
PUT
/api/v1/stores/{storeId}/payout-processors/LightningAutomatedPayoutSenderFactory/{payoutMethodId}
Update configured store Lightning automated payout processors
GreenfieldStoreAutomatedLightningPayoutProcessorsController_UpdateStoreLightningAutomatedPayoutProcessor 2 params body → 200403404
GET
/api/v1/stores/{storeId}/payout-processors/OnChainAutomatedTransferSenderFactory
Get configured store onchain automated payout processors
GreenfieldStoreAutomatedOnChainPayoutProcessorsController_GetStoreOnChainAutomatedTransferSenderFactory 1 param → 200403404
PUT
/api/v1/stores/{storeId}/payout-processors/OnChainAutomatedTransferSenderFactory
Update configured store onchain automated payout processors
GreenfieldStoreAutomatedOnChainPayoutProcessorsController_UpdateStoreOnChainAutomatedTransferSenderFactory 1 param body → 200403404
GET
/api/v1/stores/{storeId}/payout-processors/LightningAutomatedPayoutSenderFactory
Get configured store Lightning automated payout processors
GreenfieldStoreAutomatedLightningPayoutProcessorsController_GetStoreLightningAutomatedPayoutSenderFactory 1 param → 200403404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are OnChainAutomatedTransferSettings (5 properties), LightningAutomatedTransferSettings (4 properties), UpdateOnChainAutomatedTransferSettings (4 properties), UpdateLightningAutomatedTransferSettings (3 properties). Each schema is shown below with its type and property counts.

LightningAutomatedTransferSettings
object
4 properties
TimeSpanSeconds
A span of times in seconds
UpdateLightningAutomatedTransferSettings
object
3 properties
OnChainAutomatedTransferSettings
object
5 properties
TimeSpan
number
PayoutMethodId
string
Payout method IDs. Available payment method IDs for Bitcoin are: - "BTC-CHAIN": Onchain -"BTC-LN": Lightning
UpdateOnChainAutomatedTransferSettings
object
4 properties
StoreId
string
Store ID of the item
PaymentMethodId
string
Payment method IDs. Available payment method IDs for Bitcoin are: - "BTC-CHAIN": Onchain -"BTC-LN": Lightning - "BTC-LNURL": LNURL
PayoutProcessorData
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

btcpay-stores-payout-processors-api-openapi.yml Raw ↑

Other APIs BTCPay Server publishes across the network.

BTCPay Server API Keys API
AE Profile APIs.io
BTCPay Server Apps API
AE Profile APIs.io
BTCPay Server Authorization API
AE Profile APIs.io
BTCPay Server Crowdfund API
AE Profile APIs.io
BTCPay Server Files API
AE Profile APIs.io
BTCPay Server Health API
AE Profile APIs.io
BTCPay Server Invoices API
AE Profile APIs.io
BTCPay Server Lightning address API
AE Profile APIs.io
BTCPay Server Lightning (Internal Node) API
AE Profile APIs.io
BTCPay Server Lightning (Store) API
AE Profile APIs.io
BTCPay Server Miscelleneous API
AE Profile APIs.io
BTCPay Server Notifications (Current User) API
AE Profile APIs.io
#Stores (Payout Processors)
← Back to B APIs
API Details
ID
btcpay:btcpay-stores-payout-processors-api
Base URL
https://{btcpay-host}/api/v1
Docs
https://docs.btcpayserver.org/API/Greenfield/v1/
Provider
BTCPay Server
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=btcpay-stores-payout-processors-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/btcpay-stores-payout-processors-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of BTCPay Server Stores (Payout Processors) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.