Integrations · Help desk AI
How to let Intercom Fin issue Stripe refunds with manager approval
Let Fin request refunds through a data connector, with your cap and a named approver. Fin calls Countersign through a data connector. Fin never holds a Stripe key with refund rights.
Auto-approve under $50
Small refunds that fit your rules go through at once.
Route the rest
A named approver gets a one-tap card on their phone.
Log everything
Who approved, why, the Stripe refund id. CSV for finance.
Setup: Intercom Fin data connector
- Sign up free, connect Stripe with a restricted key (test mode works) and pick a policy.
- In Intercom, go to Settings → Integrations → Data connectors → New data connector, and call it "Request refund".
- Set "When should Fin use this?" to: when a customer asks for a refund on a payment. Add inputs charge_id, amount (cents) and reason, and map ticket_url and customer_email from the conversation.
- Method POST, URL https://countersign.vibiz.app/api/v1/refunds/request, header Authorization: Bearer cs_YOUR_KEY.
- Paste the body below, then map the response field "message" into Fin's reply. Fin never gets refund rights in Stripe.
{
"charge_id": "{{charge_id}}",
"amount": {{amount}},
"reason": "{{reason}}",
"ticket_url": "{{conversation.url}}",
"agent_name": "support-bot",
"agent_reasoning": "{{fin.reasoning}}",
"customer_email": "{{customer.email}}"
}Replace cs_YOUR_KEY; in the dashboard this snippet comes with your key filled in.
Questions
Does Intercom Fin get access to my Stripe account?
No. Intercom Fin gets a Countersign key that can only ask for refunds. Countersign holds a restricted Stripe key and refunds only after your policy or an approver says yes.
What does the agent get back?
status (approved_and_refunded, pending or denied), a message to relay to the customer, the rule that decided it, and a status_url for pending requests.
Who approves the big ones?
The approver for that amount tier gets an email with a one-tap approve card: customer, charge, refundable balance, earlier refunds, the agent's reasoning and the ticket link.