BTCPay Server Strawberry

The BTCPay Server payment requests nobody wants to work through

One sentence in, and a companion has been through the BTCPay Server payment requests, put them where you can read them, and marked the ones it was not sure about.

Open the payment request. Check it against something else. Write the change. Move to the next one. That is the BTCPay Server afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a payment request until you approve it.

What it can do is exactly what BTCPay Server exposes to an account you authorise and nothing beyond it: 2 operations, 1 read and 1 write. In practice that means it can create a payment request, and work across the payment requests and store on-chain wallet balances.

The BTCPay Server API stops at BTCPay Server. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

What does it already know about your store on-chain wallet balances?

1 of the 2 operations is a read.

Your account, not a guess at it: a companion can get store on-chain wallet balance, and the full list below is the whole list, with nothing inferred from BTCPay Server's documentation.

The payment requests are what most of this inventory is about, alongside the store on-chain wallet balances. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of BTCPay Server admin becomes a queue you review.

  • Get Store On-Chain Wallet Balance

Which payment requests wait for your approval?

The one write operation there is waits for you.

A companion can create a payment request, and each one is staged on an approval card first: you see the payment request, the field and the new value before it lands in BTCPay Server.

Nothing in BTCPay Server is sent, changed or deleted on your behalf without that click, and a rejected card leaves the payment request exactly as it was. The gate is the same one on every surface, described at security.

  • Create Payment Request

Can it get store on-chain wallet balance every morning by itself?

Yes.

Saved as a routine, the BTCPay Server payment requests pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The operations playbook catalogues the other recurring shapes of store admin, the BTCPay Server payment requests sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your BTCPay Server account and a companion works 2 operations in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide