Updated:
What you'll achieve
Support can review read-only billing context and offer a confirmed one-time checkout from a published widget Procedure when the required Stripe permissions are available.
Connect Stripe
The screenshot shows the Stripe provider detail panel in the demo. It is a visual example only: complete the connection in your workspace after the required Stripe credentials and provider approval are ready.
Stripe App review, external test data and remote verification remain separate gates. DobroDesk never treats missing credentials or provider approval as a successful remote connection. If a checkout permission is unavailable, the read-only customer context can remain available while the related widget Procedure stays unavailable.
Open Settings > Integrations > Data integrations and choose Stripe.
Confirm that the Stripe App client credentials and webhook secret are configured for this DobroDesk deployment. If the screen says awaiting credentials, an owner must complete that setup first.
Sign in to the Stripe account you administer and grant only the displayed permissions. Customer and billing context stays read-only. A widget checkout Procedure additionally needs access to the selected Products, one-time Prices and Checkout Sessions.
Return to DobroDesk and verify the connected account, granted scopes and webhook health.
Open a known customer and confirm that the Stripe context is attributed to the right customer identity.
Review Stripe billing context safely
- Customer, invoice and subscription lookups require an authorized customer identity and stay read-only.
- Disconnecting revokes the provider connection, removes encrypted credentials and stops future Stripe lookups without deleting DobroDesk conversations.
Offer one-time checkout in the widget
Open the Prepare a quote and checkout Procedure template and select the connected Stripe account for each required operation. Native Stripe fields are mapped automatically. Custom API fields are not a substitute for the native Stripe operations.
Use active Stripe Products with fixed one-time Prices. The customer searches the catalog, chooses a price and quantity, reviews the current quote and confirms before the provider-hosted Checkout opens.
Stripe Checkout collects the payment details. A new buyer can enter an email there without access to another customer's billing history. DobroDesk does not create direct charges, subscriptions or refunds through this flow.
After returning to the chat, choose Check payment. Pending or unknown results stay available for another provider status check. The customer sees paid only after Stripe confirms the Checkout Session.
If the Stripe account is disconnected or reconnected, review and save the Procedure bindings again. A changed connection revision makes the previous binding stale so a customer cannot resume an old account mapping.
Stripe checkout and permission FAQ
Can billing context work without checkout permissions? Yes. Read-only customer and billing context has its own permission boundary. Catalog, quote, Checkout and payment-status steps require the additional Stripe permissions and a saved Procedure binding.
Can DobroDesk show a successful payment after the customer returns from Checkout? No. The return page only tells the customer to return to the original chat and run Check payment. Only a fresh Stripe status response can show paid.
Put this guide into practice
Open Setup Center to apply the instructions in your workspace. Sign in when prompted.