Loopwix

Our beta release is end of October 2026

Join the waitlist
Skip to content
Loopwix

Use case

A chatbot for billing questions that reads Stripe, safely

Loopwix answers “what was I charged for?”, “when does my plan renew?” and “can I get my invoice?” for verified customers, and passes refunds and disputes to your team.

Beta opens end of October 2026. Early access is invite-only.

Loopwix Agent

Online

Sample
  1. I was charged $49 this morning, what's that for?
  2. I can check. I've sent a code to your email to confirm it's you. Please enter it here.
  3. 330918
  4. Verified: customer owns the email on the account

In short

A chatbot for billing questions answers customers' questions about invoices, charges and subscriptions using your billing system. Loopwix verifies the customer by email, reads their invoices and subscription status from Stripe, explains your billing policies, and passes refunds, disputes and plan changes to your team.

By the Loopwix team · Last updated 11 October 2026

Why billing questions pile up

  • The same questions every day

    What was this charge? When does it renew? Where is my invoice?

  • Billing data is sensitive

    Anyone can type an email address. A bot must not show invoices without proof of who is asking.

  • Money needs a person

    Refunds and disputes should only move when someone on your team decides they should.

Who this is for

  • Subscription boxes

    Renewals, skipped boxes and unexpected charges.

  • Gyms and memberships

    Membership status, renewal dates and card receipts.

  • SaaS products

    Plan, invoice and renewal questions from customers.

  • Online courses

    Receipts and payment questions after enrolment.

  • Agencies with retainer clients

    Invoice copies and payment status for recurring clients.

  • Service businesses

    Invoices sent through Stripe and questions about them.

Questions it answers, and what it never does

Questions it answers, and what it never does
FeatureLoopwix
“When does my subscription renew?”Reads the renewal date from Stripe for the verified customer
“Can I get last month's invoice?”Finds the invoice and shares its details
“Why was I charged twice?”Shows the charges it can see and opens a ticket for your team
“What's your refund policy?”Explains it from your policy page
“Refund me”Never refunds on its own; passes the request to your team with the details
“Change my plan”Passes to your team (plan changes are off by default)

Refunds and plan changes stay off by default, because money should only move when a person decides it should.

Proof by example

See a real conversation

The $49 is part of a made-up example. It is not a Loopwix price.

  • Answers show where they came from.
  • Nothing changes until the customer confirms.
  • A person takes over when it should.

Loopwix Agent

Online

Sample
  1. I was charged $49 this morning, what's that for?
  2. I can check. I've sent a code to your email to confirm it's you. Please enter it here.
  3. 330918
  4. Verified: customer owns the email on the account
  5. Thanks, you're verified. The $49 charge today is the monthly renewal of your Pro membership. Your next renewal is on 11 November.Source: Stripe
  6. I cancelled last week though
  7. I can see your membership is still active in our system. I've opened a ticket so the team can check your cancellation and the charge. They'll reply here, usually within a few hours.Source: Stripe, Cancellation policy

Set it up in 3 steps

  1. 1

    Connect Stripe

    Approve what Loopwix may read: customers, invoices and subscription status.

  2. 2

    Add your billing policies

    Refunds, cancellations, renewals and failed payments, from your website or a document.

  3. 3

    Choose your handoff rules

    For example all disputes, any refund request, or charges above a set amount, then test and go live.

Safety

Rules that keep billing safe

  • Billing details only after the customer verifies their email

  • Card numbers are never shown or stored in chat

  • No refunds, credits or plan changes by the AI unless you switch them on, and they're off by default

  • Every lookup recorded in your audit log

  • Customers can be handed to a person at any point

More about how it works: how Loopwix keeps data safe.

Channels and integrations

Works with the systems that bill your customers

Customers ask about charges on your website, messaging apps or inside your own app, and Loopwix reads the answer from the system that bills them.

Where customers reach you

  • Website chat
  • Messaging apps
  • Your own app, through the developer API

Systems it works with here

  • Stripe

    Customers, invoices, subscription status

  • Gmail

    Confirmations

  • Slack

    Billing alerts

Not limited to a list of integrations.

If a system has an API or an MCP server, your Loopwix agent can read it and act on it, inside permissions you approve. Your booking tool, CRM, order system, helpdesk or in-house software: connect as many as your business needs.

  • Named connectors

    Shopify, Stripe, Calendly, Gmail, Slack and Google Sheets, ready to connect.

  • Any REST API

    Point Loopwix at any HTTP API with its address and authentication, and approve each endpoint it may use.

  • Any MCP server

    Connect a Model Context Protocol server by URL. Loopwix finds its tools, then tests and approves them like any other source.

Loopwix reads billing status and invoices only. Card numbers never appear in the chat, and refunds and plan changes stay with your team unless you decide otherwise.

How Loopwix compares

Billing questions: how Loopwix compares
FeatureBilling FAQ pageSupport team by emailLoopwix billing chatbot
Answers with the customer's own dataNoYes, slowlyYes, instantly, after verification
Connects to your systemsNot applicableWhatever your team opens by handAny system: named connectors, any REST API, any MCP server
Available at any hourYesNoYes
Handles refundsNoYesPasses them to the team, with the details
Protects billing dataNot applicableDepends on the agentEmail verification, enforced by the server

What you need to get started

Before you begin

  • Access to your Stripe account, to approve what Loopwix may read
  • Your billing, refund and cancellation policies, on your website or in a document
  • The email address or Slack channel where refunds and disputes should go
  • About 15 minutes to connect, test and go live

Building for clients? See the agency program.

Frequently asked questions

Can a chatbot answer billing questions safely?

Yes, if it verifies the customer first. Loopwix sends a one-time code to the customer's email before showing any billing details.

Does it work with Stripe?

Yes. It reads customers, invoices and subscription status from your Stripe account.

Can it issue refunds?

Not by default. Refund requests go to your team with the details. Refunds stay off unless you choose otherwise.

Will it see card numbers?

No. It never shows or stores full card numbers.

Can customers download invoices?

Yes. It finds the invoice they ask about and shares its details and link.

What if the customer disputes a charge?

It opens a ticket with the charge details and a summary for your team.

Does it work inside our app?

Yes, through the developer API, with the same verification.

Early access

See your agent in 48 hours.

Tell us your website and business type. We build an agent on your own content and send you a private link to try it, before the beta opens at the end of October 2026.

Prefer to wait? Join the waitlist.

We use your website to build the agent. No spam, and your details stay private.