When a customer asks to upgrade a service, pay an invoice or complete an order, your team can send a structured payment card in the conversation. Published requests start OPEN and can become PAID, EXPIRED, CANCELLED or REFUNDED through the supported verification or bookkeeping paths. Checkout preparation can remain uncertain before any card is published.
Setting up your merchant checkout connection
Workspace owners configure merchant checkout under Settings → Integrations → Actions in your system. Use Native Stripe checkout to create supported sessions with your own credentials, or supply an existing allowed HTTPS merchant checkout link:
- Enter your merchant display name and default three-letter ISO currency code (such as
USD,EUR,GBP, orAED). - For native Stripe, configure its separate API credentials, native webhook secret and endpoint; embedded checkout also needs your publishable key and the current website embed bridge.
- For existing links, configure allowed checkout hosts. A custom signed callback uses its own shared secret; your connector must establish processor truth before sending it. Sharing a callback secret does not make it a native Stripe webhook.
Frosvo seals stored merchant credentials and omits them from workspace exports. Full server/database backups can contain sealed values and need appropriate protection along with the encryption key. Merchant payments are separate from your Frosvo subscription billing.
Sending a payment request from the desk
Inside any conversation in the Desk, open the Payment requests section in the right-hand context panel:
- Choose an existing payment link, native hosted Stripe checkout, or native Stripe checkout on the customer's website. Embedded checkout requires a website conversation; other channels use hosted links.
- Enter the reference, title, amount, currency and optional customer note. Supply the HTTPS checkout URL only for an existing link.
- Click Send payment card to chat. Frosvo posts a visible message in the conversation and renders an interactive payment card in the customer's chat widget.
Automatic webhook confirmation and manual updates
Native Stripe events prompt a server-side session retrieval; event fields or a browser return alone cannot prove payment. Owners can choose Check Stripe status for a published native request. The check validates the saved session, amount, currency, merchant and request before applying paid or expired state. Pending payment remains pending. Changed settings or payment details require reload/review, and checks are audited. A confirmation reply must also pass the current conversation/channel policy.
Owners may record manual paid/cancelled/refunded bookkeeping for existing external links. Those controls do not issue a provider refund or stop a checkout. Native requests refuse manual overrides and unverified custom callbacks. Refund reconciliation, processor cancellation and unpublished uncertain-session recovery remain separate work. Keep the original request identity when retrying an uncertain creation; do not start another purchase because a response was lost.