Check BTCPay Server status after a failed Stripe charge
Bring your Bitcoin payment server's available status details into view when a direct Stripe charge fails.
Trigger
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Action
Get BTCPay Server Info
Tool to retrieve information about the btcpay server instance. use when needing server version, tor address, supported payment methods, and synchronization states.
Why this helps
A charge failure can prompt a scramble across payment systems, with server details requiring a separate lookup.
- Make BTCPay instance details easier to review during payment troubleshooting.
- Reduce extra navigation during a charge failure.
- Keep available payment method and synchronization information close to the incident.
Setup
Build it in a few focused steps.
- 1Connect Stripe and BTCPay Server once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel what outcome you want.
- 3In one instruction, ask Notis to retrieve BTCPay Server instance information when a direct Stripe charge fails and summarize the available status details.
- 4Choose the Stripe Charge Failed trigger and select where run reports should go.
- 5Test with one real failed direct charge and review the run report.
Questions about this workflow
Does this determine the cause of the Stripe failure?
No. It retrieves BTCPay Server instance information. Any Stripe failure cause depends on the data supplied by the event and is not established by the server check.
What information can it retrieve?
The action description includes instance information such as server version, Tor address, supported payment methods, and synchronization states, subject to what the server returns.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Btcpay server. A trigger fires from one place; an action lands in another.
Stripe triggers
Btcpay server actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Payment Request
Tool to create a new payment request for a store. use after confirming store id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Store
Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create BTCPay Server User
Tool to create a new btcpay server user. use when you need to register a new user programmatically as an administrator.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Register a Webhook
Tool to register a new webhook. use when you need to receive store event notifications.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Delete API Key
Tool to revoke a specific api key. use when you need to remove an api key to immediately prevent its use. call after identifying the key to revoke.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Delete Payment Request
Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.
Product Created Trigger
Triggered when a product is created in Stripe
Delete Store Payout
Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Get API Key
Tool to retrieve the current api key. use after authentication to get api key details.
Connect any two apps with Notis in the middle.
Stripe and Btcpay server, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Btcpay server.