BTCPay Server
Build around payment requests

SPIRITT can build payment-request workspaces, coordinate store event workflows, and keep checkout operations traceable. Create shareable payment requests for selected stores and maintain a source-to-request ledger.

Yes. A payment-request workspace can map requests to customer orders, coordinate validated store-event processing, and keep request creation distinct from evidence of payment. SPIRITT builds the application and runs the connected workflow around your rules.

BTCPay Server supports store and payment-request creation, request listings, store and server reads, app listings, and webhook creation or reads. A payment request is a shareable page from which a customer can initiate an invoice, not proof of payment. This page does not promise payout creation, refunds, wallet transfers, or invoice retrieval.

SPIRITT coordinates separately connected apps around one outcome. Track request workflows with Supabase. Send payment request links with Gmail. Resolve payment exceptions with Slack. You choose the accounts and actions it can use.

Yes. Check store and webhook configuration, track processing failures, and distinguish payment-request creation from confirmed payment. Set the schedule and approval rules; SPIRITT verifies results and keeps unresolved work assigned to an owner.

Open a workspace, connect BTCPay Server, and hand SPIRITT a mission. Specify the records, outcome, and approval rules. Your connected account must have access to the operations the mission uses; additional apps are connected separately.